Enterprise: Upgrade the Management Cluster CAPI Components
Upgrade the CAPI Components on the Management cluster.
For a Pre-provisioned air-gapped environment only, ensure you have uploaded the artifacts.
For air-gapped environments, ensure you have created to air-gapped bundle correctly: Upgrade: For Air-gapped Environments Only
Upgrade the CAPI Components
New versions of DKP come pre-bundled with newer versions of CAPI, newer versions of infrastructure providers, or new infrastructure providers. When using a new version of the DKP CLI, upgrade all of these components first.
If you are running on more than one management cluster, you must upgrade the CAPI components on each of these clusters.
Ensure your dkp
configuration references the management cluster where you want to run the upgrade by setting the KUBECONFIG
environment variable, or using the --kubeconfig
flag, in accordance with Kubernetes conventions.
Execute the upgrade command for the CAPI components.
If you created CAPI components using flags to specify values, use those same flags during Upgrade to preserve existing values while setting additional values.
Refer to dkp create cluster aws for flag descriptions for
--with-aws-bootstrap-credentials
and--aws-service-endpoints
Refer to the HTTP section for details: Create CAPI Components with HTTP/HTTPS Proxy Settings
dkp upgrade capi-components
The output resembles the following:
✓ Upgrading CAPI components
✓ Waiting for CAPI components to be upgraded
✓ Initializing new CAPI components
If the upgrade fails, review the prerequisites section and ensure that you’ve followed the steps in the DKP Upgrade overview. Furthermore, ensure you have adhered to the Prerequisites at the top of this page.