YaK User Documentation
YaK Landing PageVisit dbi-services.comContact us
YaK Release 2.1
YaK Release 2.1
  • Welcome
  • Introduction
    • YaK Core
    • YaK Components
    • Terms and definitions
  • User interface
    • Dashboard
    • Infrastructures
    • Servers
    • Components
    • Jobs
    • Configuration
    • Administration
  • YaK Demo
  • Versioning & Compatibility matrix
  • Release Notes
    • YaK components types
      • PostgreSQL
      • Oracle
  • Installation
    • System requirements
    • Install YaK Core
      • Install YaK on your own K8S cluster
      • Install YaK on Rancher Desktop
      • Uninstall Yak
  • YaK step-by-step usage
  • Configuration
    • Secrets
    • Templates
    • Provider shapes
    • Provider images
    • Artifact providers
  • Manage infrastructures
    • Declare infrastructures
    • Attach Secrets
    • Detach Secrets
  • Manage Servers
    • Declare servers
      • Basics
      • Storage
      • Attach secrets
    • Edit server configuration
    • Deploy servers
    • Destroy servers
    • Delete servers
    • Start / Stop servers
  • Manage Components
    • Artifacts requirements
    • Component types
      • PostgreSQL
        • Description
        • Pre-requisites
        • Component references
          • PostgreSQL 2.0.0
            • Standalone deployment variables
            • HA deployment variables
      • Oracle
        • Description
        • Pre-requisites
        • Component references
          • Oracle 2.0.0
            • Standalone variables
  • Use cases
    • On-Premises
    • AWS
    • Azure
    • OCI
  • Appendix
    • Create SSH Keys with PuTTYgen
    • Roles
Powered by GitBook
On this page
  1. Manage Servers
  2. Declare servers

Basics

PreviousDeclare serversNextStorage

Last updated 2 months ago

The “Basics” tab lets you enter all the minimum information required to declare a server.

Fill out the fields:

  • Name: this is your server hostname and the name it has in the YaK application

    • Server names can only contains letters, numbers and "-" characters and cannot exceed 15 characters.

  • Select the infrastructure to deploy your servers to (Infrastructure must already exist)

  • Select an image to install in the list of the "provider image name" field (see also note below)

  • Select a server shape (YaK comes with a list of default shapes, but more shapes can be added - see )

  • Server Tags (optional)

    • Server tags are key:value pairs that can be added to your server for your own purpose. You may add custom tags as per your need (this step is optional)

  • Network

    • IP address: fill in as per your need or use automatic IP with public address. Assign IP addresses according to your cloud strategy and internal rules.

    • Scope: private or public IP address

    • Mode:

      1. Automatic (lets your provider assign a DHCP address to your server)

      2. Manual (this is to set an IP address manually)

      3. None (no IP address will be configured)

    • Admin access checkbox: Grant admin access to the YaK via this IP address.

      • At least one network interface must be set as "admin access", this is required for the Yak to connect to your server and deploy components on it.

    • Note: additional network interfaces can be added by clicking the "+" sign.

Note: Please note that images are specific to a region at some cloud providers (ex: AWS and OCI). This is not related to the YaK, but is a cloud provider's limitation.

An image declared with region "eu-central-1" for example, will be available to infrastructures that belong to the same region only.

If the same image needs to be used on 2 different regions, it must be declared twice (once for each region)

See "" section for more details.

⚠️
dedicated section
Provider images