Skip to content
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

Enabe a secure way for setting up secrets in cruisecontrol.properties file #919

Open
play-io opened this issue Jan 25, 2023 · 2 comments
Open
Labels
community enhancement New feature or request

Comments

@play-io
Copy link

play-io commented Jan 25, 2023

Is your feature request related to a problem? Please describe.

  • Cruise Control can post self-healing and anomaly detection events to a Slack channel.
  • Connection details for Slack must be provided in cruisecontrol.properties ex slack.self.healing.notifier.webhook property.
  • Slack's webhook is a secret and should not be presented in clear text ex in a GIT repository.
  • Koperator assumes cruisecontrol.properties properties defined in KafkaCluster custom resource and therefore value of slack.self.healing.notifier.webhook should be there as well.
  • Because I don't want keep clear text value in slack.self.healing.notifier.webhook I was looking for a way ex:
    • refer to a value from a Secret
    • or refer to a value from ENV variable
      but cannot see it's possible now.

Describe the solution you'd like to see
Introduce syntax/[substitution variables] which can be used in ex KafkaCluster CR and be translated by "engine" (operator??) to values from a Secret or env variables.

Describe alternatives you've considered
N/A

Additional context
N/A

@panyuenlau panyuenlau added enhancement New feature or request community labels Feb 3, 2023
@panyuenlau
Copy link
Member

Hey @play-io, thanks for you feature request! Did you get to join our Slack channel where we can better felicitate discussion like this?

@play-io
Copy link
Author

play-io commented Feb 17, 2023

Hey @play-io, thanks for you feature request! Did you get to join our Slack channel where we can better felicitate discussion like this?

Will do. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants