v0.6.0

This patch release is addressing a bug tracked in the v0.6.0 milestone.

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.6.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.6.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.6.1            Already up to date
control-plane-kamaji      kamaji-system                   ControlPlaneProvider     v0.5.0            v0.6.0
cluster-api               capi-system                     CoreProvider             v1.6.1            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.6.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.6.0" TargetNamespace="kamaji-system"

v0.5.0

This patch release is addressing a bug tracked in the v0.5.0 milestone.

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.5.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.5.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.5.0            Already up to date
control-plane-kamaji    kamaji-system                        ControlPlaneProvider     v0.4.2            v0.5.0
control-plane-kubeadm   capi-kubeadm-control-plane-system    ControlPlaneProvider     v1.5.0            Already up to date
cluster-api             capi-system                          CoreProvider             v1.5.0            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.5.0
Performing upgrade...
Scaling down Provider="control-plane-kamaji" Version="v0.4.2" Namespace="kamaji-system"
Deleting Provider="control-plane-kamaji" Version="v0.4.2" Namespace="kamaji-system"
Installing Provider="control-plane-kamaji" Version="v0.5.0" TargetNamespace="kamaji-system"

v0.4.2

This patch release is addressing a bug tracked in the v0.4.2 milestone.

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.4.2/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.4.2" 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.5.0            Already up to date
control-plane-kamaji    kamaji-system                        ControlPlaneProvider     v0.4.1            v0.4.2
control-plane-kubeadm   capi-kubeadm-control-plane-system    ControlPlaneProvider     v1.5.0            Already up to date
cluster-api             capi-system                          CoreProvider             v1.5.0            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.4.2
Performing upgrade...
Scaling down Provider="control-plane-kamaji" Version="v0.4.1" Namespace="kamaji-system"
Deleting Provider="control-plane-kamaji" Version="v0.4.1" Namespace="kamaji-system"
Installing Provider="control-plane-kamaji" Version="v0.4.2" TargetNamespace="kamaji-system"

v0.4.1

This patch release is addressing a bug tracked in the v0.4.1 milestone.

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.4.1/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.4.1" 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.5.0            Already up to date
control-plane-kamaji    kamaji-system                        ControlPlaneProvider     v0.4.0            v0.4.1
control-plane-kubeadm   capi-kubeadm-control-plane-system    ControlPlaneProvider     v1.5.0            Already up to date
cluster-api             capi-system                          CoreProvider             v1.5.0            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.4.1
Performing upgrade...
Scaling down Provider="control-plane-kamaji" Version="v0.4.0" Namespace="kamaji-system"
Deleting Provider="control-plane-kamaji" Version="v0.4.0" Namespace="kamaji-system"
Installing Provider="control-plane-kamaji" Version="v0.4.1" TargetNamespace="kamaji-system"

v0.4.0

This minor release is addressing new features and bugs tracked in the v0.4.0 milestone.

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.4.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.4.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.5.0            Already up to date
control-plane-kamaji    kamaji-system                        ControlPlaneProvider     v0.3.1            v0.4.0
control-plane-kubeadm   capi-kubeadm-control-plane-system    ControlPlaneProvider     v1.5.0            Already up to date
cluster-api             capi-system                          CoreProvider             v1.5.0            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.4.0
Performing upgrade...
Scaling down Provider="control-plane-kamaji" Version="v0.3.1" Namespace="kamaji-system"
Deleting Provider="control-plane-kamaji" Version="v0.3.1" Namespace="kamaji-system"
Installing Provider="control-plane-kamaji" Version="v0.4.0" TargetNamespace="kamaji-system"

v0.3.1

This patch release is addressing all the hotfixes and features tracked in the v0.3.1 milestone.

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.3.1/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.3.1" 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.5.0            Already up to date
control-plane-kamaji    kamaji-system                        ControlPlaneProvider     v0.3.0            v0.3.1
control-plane-kubeadm   capi-kubeadm-control-plane-system    ControlPlaneProvider     v1.5.0            Already up to date
cluster-api             capi-system                          CoreProvider             v1.5.0            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.3.1
Performing upgrade...
Scaling down Provider="control-plane-kamaji" Version="v0.3.0" Namespace="kamaji-system"
Deleting Provider="control-plane-kamaji" Version="v0.3.0" Namespace="kamaji-system"
Installing Provider="control-plane-kamaji" Version="v0.3.1" TargetNamespace="kamaji-system"

v0.3.0

This patch release is addressing all the hotfixes and features tracked in the v0.3.0 milestone.

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.3.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.3.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.5.0            Already up to date
control-plane-kamaji    kamaji-system                        ControlPlaneProvider     v0.2.0            v0.3.0
control-plane-kubeadm   capi-kubeadm-control-plane-system    ControlPlaneProvider     v1.5.0            Already up to date
cluster-api             capi-system                          CoreProvider             v1.5.0            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.3.0
Performing upgrade...
Scaling down Provider="control-plane-kamaji" Version="v0.2.2" Namespace="kamaji-system"
Deleting Provider="control-plane-kamaji" Version="v0.2.2" Namespace="kamaji-system"
Installing Provider="control-plane-kamaji" Version="v0.3.0" TargetNamespace="kamaji-system"

v0.2.2

This patch release is required for a reconciliation bug with Kamaji tracked with #39.

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.2.2/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.2.2" 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.5.0            Already up to date
control-plane-kamaji    kamaji-system                        ControlPlaneProvider     v0.2.0            v0.2.2
control-plane-kubeadm   capi-kubeadm-control-plane-system    ControlPlaneProvider     v1.5.0            Already up to date
cluster-api             capi-system                          CoreProvider             v1.5.0            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.2.2
Performing upgrade...
Scaling down Provider="control-plane-kamaji" Version="v0.2.1" Namespace="kamaji-system"
Deleting Provider="control-plane-kamaji" Version="v0.2.1" Namespace="kamaji-system"
Installing Provider="control-plane-kamaji" Version="v0.2.2" TargetNamespace="kamaji-system"

v0.2.1

This patch release is required for the support of CAPI v1.5.0, tracked with #37

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.2.1/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.2.1" 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.5.0            Already up to date
control-plane-kamaji    kamaji-system                        ControlPlaneProvider     v0.2.0            v0.2.1
control-plane-kubeadm   capi-kubeadm-control-plane-system    ControlPlaneProvider     v1.5.0            Already up to date
cluster-api             capi-system                          CoreProvider             v1.5.0            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.2.1
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.2.1" TargetNamespace="kamaji-system"

v0.2.0

This release comes with the support of further infrastructure providers, such as:

• KubeVirt support #12 @ruslanoman @prometherion
• Equinix/Packet support #23 @prometherion
• Metal³ support #7 @prometherion

For these providers, please, refer to the documentation available in the README.md file

Enhancements

• Tilt.dev support #19 @jds9090
• Automated release #14 @prometherion @ptx96

Hotfixes

• Cluster API Control Plane components should be labelled #21 @jds9090 @prometherion

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.2.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.2.0" TargetNamespace="kamaji-system"

Upgrade

You can check the latest available release with clusterctl

$: clusterctl upgrade plan
Checking cert-manager version...
Cert-Manager is already up to date

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.4.3            v1.4.4
control-plane-kamaji    kamaji-system                       ControlPlaneProvider   v0.1.0            v0.2.0
control-plane-kubeadm   capi-kubeadm-control-plane-system   ControlPlaneProvider   v1.4.3            v1.4.4
cluster-api             capi-system                         CoreProvider           v1.4.3            v1.4.4

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

clusterctl upgrade apply --contract v1beta1

The upgrade can be triggered as it follows.

$: clusterctl upgrade apply --control-plane=kamaji-system/kamaji:v0.2.0
Checking cert-manager version...
Cert-manager is already up to date
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.2.0" TargetNamespace="kamaji-system"