You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 4, 2023. It is now read-only.
* 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: #257
Navigator supports the following changes to a Cassandra cluster:
192
192
193
193
* :ref:`create-cluster-cassandra`: Add all initially configured node pools and nodes.
194
+
* :ref:`minor-upgrade-cassandra`: Trigger a rolling upgrade of Cassandra nodes by increasing the minor and / or patch components of ``CassandraCluster.Spec.Version``.
194
195
* :ref:`scale-out-cassandra`: Increase ``CassandraCluster.Spec.NodePools[0].Replicas`` to add more C* nodes to a ``nodepool``.
195
196
196
197
Navigator does not currently support any other changes to the Cassandra cluster configuration.
The following configuration changes are not currently supported but will be supported in the near future:
202
203
203
-
* Minor Upgrade: Trigger a rolling Cassandra upgrade by increasing the minor and / or patch components of ``CassandraCluster.Spec.Version``.
204
204
* Scale In: Decrease ``CassandraCluster.Spec.NodePools[0].Replicas`` to remove C* nodes from a ``nodepool``.
205
205
206
206
The following configuration changes are not currently supported:
@@ -220,6 +220,19 @@ in order of ``NodePool`` and according to the process described in :ref:`scale-o
220
220
The order of node creation is determined by the order of the entries in the ``CassandraCluster.Spec.NodePools`` list.
221
221
You can look at ``CassandraCluster.Status.NodePools`` to see the current state.
222
222
223
+
.. _minor-upgrade-cassandra:
224
+
225
+
Minor Upgrade
226
+
~~~~~~~~~~~~~
227
+
228
+
If you increment the minor or patch number in ``CassandraCluster.Spec.Version``, Navigator will trigger a rolling update of the existing C* nodes.
229
+
230
+
C* nodes are upgraded serially, in order of NodePool and Pod ordinal, starting with the pod with the highest ordinal in the first NodePool.
231
+
232
+
`StatefulSet Rolling Updates <https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#rolling-updates>`_ describes the update process in more detail.
233
+
234
+
.. note:: Major version upgrades are not yet supported.
0 commit comments