Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker Provider - Force to Use Quay.io Clusterctl image #642

Closed
lb4368 opened this issue Sep 22, 2021 · 3 comments
Closed

Docker Provider - Force to Use Quay.io Clusterctl image #642

lb4368 opened this issue Sep 22, 2021 · 3 comments
Assignees
Labels
enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release
Milestone

Comments

@lb4368
Copy link

lb4368 commented Sep 22, 2021

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.

apiVersion: airshipit.org/v1alpha1
kind: GenericContainer
metadata:
  name: clusterctl
  labels:
    airshipit.org/deploy-k8s: "false"
spec:
  type: krm
  image: localhost/clusterctl:latest #  replace by e.g., quay.io/airshipit/clusterctl:eb9ac97ce207542e1e4d3b363963bfc5f0847096
  hostNetwork: true
@lb4368 lb4368 added enhancement New feature or request triage Needs evaluation by project members labels Sep 22, 2021
@shon-phand
Copy link
Contributor

I can work on this, please assign it to me

@lb4368
Copy link
Author

lb4368 commented Sep 22, 2021

Comment from @sshiba

Also make sure CAPI manifests are pinned to v1apha3. See error from Zuul airship-airshipctl-gate-script-runner-docker below:

#clusterctl -v5 init --kubeconfig /home/zuul/.airship/kubeconfig-158207872 --kubeconfig-context ephemeral-cluster --core=cluster-api:v0.4.2 --bootstrap=kubeadm:v0.4.2 --control-plane=kubeadm:v0.4.2 --infrastructure=docker:v0.3.11
Using configuration File="/workdir/.cluster-api/clusterctl.yaml"
Installing the clusterctl inventory CRD
Creating CustomResourceDefinition="providers.clusterctl.cluster.x-k8s.io"
Fetching providers
Using Override="core-components.yaml" Provider="cluster-api" Version="v0.4.2"
Using Override="bootstrap-components.yaml" Provider="bootstrap-kubeadm" Version="v0.4.2"
Using Override="control-plane-components.yaml" Provider="control-plane-kubeadm" Version="v0.4.2"
Using Override="infrastructure-components.yaml" Provider="infrastructure-docker" Version="v0.3.11"
Using Override="metadata.yaml" Provider="cluster-api" Version="v0.4.2"
Using Override="metadata.yaml" Provider="bootstrap-kubeadm" Version="v0.4.2"
Using Override="metadata.yaml" Provider="control-plane-kubeadm" Version="v0.4.2"
Using Override="metadata.yaml" Provider="infrastructure-docker" Version="v0.3.11"
Error: current version of clusterctl is only compatible with v1alpha4 providers, detected v1alpha3 for provider infrastructure-docker

@shon-phand
Copy link
Contributor

@mattmceuen mattmceuen added priority/critical Items critical to be implemented, usually by the next release and removed triage Needs evaluation by project members labels Sep 29, 2021
@mattmceuen mattmceuen added this to the v2.1 milestone Sep 29, 2021
airshipbot pushed a commit that referenced this issue Oct 8, 2021
This KRM function will contain clusterctl binary with version
0.3.x for backward compatibility while the main one will move
forward with 0.4.x releases.

Change-Id: Iba167be074c07a20701ed45c4b2ccf38ddb2185a
Signed-off-by: Ruslan Aliev <raliev@mirantis.com>
Related-To: #647
Related-To: #642
Relates-To: #650
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority/critical Items critical to be implemented, usually by the next release
Projects
None yet
Development

No branches or pull requests

3 participants