-
Notifications
You must be signed in to change notification settings - Fork 176
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
Add secret for grafana credentials #2441
Comments
This is not particularly urgent, by the way, timeline for this is 1.6 which is released in 3 months. I still need to write all the code to handle this anyways |
There is currently an issue tracking the proposal for a standard, declarative, secret manager tool/service (kubernetes/test-infra#14049). The current practice is to backup the secret value in an external data store, manually upload the value as a Kubernetes secret in the cluster(s), and optionally create a Prow preset for convenience (if applicable). |
In this specific case we only need it on one job so preset is probably not really needed |
Created secret |
Thanks!
…On Mon, Mar 2, 2020 at 10:00 AM Travis Clarke ***@***.***> wrote:
Closed #2441 <#2441>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2441?email_source=notifications&email_token=AAEYGXNFGZZ4ZOJ6MLZGCDDRFPX5JA5CNFSM4K47LCMKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOXAPOVKA#event-3089033896>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEYGXINMHYW3RBB4M2LASTRFPX5JANCNFSM4K47LCMA>
.
|
For istio/istio#21541 we will need grafana credentials in the cluster. This will be used by the release builder.
I am not sure if there is a standard practice for how we handle these secrets in the cluster?
The text was updated successfully, but these errors were encountered: