We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We should either load the correct images, or just drop them from the file:
- name: quay.io/jetstack/cert-manager-cainjector:v1.12.2 loadBehavior: tryLoad - name: quay.io/jetstack/cert-manager-webhook:v1.12.2 loadBehavior: tryLoad - name: quay.io/jetstack/cert-manager-controller:v1.12.2 loadBehavior: tryLoad
I don't know if there is any upside to loading the images in the test-framework instead of just with regular pulls in CAPV
(Definitely no upside in loading the wrong images 😂)
The text was updated successfully, but these errors were encountered:
@fabriziopandini @chrischdi WDYT?
Sorry, something went wrong.
Let's drop it, as we won't be able to keep it up to date.
/assign
We should propably also drop the ones for CAPI or implement the go marker thing for these too:
- name: registry.k8s.io/cluster-api/cluster-api-controller:v1.7.1 loadBehavior: tryLoad - name: registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.7.1 loadBehavior: tryLoad - name: registry.k8s.io/cluster-api/kubeadm-control-plane-controller:v1.7.1 loadBehavior: tryLoad
fabriziopandini
Successfully merging a pull request may close this issue.
We should either load the correct images, or just drop them from the file:
I don't know if there is any upside to loading the images in the test-framework instead of just with regular pulls in CAPV
(Definitely no upside in loading the wrong images 😂)
The text was updated successfully, but these errors were encountered: