-
Notifications
You must be signed in to change notification settings - Fork 828
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
Setup postsubmit deploy job(s) for apps running under aaa #2151
Comments
ref: #988 where I tried to grant per-namespace access to secrets, need to unpack whether this is feasible or we're still concerned about exfiltration of cert secrets |
Related to #2150. |
/milestone v1.23 |
/assign |
Opened kubernetes/test-infra#22970 |
Opened kubernetes/test-infra#23040 to have the postsubmits report to #k8s-infra-alerts in slack |
I've been holding this open to see successful deploys of all the apps #2425 touches quite a few, so if all the resulting jobs are successful I'll call this done |
One mildly annoying thing I guess, I scanned right past the "failure" text the first time. Making the template auto-bold or capitalize that might help? Or notify vs. just a regular message? Fixed slack-infra's deploy: Apps that have yet to be exercised:
|
#2431 - PR to bump kubernetes-external-secrets |
/close I'm going to call this done and followup on kubernetes-external secrets in that issue |
@spiffxp: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/milestone v1.22 |
Allow k8s-infra-prow-build-trusted to automatically deploy apps to aaa
Preferably using a service-account per app that grants it the same privileges that humans would have? I would rather avoid giving k8s-infra-prow-build-trusted cluster-admin access to
aaa
If we're comfortable doing this in a pinch, we can consider it
/wg k8s-infra
/kind feature
/area access
/area prow
/area cluster-infra
/priority important-longterm
The text was updated successfully, but these errors were encountered: