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.

Sign up for GitHub

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

Jump to bottom

Grant staging groups access to see container vulnerabilties #715

Closed
thockin opened this issue Apr 3, 2020 · 12 comments
Closed

Grant staging groups access to see container vulnerabilties #715

thockin opened this issue Apr 3, 2020 · 12 comments
Labels
area/artifacts Issues or PRs related to the hosting of release artifacts for subprojects lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@thockin
Copy link
Member

thockin commented Apr 3, 2020

To get vuln info we need to grant role "Container Analysis Occurrences Viewer".

I see 2 paths:

  1. Make a group which holds all the staging groups. Every new group has to be added there.
  2. Just grant every group that role on k8s-artifacts-prod
@spiffxp spiffxp added the area/artifacts Issues or PRs related to the hosting of release artifacts for subprojects label Apr 28, 2020
@spiffxp
Copy link
Member

spiffxp commented Apr 28, 2020

related: #803

@spiffxp
Copy link
Member

spiffxp commented Apr 28, 2020

Near as I can tell this hasn't been done yet. We're talking about roles/containeranalysis.occurrences.viewer I assume.

@thockin
Copy link
Member Author

thockin commented Apr 28, 2020 via email

@spiffxp
Copy link
Member

spiffxp commented May 27, 2020

Ask PSC, we think this isn't secret information but let's confirm before moving with option 2

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 25, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 24, 2020
@thockin
Copy link
Member Author

thockin commented Sep 24, 2020

/lifecycle frozen
/remove-lifecycle stale
/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Sep 24, 2020
@spiffxp
Copy link
Member

spiffxp commented Jan 21, 2021

/milestone v1.21

@k8s-ci-robot k8s-ci-robot added this to the v1.21 milestone Jan 21, 2021
@spiffxp spiffxp added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jan 22, 2021
@spiffxp
Copy link
Member

spiffxp commented Apr 15, 2021

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.21 milestone Apr 15, 2021
@spiffxp
Copy link
Member

spiffxp commented Apr 15, 2021

/remove-priority important-soon
/priority backlog

@k8s-ci-robot k8s-ci-robot added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Apr 15, 2021
@spiffxp
Copy link
Member

spiffxp commented Jul 16, 2021

/close
We've disabled automated scanning, ref: #1963

@k8s-ci-robot
Copy link
Contributor

@spiffxp: Closing this issue.

In response to this:

/close
We've disabled automated scanning, ref: #1963

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/artifacts Issues or PRs related to the hosting of release artifacts for subprojects lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@spiffxp @thockin @k8s-ci-robot @fejta-bot