Releases: clastix/cluster-api-control-plane-provider-kamaji
Releases · clastix/cluster-api-control-plane-provider-kamaji
v0.13.0
v0.13.0
This tag was signed with the committer’s verified signature.
The key has expired.
prometherion
Dario Tranchitella
This minor release addresses the features tracked in the milestone v0.13.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.13.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.13.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.12.0 v0.13.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.13.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.13.0" TargetNamespace="kamaji-system"
v0.12.0
This minor release addresses the features tracked in the milestone v0.12.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.12.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.12.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.4 Already up to date
control-plane-kamaji kamaji-system ControlPlaneProvider v0.11.0 v0.12.0
cluster-api capi-system CoreProvider v1.8.4 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.12.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.12.0" TargetNamespace="kamaji-system"
v0.11.0
v0.11.0
This tag was signed with the committer’s verified signature.
The key has expired.
prometherion
Dario Tranchitella
This minor release addresses the features tracked in the milestone v0.11.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.11.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.11.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 v1.7.3
control-plane-kamaji kamaji-system ControlPlaneProvider v0.10.2 v0.11.0
cluster-api capi-system CoreProvider v1.5.0 v1.7.2
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.11.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.10.2" TargetNamespace="kamaji-system"
v0.10.2
v0.10.2
This tag was signed with the committer’s verified signature.
The key has expired.
prometherion
Dario Tranchitella
This patch release addresses the #117 reported bug to enable idiomatically feature gates.
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.10.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.10.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 v1.7.3
control-plane-kamaji kamaji-system ControlPlaneProvider v0.10.1 v0.10.2
cluster-api capi-system CoreProvider v1.5.0 v1.7.2
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.10.2
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.10.2" TargetNamespace="kamaji-system"
v0.10.1
v0.10.1
This tag was signed with the committer’s verified signature.
The key has expired.
prometherion
Dario Tranchitella
7125515
This commit was signed with the committer’s verified signature.
The key has expired.
prometherion
Dario Tranchitella
This patch release addresses the #116 reported bug.
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.10.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.10.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 v1.7.3
control-plane-kamaji kamaji-system ControlPlaneProvider v0.10.0 v0.10.1
cluster-api capi-system CoreProvider v1.5.0 v1.7.2
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.10.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.10.1" TargetNamespace="kamaji-system"
v0.10.0
v0.10.0
This tag was signed with the committer’s verified signature.
The key has expired.
prometherion
Dario Tranchitella
This minor release provides features tracked in the v0.10.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.10.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.10.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 v1.7.3
control-plane-kamaji kamaji-system ControlPlaneProvider v0.9.0 v0.10.0
cluster-api capi-system CoreProvider v1.5.0 v1.7.2
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.10.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.10.0" TargetNamespace="kamaji-system"
v0.9.0
v0.9.0
This tag was signed with the committer’s verified signature.
The key has expired.
prometherion
Dario Tranchitella
This minor release provides features tracked in the v0.9.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.9.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.9.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 v1.6.2
control-plane-kamaji kamaji-system ControlPlaneProvider v0.8.0 v0.9.0
cluster-api capi-system CoreProvider v1.5.0 v1.6.2
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.9.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.9.0" TargetNamespace="kamaji-system"
v0.8.0
v0.8.0
This tag was signed with the committer’s verified signature.
The key has expired.
prometherion
Dario Tranchitella
This minor release is addressing bugs and features tracked in the v0.8.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.8.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.8.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 v1.6.2
control-plane-kamaji kamaji-system ControlPlaneProvider v0.7.1 v0.8.0
cluster-api capi-system CoreProvider v1.5.0 v1.6.2
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.8.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.8.0" TargetNamespace="kamaji-system"
v0.7.1
v0.7.1
This tag was signed with the committer’s verified signature.
The key has expired.
prometherion
Dario Tranchitella
This patch release is addressing a bug tracked in the v0.7.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.7.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.7.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 v1.6.2
control-plane-kamaji kamaji-system ControlPlaneProvider v0.7.0 v0.7.1
cluster-api capi-system CoreProvider v1.5.0 v1.6.2
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.7.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.7.0" TargetNamespace="kamaji-system"
v0.7.0
v0.7.0
This tag was signed with the committer’s verified signature.
The key has expired.
prometherion
Dario Tranchitella
This patch release is addressing a bug tracked in the v0.7.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.7.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.7.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 v1.6.2
control-plane-kamaji kamaji-system ControlPlaneProvider v0.6.0 v0.7.0
cluster-api capi-system CoreProvider v1.5.0 v1.6.2
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.7.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.7.0" TargetNamespace="kamaji-system"