Coding Rollout Pause/Resume/Rollback
See original GitHub issueIt’s unclear to me how I would go about acting on a deployment rollout. I’m trying to figure out how to Pause, Resume and Rollback a rollout.
Initially I thought I could Pause/Resume by patching the deployment.Spec.Paused field as seen below. But this does not work.
var depClient = GetClient().DeploymentsV1();
var dep = await depClient.Get(deploymentName);
await depClient.Update(dep.Metadata.Name, patch =>
{
patch.Replace(d => d.Spec.Paused, true);
});
I also have no idea how I would Rollback. Any ideas on this area of the api?
Issue Analytics
- State:
- Created 5 years ago
- Comments:19 (13 by maintainers)
Top Results From Across the Web
Issues · tintoy/dotnet-kube-client
Add helpers for generating kubectl-style resource annotations. #62 opened on Jan 29, 2019 by tintoy · Coding Rollout Pause/Resume/Rollback.
Read more >K8s Deployments & Replicasets — Part2
K8s deployment is an abstraction layer for the pods. The deployment K8s ... One can also pause, resume, rollback, etc., with deployments.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yep, looks like I was right (in general, at least):
https://unofficial-kubernetes.readthedocs.io/en/latest/concepts/workloads/controllers/deployment/#revision-history-limit
Whoa, I was unaware of the --v option. Nice! In playing with it for a few minutes, does this make it easy for you to map in your head the k8s api call to objects in your library? It was not obvious to me how that mapping works.
I will take a look as soon as i can, though my attention has been redirected at other areas for a bit. I do need to get back to this as soon as I can. Totally appreciate the pointer to this option! Oh, and thanks for continuing to build a nice abstraction layer over the api, sooo appreciated!