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.

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

prepare prior to cordon/drain+upgrade #8

Closed
dweomer opened this issue Jan 24, 2020 · 0 comments · Fixed by #17
Closed

prepare prior to cordon/drain+upgrade #8

dweomer opened this issue Jan 24, 2020 · 0 comments · Fixed by #17
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@dweomer
Copy link
Contributor

dweomer commented Jan 24, 2020

Is your feature request related to a problem? Please describe.
Would like to (optionally) run a process that must exit successfully before invoking the (optional) cordon/drain and then moving on to the upgrade process.

Describe the solution you'd like
Add prepare "container spec" that looks a lot like the current upgrade spec.

Describe alternatives you've considered
n/a

Additional context
n/a

@dweomer dweomer changed the title upgrade job/pod precondition precondition container prior to invoking cordon/drain then upgrade Jan 24, 2020
@dweomer dweomer changed the title precondition container prior to invoking cordon/drain then upgrade precondition prior to invoking cordon/drain+upgrade Jan 24, 2020
@dweomer dweomer changed the title precondition prior to invoking cordon/drain+upgrade precondition prior to cordon/drain+upgrade Jan 24, 2020
@dweomer dweomer added the enhancement New feature or request label Jan 28, 2020
@dweomer dweomer added this to the v0.2.0 milestone Jan 29, 2020
@dweomer dweomer self-assigned this Jan 30, 2020
@dweomer dweomer changed the title precondition prior to cordon/drain+upgrade prepare prior to cordon/drain+upgrade Jan 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants