Using Externally Defined Secrets

Table of Contents

How To Use
- Example

Need help?

Schedule a consultation with an Azul performance expert.

Secrets can be externally defined to allow you to manage Kubernetes secrets independent of the Optimizer Hub configuration.

You can define the following secrets by overriding the following default settings for Externally Defined Secrets Parameters in your values-override.yaml file:

S3
Azure

How To Use

If you keep the default values, the Optimizer Hub helm chart defines and uses its own Kubernetes secret objects.
Or you use your existing secrets by:
- Defining the name of your Kubernetes secret object with existingSecret.
- Optionally you can define the name of the keys in your Kubernetes secret object with, e.g. accessKeySecretKey, in case you want something different than what Optimizer Hub expects by default.

Example

For example, if you have an existing secret with S3 credentials, and the name of this K8S secret Object is awsS3secretsForOpthub, it should contain the following values:

 MyKeyID: key123455
MyKey: xyzabcdef

Then you can configure Optimizer Hub with the following values in your values-override.yaml file:

 secrets:
  blobStorage:
    s3:
      existingSecret: awsS3secretsForOpthub
      accessKeySecretKey: MyKeyID
      secretAccessKeySecretKey: MyKey