Docker Provider - Force to Use Quay.io Clusterctl image #642
Labels
enhancement
New feature or request
priority/critical
Items critical to be implemented, usually by the next release
Milestone
Problem description (if applicable)
In order to fix issue when uplifting to CAPI v0.4.2 (#518), we need the Docker provider to use the krm supporting clusterctl: 0.3.22 version instead of latest. The reason is when uplifting to CAPI v0.4.2, the clusterctl krm image is build using clusterctl:0.4.2 binary, which may be causing Zuul to fail during docker provider test.
Proposed change
The proposed approach (but not limited to) is to create a strategic merge on the docker-test-site level for the clusterctl executor.
The text was updated successfully, but these errors were encountered: