Skip to content
This repository has been archived by the owner on Feb 2, 2021. It is now read-only.

Use kubectl rollout status instead of looping #86

Open
alexellis opened this issue Mar 15, 2019 · 5 comments
Open

Use kubectl rollout status instead of looping #86

alexellis opened this issue Mar 15, 2019 · 5 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed skill/beginner

Comments

@alexellis
Copy link
Member

We can use the blocking command

Expected Behaviour

We can use kubectl rollout status instead of looping to see if various services / deployments have come up / are ready. Found this out via @zeerorg

Current Behaviour

We are looping in code.

Possible Solution

Try out kubectl rollout status instead for things like checking cert-manager / SealedSecrets / Tiller etc are up and ready for the next stage.
@alexellis alexellis added help wanted Extra attention is needed good first issue Good for newcomers skill/beginner labels Mar 15, 2019
@alexellis
Copy link
Member Author

@zeerorg WDYT?

@zeerorg
Copy link

zeerorg commented Mar 25, 2019

This could give a lot better command line experience with the tool.
I'll pick this up in a few days.

@zeerorg zeerorg mentioned this issue Mar 28, 2019
Closed
5 tasks
@zeerorg
Copy link

zeerorg commented Mar 28, 2019

Addressed by PR #89

@alexellis
Copy link
Member Author

alexellis commented Apr 6, 2019 •
edited

@zeerorg please use Derek to close this issue when #89 is merged.

@zeerorg
Copy link

zeerorg commented Apr 6, 2019

👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
good first issue Good for newcomers help wanted Extra attention is needed skill/beginner
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alexellis @zeerorg