3 ms·
Other posters have already commented on this but, if you are not using deployments (or at least, replication controllers), stop what you are doing right away an
by outworlder 9y ago
Other posters have already commented on this but, if you are not using deployments (or at least, replication controllers), stop what you are doing right away and fix that. Otherwise you lose one of the biggest advantages of k8s.
- brianwawok 9y agoDeployments are key. One annoyance is now some of the lower units feel more clunky. Is there roadmap to say let you do a stateful set as a Deployment? Obviously a bit tricky and rolling deploy could never surge...
- TheSwordsman 9y agoWRT to StatefulSets I assume you are talking about the fact they are immutable (minus a few fields)? If so, the hack we've applied for StatefulSets is to delete the StatefulSet with `--cascade=false`. This keeps the Pods of the StatefulSet online, but removes the StatefulSet itself. We can then deploy the StatefulSet with the new configuration vlaues, and manually delete the Pods one-by-one to have the changes be applied. Graceful: Nope. Needs Improvement: For sure Gets the job done: Yep!
- brianwawok 9y agoHum I have deployed a SS with just delete and create. No need for a cascade flag. Maybe that is the default? But yah like I said, not as nice as deploying a deployment.