Custom Secret Management (Deprecated)
Overview
The SUSE Observability agent supports specifying the name of a custom secret that contains the API key and cluster authorization token. This feature is useful for users who wish to manage their own secrets and avoid the automatic creation of secrets by the Helm chart.
This method of customizing secrets is deprecated and is incompatible with the RBAC feature.
Please use the new method for using external secrets.
Regarding the Helm Chart
Configuration Options
stackstate.manageOwnSecrets
: A boolean flag that determines whether the user wishes to manage their own secrets. Default value isfalse
.stackstate.customSecretName
: (Optional) Name of the custom secret to be created by the user. Required ifstackstate.manageOwnSecrets
is set totrue
.stackstate.customApiKeySecretKey
: (Optional) Key name for the API key within the custom secret. Required ifstackstate.manageOwnSecrets
is set totrue
.stackstate.customClusterAuthTokenSecretKey
: (Optional) Key name for the cluster authorization token within the custom secret. Required ifstackstate.manageOwnSecrets
is set totrue
.
Behavior Description
Automatic Secret Creation: By default, the chart continues to automatically create secrets as before if
stackstate.manageOwnSecrets
is set tofalse
.Custom Secret Management: If
stackstate.manageOwnSecrets
is set totrue
, the chart expects the user to provide the name of the custom secret (stackstate.customSecretName
) along with the keys for the API key and authorization token (stackstate.customApiKeySecretKey
andstackstate.customClusterAuthTokenSecretKey
, respectively).Implied Omission: When specifying that you would like to manage your own secrets, the chart will ignore values for
stackstate.apiKey
andstackstate.cluster.authToken
.
How to Use in values.yaml
Using Automatic Secret Creation (Default):
Managing Own Secrets:
Last updated