Custom Secret Management (Deprecated)
Last updated
Last updated
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 for using external secrets.
stackstate.manageOwnSecrets
: A boolean flag that determines whether the user wishes to manage their own secrets. Default value is false
.
stackstate.customSecretName
: (Optional) Name of the custom secret to be created by the user. Required if stackstate.manageOwnSecrets
is set to true
.
stackstate.customApiKeySecretKey
: (Optional) Key name for the API key within the custom secret. Required if stackstate.manageOwnSecrets
is set to true
.
stackstate.customClusterAuthTokenSecretKey
: (Optional) Key name for the cluster authorization token within the custom secret. Required if stackstate.manageOwnSecrets
is set to true
.
Automatic Secret Creation: By default, the chart continues to automatically create secrets as before if stackstate.manageOwnSecrets
is set to false
.
Custom Secret Management: If stackstate.manageOwnSecrets
is set to true
, 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
and stackstate.customClusterAuthTokenSecretKey
, respectively).
Implied Omission: When specifying that you would like to manage your own secrets, the chart will ignore values for stackstate.apiKey
and stackstate.cluster.authToken
.
Using Automatic Secret Creation (Default):
Managing Own Secrets: