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

Updating boskos should actually update boskos #11956

Closed
Katharine opened this issue Mar 26, 2019 · 6 comments
Closed

Updating boskos should actually update boskos #11956

Katharine opened this issue Mar 26, 2019 · 6 comments
Assignees
@sebastienvas
Labels
area/boskos Issues or PRs related to code in /boskos kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@Katharine
Copy link
Member

Katharine commented Mar 26, 2019 •
edited

Currently updating boskos is a manual process that, potentially surprising, doesn't immediately do anything.
@Katharine Katharine added kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. area/boskos Issues or PRs related to code in /boskos priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Mar 26, 2019
@Katharine
Copy link
Member Author

/assign @sebastienvas

@stevekuznetsov
Copy link
Contributor

We're past 1.7 so I think this is just setting a field in the config? https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#updating-statefulsets

@fejta fejta mentioned this issue Mar 26, 2019
Closed
@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 Jun 24, 2019
@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 Jul 24, 2019
@sebastienvas sebastienvas mentioned this issue Jul 25, 2019
Merged
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

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.

@bobcatfish bobcatfish mentioned this issue Jan 21, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sebastienvas sebastienvas

Labels
area/boskos Issues or PRs related to code in /boskos kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@Katharine @stevekuznetsov @sebastienvas @k8s-ci-robot @fejta-bot