Clusterctl N-Infra Workflow

Workflow.md

We have an N-Infa-Setup like this:

Management group: capi-system/cluster-api, latest release available for the v1alpha3 API Version of Cluster API (contract):

NAME                     NAMESPACE                           TYPE                     CURRENT VERSION   NEXT VERSION
bootstrap-kubeadm        capi-kubeadm-bootstrap-system       BootstrapProvider        v0.3.6            Already up to date
control-plane-kubeadm    capi-kubeadm-control-plane-system   ControlPlaneProvider     v0.3.6            Already up to date
cluster-api              capi-system                         CoreProvider             v0.3.6            Already up to date
infrastructure-vsphere   capv-system-bremen                  InfrastructureProvider   v0.6.5            Already up to date
infrastructure-vsphere   capv-system-demo                    InfrastructureProvider   v0.6.5            Already up to date
infrastructure-vsphere   capv-system-refsaone                InfrastructureProvider   v0.6.5            Already up to date

Each of the Infra Providers has its own set of clusterctl config, as the vsphere credentials differ from provider to provider

Now we want to upgrade each provider converving its config, and i havent found a way to do so Trys were:

clusterctl upgrade plan --kubeconfig mgmt-capi-cluster-1.kubeconfig --config .cluster-api/clusterctl-bremen.yaml
clusterctl upgrade apply -i capv-system-demo/infrastructure-vsphere --kubeconfig mgmt-capi-cluster-1.kubeconfig --config .cluster-api/clusterctl-bremen.yaml

Which didnt work

could you attach the output of clusterctl upgrade plan?

clusterctl upgrade plan --kubeconfig mgmt-capi-cluster-1.kubeconfig --config .cluster-api/clusterctl-bremen.yaml
Checking new release availability...

Management group: capi-system/cluster-api, latest release available for the v1alpha3 API Version of Cluster API (contract):

NAME                     NAMESPACE                           TYPE                     CURRENT VERSION   NEXT VERSION
bootstrap-kubeadm        capi-kubeadm-bootstrap-system       BootstrapProvider        v0.3.6            Already up to date
control-plane-kubeadm    capi-kubeadm-control-plane-system   ControlPlaneProvider     v0.3.6            Already up to date
cluster-api              capi-system                         CoreProvider             v0.3.6            Already up to date
infrastructure-vsphere   capv-system-bremen                  InfrastructureProvider   v0.6.5            Already up to date
infrastructure-vsphere   capv-system-demo                    InfrastructureProvider   v0.6.5            Already up to date
infrastructure-vsphere   capv-system-refsaone                InfrastructureProvider   v0.6.5            Already up to date

You are already up to date!

You should try

1. first update the CAPI providers one by one

set env variables for CAPI providers

clusterctl upgrade apply  --management-group capi-system/cluster-api  --core capi-system/cluster-api:v0.3.6
clusterctl upgrade apply  --management-group capi-system/cluster-api  -b capi-kubeadm-bootstrap-system/bootstrap-kubeadm:v0.3.6
clusterctl upgrade apply  --management-group capi-system/cluster-api  -c capi-kubeadm-control-plane-system/control-plane-kubeadm:v0.3.6

2. then update the vsphere providers one by one (changing env variables for each instance)

set env variables for capv-system-bremen

clusterctl upgrade apply  --management-group capi-system/cluster-api  -i capv-system-bremen/infrastructure-vsphere:v0.6.5

set env variables for capv-system-demo

clusterctl upgrade apply  --management-group capi-system/cluster-api  -i capv-system-demo/infrastructure-vsphere:v0.6.5

set env variables for capv-system-refsaone

clusterctl upgrade apply  --management-group capi-system/cluster-api  -i capv-system-refsaone/infrastructure-vsphere:v0.6.5