Ignition data too large when creating various CAPA Workload Clusters #3442
Labels
phoenix-size/l
provider/cluster-api-aws
Cluster API based running on AWS
team/phoenix
Team Phoenix
topic/private-clusters
Because of the amount of configuration we now have in our ignition data and the extra that is needed for private clusters (such as the proxy details) we've hit the limit for the file with MachinePools (that stores in a Kubernetes secret).
Error on MachinePool:
This is occurring on our test private CAPA cluster
goat
since the release of cluster-aws v0.75.0.The capa-private E2E test suite is currently failing because of this issue and has been disabled until it can be resolved.
Some notes:
The Control Plane nodes make use of S3 to temporarily store their ignition data as outlined in the documentation but it seems to not be implemented for MachinePools as far as we can tell. I have been unable to find any relevant issues upstream so we may be the first to hit this issue.
For reference:
The length of the ignition file on a capa private WC was - 17,368 characters
The length of the ignition file on a capa non-private WC was - 13,908 characters
Tasks
Related Slack thread
The text was updated successfully, but these errors were encountered: