v0.20.0

Full Changelog: v0.19.0...v0.20.0

⚠️ Breaking Changes!

Starting from v0.20.0, the Kamaji Control Plane Provider adopted the Cluster API v1beta2 contract by bumping its KamajiControlPlane and KamajiControlPlaneTemplate API versions to v1alpha2.

Previously created clusters with < v0.20.0 (thus, v1beta1 Cluster API contract) will not be reconciled by this release.

To support CLASTIX's commitment to delivering production-grade open-source software, we are offering a Stable Release Channel for the Cluster API Control Plane Provider for Kamaji.

The Stable Release Channel provides resource conversion capabilities for clusters created with previous Cluster API contracts,
allowing operators to seamlessly transition from v1beta1 to v1beta2.
This ensures that production environments can be upgraded without disruption,
giving platform teams the flexibility to migrate workloads on their own schedule while maintaining operational continuity.

Installation

Install the provider by ensuring it is in your ~/.cluster-api/clusterctl.yaml file as follows:

providers:
  - name: "kamaji"
    url: "https://github.com/clastix/cluster-api-control-plane-provider-kamaji/releases/v0.20.0/control-plane-components.yaml"
    type: "ControlPlaneProvider"

Once done, initialise it.

$: clusterctl init --control-plane kamaji
Fetching providers
Skipping installing cert-manager as it is already installed
Installing Provider="control-plane-kamaji" Version="v0.20.0" TargetNamespace="kamaji-system"

Upgrade

You can check the latest available release with clusterctl

clusterctl upgrade apply --contract v1beta2

The upgrade can be triggered as follows.

$: clusterctl upgrade apply --control-plane=kamaji-system/kamaji:v0.20.0
Performing upgrade...
Scaling down Provider="control-plane-kamaji" Version="" Namespace="kamaji-system"
Deleting Provider="control-plane-kamaji" Version="" Namespace="kamaji-system"
Installing Provider="control-plane-kamaji" Version="v0.19.0" TargetNamespace="kamaji-system"

v0.19.0

Full Changelog: v0.18.0...v0.19.0

Installation

Install the provider by ensuring it is in your ~/.cluster-api/clusterctl.yaml file as follows:

providers:
  - name: "kamaji"
    url: "https://github.com/clastix/cluster-api-control-plane-provider-kamaji/releases/v0.19.0/control-plane-components.yaml"
    type: "ControlPlaneProvider"

Once done, initialise it.

$: clusterctl init --control-plane kamaji
Fetching providers
Skipping installing cert-manager as it is already installed
Installing Provider="control-plane-kamaji" Version="v0.19.0" TargetNamespace="kamaji-system"

Upgrade

You can check the latest available release with clusterctl

$: clusterctl upgrade plan
Checking new release availability...

Latest release available for the v1beta1 API Version of Cluster API (contract):

NAME                      NAMESPACE                       TYPE                     CURRENT VERSION   NEXT VERSION
bootstrap-kubeadm         capi-kubeadm-bootstrap-system   BootstrapProvider        v1.10.1           v1.10.8
cluster-api               capi-system                     CoreProvider             v1.10.1           v1.10.8
control-plane-kamaji      kamaji-system                   ControlPlaneProvider     v0.18.0           v0.19.0
infrastructure-kubevirt   capk-system                     InfrastructureProvider   v0.1.10           Already up to date

You can now apply the upgrade by executing the following command:

clusterctl upgrade apply --contract v1beta1

The upgrade can be triggered as follows.

$: clusterctl upgrade apply --control-plane=kamaji-system/kamaji:v0.19.0
Performing upgrade...
Scaling down Provider="control-plane-kamaji" Version="" Namespace="kamaji-system"
Deleting Provider="control-plane-kamaji" Version="" Namespace="kamaji-system"
Installing Provider="control-plane-kamaji" Version="v0.19.0" TargetNamespace="kamaji-system"

v0.18.0

Full Changelog: v0.17.0...v0.18.0

Installation

Install the provider by ensuring it is in your ~/.cluster-api/clusterctl.yaml file as follows:

providers:
  - name: "kamaji"
    url: "https://github.com/clastix/cluster-api-control-plane-provider-kamaji/releases/v0.18.0/control-plane-components.yaml"
    type: "ControlPlaneProvider"

Once done, initialise it.

$: clusterctl init --control-plane kamaji
Fetching providers
Skipping installing cert-manager as it is already installed
Installing Provider="control-plane-kamaji" Version="v0.18.0" TargetNamespace="kamaji-system"

Upgrade

You can check the latest available release with clusterctl

$: clusterctl upgrade plan
Checking new release availability...

Latest release available for the v1beta1 API Version of Cluster API (contract):

NAME                      NAMESPACE                       TYPE                     CURRENT VERSION   NEXT VERSION
bootstrap-kubeadm         capi-kubeadm-bootstrap-system   BootstrapProvider        v1.10.1           v1.10.8
cluster-api               capi-system                     CoreProvider             v1.10.1           v1.10.8
control-plane-kamaji      kamaji-system                   ControlPlaneProvider     v0.17.0           v0.18.0
infrastructure-kubevirt   capk-system                     InfrastructureProvider   v0.1.10           Already up to date

You can now apply the upgrade by executing the following command:

clusterctl upgrade apply --contract v1beta1

The upgrade can be triggered as follows.

$: clusterctl upgrade apply --control-plane=kamaji-system/kamaji:v0.18.0
Performing upgrade...
Scaling down Provider="control-plane-kamaji" Version="" Namespace="kamaji-system"
Deleting Provider="control-plane-kamaji" Version="" Namespace="kamaji-system"
Installing Provider="control-plane-kamaji" Version="v0.18.0" TargetNamespace="kamaji-system"

v0.17.0

Full Changelog: v0.16.0...v0.17.0

Installation

Install the provider by ensuring it is in your ~/.cluster-api/clusterctl.yaml file as follows:

providers:
  - name: "kamaji"
    url: "https://github.com/clastix/cluster-api-control-plane-provider-kamaji/releases/v0.17.0/control-plane-components.yaml"
    type: "ControlPlaneProvider"

Once done, initialise it.

$: clusterctl init --control-plane kamaji
Fetching providers
Skipping installing cert-manager as it is already installed
Installing Provider="control-plane-kamaji" Version="v0.17.0" TargetNamespace="kamaji-system"

Upgrade

You can check the latest available release with clusterctl

$: clusterctl upgrade plan
Checking new release availability...

Latest release available for the v1beta1 API Version of Cluster API (contract):

NAME                      NAMESPACE                       TYPE                     CURRENT VERSION   NEXT VERSION
bootstrap-kubeadm         capi-kubeadm-bootstrap-system   BootstrapProvider        v1.10.1           v1.10.8
cluster-api               capi-system                     CoreProvider             v1.10.1           v1.10.8
control-plane-kamaji      kamaji-system                   ControlPlaneProvider     v0.16.0           v0.17.0
infrastructure-kubevirt   capk-system                     InfrastructureProvider   v0.1.10           Already up to date

You can now apply the upgrade by executing the following command:

clusterctl upgrade apply --contract v1beta1

The upgrade can be triggered as follows.

$: clusterctl upgrade apply --control-plane=kamaji-system/kamaji:v0.17.0
Performing upgrade...
Scaling down Provider="control-plane-kamaji" Version="" Namespace="kamaji-system"
Deleting Provider="control-plane-kamaji" Version="" Namespace="kamaji-system"
Installing Provider="control-plane-kamaji" Version="v0.17.0" TargetNamespace="kamaji-system"

v0.16.0

Full Changelog: v0.15.0...v0.16.0

Installation

Install the provider by ensuring it is in your ~/.cluster-api/clusterctl.yaml file as follows:

providers:
  - name: "kamaji"
    url: "https://github.com/clastix/cluster-api-control-plane-provider-kamaji/releases/v0.16.0/control-plane-components.yaml"
    type: "ControlPlaneProvider"

Once done, initialize it.

$: clusterctl init --control-plane kamaji
Fetching providers
Skipping installing cert-manager as it is already installed
Installing Provider="control-plane-kamaji" Version="v0.16.0" TargetNamespace="kamaji-system"

Upgrade

You can check the latest available release with clusterctl

$: clusterctl upgrade plan
Checking new release availability...

Latest release available for the v1beta1 API Version of Cluster API (contract):

NAME                      NAMESPACE                       TYPE                     CURRENT VERSION   NEXT VERSION
bootstrap-kubeadm         capi-kubeadm-bootstrap-system   BootstrapProvider        v1.10.1           v1.10.8
cluster-api               capi-system                     CoreProvider             v1.10.1           v1.10.8
control-plane-kamaji      kamaji-system                   ControlPlaneProvider     v0.15.0           v0.16.0
infrastructure-kubevirt   capk-system                     InfrastructureProvider   v0.1.10           Already up to date

You can now apply the upgrade by executing the following command:

clusterctl upgrade apply --contract v1beta1

The upgrade can be triggered as follows.

$: clusterctl upgrade apply --control-plane=kamaji-system/kamaji:v0.16.0
Performing upgrade...
Scaling down Provider="control-plane-kamaji" Version="" Namespace="kamaji-system"
Deleting Provider="control-plane-kamaji" Version="" Namespace="kamaji-system"
Installing Provider="control-plane-kamaji" Version="v0.14.0" TargetNamespace="kamaji-system"

v0.15.4

What's Changed

• feat(deps): bump github.com/spf13/pflag from 1.0.6 to 1.0.7 by @dependabot[bot] in #235
• feat(deps): bump sigs.k8s.io/cluster-api from 1.10.3 to 1.10.4 by @dependabot[bot] in #234
• feat(deps): bump github.com/onsi/gomega from 1.37.0 to 1.38.0 by @dependabot[bot] in #237
• chore(ci): bump docker/login-action from 3.4.0 to 3.5.0 by @dependabot[bot] in #241
• chore(ci): bump docker/metadata-action from 5.7.0 to 5.8.0 by @dependabot[bot] in #240
• feat: add support for DataStoreUsername by @synthe102 in #243
• chore(ci): bump actions/checkout from 4.2.2 to 5.0.0 by @dependabot[bot] in #242
• chore(ci): bump amannn/action-semantic-pull-request from 5 to 6 by @dependabot[bot] in #244

New Contributors

• @synthe102 made their first contribution in #243

Full Changelog: v0.15.3...v0.15.4

v0.15.3

What's Changed

• chore(ci): bump docker/build-push-action from 6.16.0 to 6.18.0 by @dependabot in #219
• feat(deps): bump sigs.k8s.io/cluster-api from 1.10.1 to 1.10.2 by @dependabot in #216
• feat(deps): bump sigs.k8s.io/controller-runtime from 0.20.4 to 0.21.0 by @dependabot in #218
• fix: enqueue after migration for reconciliation results by @prometherion in #223
• chore(ci): bump softprops/action-gh-release from 2.2.2 to 2.3.0 by @dependabot in #222
• chore(ci): bump softprops/action-gh-release from 2.3.0 to 2.3.2 by @dependabot in #224
• feat(docs): add kubevirt clusterclass template by @vriabyk in #221
• feat(deps): bump sigs.k8s.io/cluster-api from 1.10.2 to 1.10.3 by @dependabot in #229
• chore(ci): bump docker/setup-buildx-action from 3.10.0 to 3.11.1 by @dependabot in #228
• fix: prioritize InternalIP in kubelet-preferred-address-types by @parthyadav3105 in #231
• fix: limit ECR manager cache to TenantControlPlanes by @avorima in #232

New Contributors

• @vriabyk made their first contribution in #221
• @parthyadav3105 made their first contribution in #231

Full Changelog: v0.15.2...v0.15.3

v0.15.2

Full Changelog: v0.15.1...v0.15.2

v0.15.1

Full Changelog: v0.15.0...v0.15.1

v0.15.0

Full Changelog: v0.14.0...v0.15.0

Installation

Install the provider by ensuring it is in your ~/.cluster-api/clusterctl.yaml file as follows:

providers:
  - name: "kamaji"
    url: "https://github.com/clastix/cluster-api-control-plane-provider-kamaji/releases/v0.15.0/control-plane-components.yaml"
    type: "ControlPlaneProvider"

Once done, initialize it.

$: clusterctl init --control-plane kamaji
Fetching providers
Skipping installing cert-manager as it is already installed
Installing Provider="control-plane-kamaji" Version="v0.15.0" TargetNamespace="kamaji-system"

Upgrade

You can check the latest available release with clusterctl

$: clusterctl upgrade plan
Checking new release availability...

Latest release available for the v1beta1 API Version of Cluster API (contract):

NAME                      NAMESPACE                       TYPE                     CURRENT VERSION   NEXT VERSION
bootstrap-kubeadm         capi-kubeadm-bootstrap-system   BootstrapProvider        v1.8.5            Already up to date
control-plane-kamaji      kamaji-system                   ControlPlaneProvider     v0.14.0           v0.15.0
cluster-api               capi-system                     CoreProvider             v1.8.5            Already up to date

You can now apply the upgrade by executing the following command:

clusterctl upgrade apply --contract v1beta1

The upgrade can be triggered as follows.

$: clusterctl upgrade apply --control-plane=kamaji-system/kamaji:v0.15.0
Performing upgrade...
Scaling down Provider="control-plane-kamaji" Version="" Namespace="kamaji-system"
Deleting Provider="control-plane-kamaji" Version="" Namespace="kamaji-system"
Installing Provider="control-plane-kamaji" Version="v0.14.0" TargetNamespace="kamaji-system"