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
  • Upload your artifacts to the repository
  • Declare an artifact provider in the YaK UI
  1. Configuration

Artifact providers

PreviousProvider imagesNextManage infrastructures

Last updated 2 months ago

An is a repository that contains all the required to deploy components. In its current version, YaK supports AWS S3 bucket, Azure Blob Storage, and OCI Object Storage as artifact providers.

The repository must already exist at your cloud provider end. YaK will connect to this repository to fetch the required artifacts.

YaK does not provide the artifacts, it is up to the user to download artifacts from the vendors and make them available to the right artifact provider.

However, we provide you with the list of required artifacts for a given component type, and links to download them. This list can be found in the of each component type.

The path to the artifact and the artifact name must be exactly the same as what is defined in the release notes of your component type.

Upload your artifacts to the repository

  • Retrieve all required artifacts for the component you want to deploy (see component type )

  • Connect to your cloud provider account

  • Upload all artifacts needed to your repository

  • Ensure that paths and names of the files uploaded match exactly the structure defined in the release notes.

Declare an artifact provider in the YaK UI

  • Navigate to Configuration -> Artifact providers

  • Artifacts providers are organized by type of providers

    • Navigate through the tabs to find the artifact provider for your deployment (AWS, Azure, OCI, On-Prem)

  • Click Declare

  • Name your artifact provider

  • Choose the provider (AWS, Azure, OCI, On-Prem)

  • Attach the secret used to access your artifacts provider (see section).

  • Fill-in the required fields of the form with information gathered from your cloud provider (ex : bucket name, etc...)

  • The checkbox "Is Default" informs the YaK that this artifact provider is the default location where to look for artifacts when deploying any component

  • Click Save

In this release (YaK-2.1.0), only one artifact provider is supported. Support for multiple providers will be introduced in future releases.

Release Note
Release Note
secrets
artifact provider
artifacts