-
We are attempting to gather more information on a flexible and simpler approach to rolling upgrades and also single binary syncs. This approach involves versioning the application struct (and potentia…
-
**What happened:**
The issue has been described in https://gitlab.com/sylva-projects/sylva-core/-/issues/1595
During rolling upgrades, control-plane node machine is removed from etcd cluster as …
-
### Enhancement Description
- One-line enhancement description (can be used as a release note): Respect PodTopologySpread after rolling upgrades
- Kubernetes Enhancement Proposal: https://github.c…
-
# Support rolling upgrades to enable security
Currently it is impossible to upgrade a non-secured cluster to a secured cluster due to the need to enable TLS. We would like to enable a way for clust…
-
This is a tracker for our epic to make sure rolling restarts are graceful and no connection gets handled ungracefully.
Unfortunately, at this point we use services that publish unready endpoints and …
-
https://botbot.me/freenode/weavenetwork/2015-02-18/?msg=32237468&page=1
> Any thoughts on how I may perform a rolling update of weave without taking the whole cluster down?
-
### Summary
The Cosmos SDK upgrade process has been that validators either need to use cosmovisor, be present at the time of the upgrade or have a third party tool in order to start the new binary wh…
-
**Is your feature request related to a problem? Please describe.**
Kibana does not support rolling upgrades per https://www.elastic.co/guide/en/kibana/current/upgrade-standard.html. Support rolling…
-
After upgrading to v1.2.3 and having `rollingDeploy=true`, I see that rolling updates are no longer performed in the usual order:
1. Historical
2. MMs
3. Broker
4. Overlord
5. Coordinator
6. R…
-
This isn't an issue, but I thought it may be of use to you; we forked your Elasticsearch states a while back and just released an automated rolling restart/upgrade to go with it: https://github.com/v…