Skip to content
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.

Add a Cassandra upgrade mechanism #352

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

wallrj
Copy link
Member

@wallrj wallrj commented 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: #257

Release note:

Navigator can now perform minor and patch upgrades of Cassandra clusters.

@jetstack-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: wallrj

Assign the PR to them by writing /assign @wallrj in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@wallrj wallrj mentioned this pull request May 9, 2018
@wallrj wallrj changed the title Add a Cassandra upgrade mechanism WIP: Add a Cassandra upgrade mechanism 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
…m the controlling pod and add those generic labels to the pod template and pod pilot selectors
@wallrj wallrj changed the title WIP: Add a Cassandra upgrade mechanism Add a Cassandra upgrade mechanism Jun 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants