Temporarily override the CAPI AWS provider image #1933
Conversation
…uster-api and other services
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: csrwng The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
hypershift-operator/main.go
Outdated
| ComponentImages: map[string]string{ | ||
| // TODO: Remove this override when we update CAPA to match the master branch of openshift/cluster-api-provider-aws | ||
| // Currently, this image points to CAPA in OCP release 4.12.0-ec.5 | ||
| "aws-cluster-api-controllers": "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:0fe3b95dad471e6840e8f38624fcd0ee6cbc92503460fe7f3503e640e13402d3", |
There was a problem hiding this comment.
Would it be possible to use a multi-arch image here rather than an x86 only image?
Ex: quay.io/openshift-release-dev/ocp-release:4.12.0-rc.3-multi
There was a problem hiding this comment.
Hey @bryan-cox yup, that makes sense, will update.
This allows OCP 4.13 clusters to work while we bump the CAPA dependency (and API version) in our code
csrwng
force-pushed
the
fix-capi-provider
branch
from
c5e7b02
to
9eb0b94
Compare
|
/lgtm |
|
@csrwng: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
What this PR does / why we need it:
This allows OCP 4.13 clusters to work while we bump the CAPA dependency (and API version) in our code
Checklist