-
Notifications
You must be signed in to change notification settings - Fork 707
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce Elasticsearch config and additional secret mounts to stack config policy #7233
Introduce Elasticsearch config and additional secret mounts to stack config policy #7233
Conversation
pkg/controller/stackconfigpolicy/elasticsearch_config_secret_mounts_settings.go
Outdated
Show resolved
Hide resolved
pkg/controller/stackconfigpolicy/elasticsearch_config_secret_mounts_settings.go
Outdated
Show resolved
Hide resolved
Co-authored-by: Michael Morello <michael.morello@gmail.com>
Co-authored-by: Thibault Richard <thbkrkr@users.noreply.github.com>
pkg/controller/stackconfigpolicy/elasticsearch_config_settings.go
Outdated
Show resolved
Hide resolved
Co-authored-by: Thibault Richard <thbkrkr@users.noreply.github.com>
pkg/controller/stackconfigpolicy/elasticsearch_config_settings.go
Outdated
Show resolved
Hide resolved
} | ||
|
||
// reconcileSecretMounts creates the secrets in SecretMounts to the respective Elasticsearch namespace where they should be mounted to. | ||
func reconcileSecretMounts(ctx context.Context, c k8s.Client, es esv1.Elasticsearch, policy *policyv1alpha1.StackConfigPolicy) error { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure to understand if Secrets
which are no longer referenced in a policy are deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
currently if a secret is removed from a stack config policy, that secret gets left behind(it is deleted only when the stack config policy itself is deleted or the elasticsearch cluster is). I was going to address this in a separate PR, as even today we don't reset a secret that is no longer referenced in the stackconfig policy I believe.
Co-authored-by: Michael Morello <michael.morello@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM just a few nits.
Co-authored-by: Peter Brachwitz <peter.brachwitz@gmail.com>
buildkite test this -f p=gke |
…config policy (elastic#7233) Introduce two new fields in StackConfigPolicy, ElasticsearchConfig and SecretMounts. The ElasticsearchConfig field can be used to add configurations for the Elasticsearch clusters managed by the StackConfigurationPolicy, these configurations typically go into the elasticsearch.yml file.SecretMounts are used add additional secrets that need to be mounted into the Elasticsearch pods. --------- Co-authored-by: Michael Morello <michael.morello@gmail.com> Co-authored-by: Thibault Richard <thbkrkr@users.noreply.github.com> Co-authored-by: Peter Brachwitz <peter.brachwitz@gmail.com>
This PR introduces two new fields to the stack config policy, under Elasticsearch
These changes are part of an effort to allow users to configure Authentication policies through the Stack configuration.
This PR does the following.
StackConfigPolicy controller:
Elasticsearch controller:
Tasks pending: