This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
Allow Cassandra database to be upgraded between minor and patch versions #257
Labels
Milestone
Comments
Closed
wallrj
added a commit
to wallrj/navigator
that referenced
this issue
Mar 7, 2018
* Add a NodePool.Status.Version attribute which has the lowest reported version from all the pilots in the pool. * Or nil, if the pilot failed to query its Cassandra database for its version. * Calculate an UpdateVersion action if the desired Cassandra version is higher than the version reported for a NodePool. * NodePools are upgraded one at a time. * Pods within a Nodepool are upgraded one at a time, using a rolling update strategy without any partitioning. * Upgrades are performed before any extra Nodepools are created and before nodepool scale out. Fixes: jetstack#257
wallrj
added a commit
to wallrj/navigator
that referenced
this issue
Mar 28, 2018
* Add a NodePool.Status.Version attribute which has the lowest reported version from all the pilots in the pool. * Or nil, if the pilot failed to query its Cassandra database for its version. * Calculate an UpdateVersion action if the desired Cassandra version is higher than the version reported for a NodePool. * NodePools are upgraded one at a time. * Pods within a Nodepool are upgraded one at a time, using a rolling update strategy without any partitioning. * Upgrades are performed before any extra Nodepools are created and before nodepool scale out. Fixes: jetstack#257
wallrj
added a commit
to wallrj/navigator
that referenced
this issue
May 8, 2018
* Add a NodePool.Status.Version attribute which has the lowest reported version from all the pilots in the pool. * Or nil, if the pilot failed to query its Cassandra database for its version. * Calculate an UpdateVersion action if the desired Cassandra version is higher than the version reported for a NodePool. * NodePools are upgraded one at a time. * Pods within a Nodepool are upgraded one at a time, using a rolling update strategy without any partitioning. * Upgrades are performed before any extra Nodepools are created and before nodepool scale out. Fixes: jetstack#257
wallrj
added a commit
to wallrj/navigator
that referenced
this issue
May 8, 2018
* Add a NodePool.Status.Version attribute which has the lowest reported version from all the pilots in the pool. * Or nil, if the pilot failed to query its Cassandra database for its version. * Calculate an UpdateVersion action if the desired Cassandra version is higher than the version reported for a NodePool. * NodePools are upgraded one at a time. * Pods within a Nodepool are upgraded one at a time, using a rolling update strategy without any partitioning. * Upgrades are performed before any extra Nodepools are created and before nodepool scale out. Fixes: jetstack#257
wallrj
added a commit
to wallrj/navigator
that referenced
this issue
May 9, 2018
* Add a NodePool.Status.Version attribute which has the lowest reported version from all the pilots in the pool. * Or nil, if the pilot failed to query its Cassandra database for its version. * Calculate an UpdateVersion action if the desired Cassandra version is higher than the version reported for a NodePool. * NodePools are upgraded one at a time. * Pods within a Nodepool are upgraded one at a time, using a rolling update strategy without any partitioning. * Upgrades are performed after Nodepools are created and after scale out. Fixes: jetstack#257
wallrj
added a commit
to wallrj/navigator
that referenced
this issue
May 9, 2018
* Add a NodePool.Status.Version attribute which has the lowest reported version from all the pilots in the pool. * Or nil, if the pilot failed to query its Cassandra database for its version. * Calculate an UpdateVersion action if the desired Cassandra version is higher than the version reported for a NodePool. * NodePools are upgraded one at a time. * Pods within a Nodepool are upgraded one at a time, using a rolling update strategy without any partitioning. * Upgrades are performed after Nodepools are created and after scale out. Fixes: jetstack#257
wallrj
added a commit
to wallrj/navigator
that referenced
this issue
May 9, 2018
* Add a NodePool.Status.Version attribute which has the lowest reported version from all the pilots in the pool. * Or nil, if the pilot failed to query its Cassandra database for its version. * Calculate an UpdateVersion action if the desired Cassandra version is higher than the version reported for a NodePool. * NodePools are upgraded one at a time. * Pods within a Nodepool are upgraded one at a time, using a rolling update strategy without any partitioning. * Upgrades are performed after Nodepools are created and after scale out. Fixes: jetstack#257
wallrj
added a commit
to wallrj/navigator
that referenced
this issue
Jun 7, 2018
* Add a NodePool.Status.Version attribute which has the lowest reported version from all the pilots in the pool. * Or nil, if the pilot failed to query its Cassandra database for its version. * Calculate an UpdateVersion action if the desired Cassandra version is higher than the version reported for a NodePool. * NodePools are upgraded one at a time. * Pods within a Nodepool are upgraded one at a time, using a rolling update strategy without any partitioning. * Upgrades are performed after Nodepools are created and after scale out. Fixes: jetstack#257
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We need an action to perform Cassandra version upgrades.
Upgrading to a new major version will need extra work and should be dissallowed for now.
/kind feature
The text was updated successfully, but these errors were encountered: