YaK User Documentation
YaK Landing PageVisit dbi-services.comContact us
YaK Release 2.1
YaK Release 2.1
  • Welcome to YaK Release 2.1
  • Introduction
    • YaK Core
    • YaK Components
    • Terms and definitions
    • YaK Demo
  • User interface
    • Dashboard
    • Infrastructures
    • Servers
    • Components
    • Jobs
    • Configuration
    • Administration
  • 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
    • Roles
Powered by GitBook
On this page
  1. Manage infrastructures

Attach Secrets

PreviousDeclare infrastructuresNextDetach Secrets

Last updated 1 month ago

Secrets must exist first, see section for more details

Once your infrastructure has been properly declared, you need to attach secrets to operate your instances securely.

  1. Navigate to the Infrastructures menu

  2. Select the infrastructure previously created from the list

  3. Click "Actions" -> "Attach Secret"

  4. Select a secret from the list in the pop-up box (a secret must exist first)

  5. Click "Attach"

  6. Repeat the same procedure if additional secrets need to be attached to this infrastructure

You will need a minimum of 2 secrets types for cloud setups:

  • Your cloud provider credentials, to deploy to your favorite cloud (, , )

  • A (For Linux servers) or a (For Windows servers), to connect to your instances once deployed.

On-premises configuration only requires (For Linux servers) or a (For Windows servers)

Configuration/Secret
AWS
Azure
OCI
SSH key
WinRM certificate
SSH key
WinRM certificate