Handle clusterctl move
issue with AWSMachinePools
#1280
Labels
area/kaas
Mission: Cloud Native Platform - Self-driving Kubernetes as a Service
blocked-upstream
kind/task
provider/cluster-api-aws
Cluster API based running on AWS
topic/capi
See upstream issue: kubernetes-sigs/cluster-api-provider-aws#3624
It's currently not possible to run
clusterctl move
against a cluster that hasAWSMachinePools
that have been reconciled. Thespec.awsLaunchTemplate.rootVolume.deviceName
property is populated when the Launch Template is created in AWS but the admission webhook on the target cluster enforces this to not be set on creation.Manual intervention can work around this by removing the
deviceName
property (it isn't reconciled again post-creation) which would then allowclusterctl move
to perform correctly. For not we'll need to handle this in mc-bootstrap.Long-term an API change is needed in CAPA, as tracked by the above linked issue.
The text was updated successfully, but these errors were encountered: