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

Infra turnup: Whoever creates the project is listed as Owner #299

Closed
thockin opened this issue Jul 10, 2019 · 6 comments · Fixed by #1859
Closed

Infra turnup: Whoever creates the project is listed as Owner #299

thockin opened this issue Jul 10, 2019 · 6 comments · Fixed by #1859
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone
v1.21

Comments

@thockin
Copy link
Member

thockin commented Jul 10, 2019

E.g. @dims created k8s-release-test-prod and is now an owner as his individual ID.

We should probably require (automatically via the scripts) that individuals remove themselves unless they are org-inherited.
@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 Oct 8, 2019
@cblecker
Copy link
Member

cblecker commented Oct 8, 2019

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 8, 2019
@thockin
Copy link
Member Author

thockin commented Dec 11, 2019

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Dec 11, 2019
@thockin thockin added the kind/bug Categorizes issue or PR as related to a bug. label Dec 11, 2019
@spiffxp spiffxp mentioned this issue Jan 21, 2021
Merged
@spiffxp spiffxp mentioned this issue Feb 25, 2021
Merged
@spiffxp
Copy link
Member

spiffxp commented Feb 25, 2021

Going to remove myself from all of the e2e projects via: #1722

A longer term fix would be to have ensure_project be smart about this. And maybe find a blanket way of enforcing that user:foo bindings should not exist at the project level or below

@spiffxp spiffxp mentioned this issue Mar 3, 2021
Merged
This was referenced Apr 6, 2021
Merged
Merged
@spiffxp
Copy link
Member

spiffxp commented Apr 7, 2021

@spiffxp
Copy link
Member

spiffxp commented Jul 16, 2021

/milestone v1.21

@k8s-ci-robot k8s-ci-robot added this to the v1.21 milestone Jul 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
v1.21
Development

Successfully merging a pull request may close this issue.

Refresh infra scripts to address audit followups, reduce output noise spiffxp/k8s.io
5 participants
@spiffxp @cblecker @thockin @k8s-ci-robot @fejta-bot