You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Cli Rollout as far as i remember from old reading of code , is not based on api(not rolling update of deployment) . It was replica set management on the client side . Not sure if that has changed recently
The rollout command was co-developed with the Deployment API. It was rolling-update that predates kubectl. Pause and resume patch the paused API field. https://github.com/kubernetes/kubernetes/blob/5b0d8d2ce118d44731c9eb4c52b285d676424e01/staging/src/k8s.io/api/apps/v1/types.go#L303 …
Deployment was started in Kubernetes 1.1, so yeah it predates KEPs by a few years. The code is indeed more abstract now that it used to be, but you can see the patch code (just not what is patched), here: https://github.com/kubernetes/kubernetes/blob/5b0d8d2ce118d44731c9eb4c52b285d676424e01/staging/src/k8s.io/kubectl/pkg/cmd/rollout/rollout_resume.go#L134 …
ah thanks, i was thinking more about "kubectl rolling-update" command , i could not find an official documentation but this https://jamesdefabia.github.io/docs/user-guide/kubectl/kubectl_rolling-update/ … . wonder why we never have pause for daemonset
It is documented on the deployment page: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/ …. I don't think I have ever seen usage data for the feature.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
