Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Cloud Stackland
  • What's new
  • Installation
    • All tutorials
    • Installing Stackland on Yandex BareMetal
    • Setting up external access to a pod in a cluster
    • All guides
    • Projects
    • Resource model
      • Overview
      • Certificate Manager
      • DNS
      • IAM
      • Logging Stack
      • Managed Service for Apache Kafka®
      • Managed Service for PostgreSQL
      • Managed Service for ClickHouse®
      • DataLens
      • Monitoring
      • Object Storage
      • Disk subsystem
      • NVIDIA® GPU support
      • Policy Manager
      • Secrets Store
      • SpeechSense
  • Access management
  • Pricing policy
  • Diagnostics and troubleshooting

In this article:

  • Access to OpenBao
  • Using Secrets Injector
  • Configuration
  • Secrets Injector settings
  • OpenBao pod settings
  • Using the interface
  1. Concepts
  2. Components
  3. Secrets Store

Secrets Store

Written by
Yandex Cloud
Updated at April 8, 2026
  • Access to OpenBao
  • Using Secrets Injector
  • Configuration
    • Secrets Injector settings
    • OpenBao pod settings
    • Using the interface

Stackland uses two main tools for safe storage of secrets and their injection:

  • Secrets Injector: Uploads secrets via a Vault-compatible API and injects them into cluster resources.
  • Vault-compatible secrets storage.

If you use the default Secrets Injector configuration, the cluster's secret storage will be OpenBao, a fork of Vault.

You can change the default settings using the SecretsStoreConfig custom resource properties.

Access to OpenBaoAccess to OpenBao

The OpenBao interface and API access are disabled by default.

  • To open access to the OpenBao API from outside the cluster, you need to set the server.ingress.enabled = true flag.
  • To open access to the OpenBao interface from outside the cluster, you need to set the server.ingress.enabled = true and ui.enabled = true flag.

The interface and API will be available at https://secrets.sys.<cluster domain>. If ui.enabled is set to true, and server.ingress.enabled, to false, accessing the interface will only be available within the cluster.

Using Secrets InjectorUsing Secrets Injector

Secrets Injector is ready to work right after cluster deployment and does not require any additional configuration. Secrets Injector uses OpenBao storage in Stackland. If required, you can configure the use of your own secret storage in a custom resource using the secretsAddr property.

Secrets Injector uses the OpenBao API to authenticate service accounts that inject secrets into manifests. By default, the auth/kubernetes endpoint is used; however, you can change it by modifying the authPath property.

ConfigurationConfiguration

Here is an example:

apiVersion: stackland.yandex.cloud/v1alpha1
kind: SecretsStoreConfig
metadata:
  name: main # This is a required field you must set to `main`
spec:
  enabled: true
  settings:
    stacklandSecretsInjector: # Secrets Injector settings
      authPath: kubernetes
      enabled: true
      resources:
        limits:
          cpu: 100m
          memory: 128Mi
        requests:
          cpu: 50m
          memory: 64Mi
      secretsAddr: ''
      skipTLSVerify: false
      webhookTimeout: 30
    server: # OpenBao pod settings
      dataStorage:
        size: 2Gi
        storageClass: stackland-default
      enabled: true
      ingress:
        clusterIssuer: stackland-default
        enabled: false
      resources:
        limits:
          cpu: 500m
          memory: 512Mi
        requests:
          cpu: 100m
          memory: 256Mi
      updateStrategyType: RollingUpdate
    ui:
      enabled: true # Whether to use the OpenBao interface

Secrets Injector settingsSecrets Injector settings

stacklandSecretsInjector:
  authPath: kubernetes
  enabled: true
  resources:
    limits:
      cpu: 100m
      memory: 128Mi
    requests:
      cpu: 50m
      memory: 64Mi
  secretsAddr: ''
  skipTLSVerify: false
  webhookTimeout: 30
  • authPath: Specifies the OpenBao API endpoint for authentication and authorization via Kubernetes. The default value is auth/kubernetes.
  • enabled: Enables the use of Secrets Injector.
  • resources: Limits resources (CPU and memory) for the pod.
  • secretsAddr: Specifies the HTTPS address of the OpenBao API.
  • skipTLSVerify: Allows you to skip checking the TLS certificate if it is not in the list of trusted certificates.
  • webhookTimeout: Determines the time to wait for a response from Secrets Injector.

OpenBao pod settingsOpenBao pod settings

server:
  dataStorage:
    size: 2Gi
    storageClass: stackland-default
  enabled: true
  ingress:
    clusterIssuer: stackland-default
    enabled: false
  resources:
    limits:
      cpu: 500m
      memory: 512Mi
    requests:
      cpu: 100m
      memory: 256Mi
  updateStrategyType: RollingUpdate
  • dataStorage: Sets advanced settings for the storage.
  • enabled: Enables the use of a pod.
  • ingress: Specifies the settings of the Ingress object.
  • resources: Limits resources (CPU and memory) for the pod.
  • updateStrategyType: Determines the type of update.

Using the interfaceUsing the interface

ui:
  enabled: true
  • enabled: Enables the OpenBao interface at https://secrets.sys.<cluster domain>.

Was the article helpful?

Previous
Policy Manager
Next
SpeechSense
© 2026 Direct Cursus Technology L.L.C.