OCPEDGE-2463: fix(cluster): add local registry CA trust when MIRROR_IMAGES is enabled#1882
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @jaypoulz. Thanks for your PR. I'm waiting for a openshift-metal3 member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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-sigs/prow repository. |
0d96591 to
155a3d6
Compare
…MAGES is enabled IPv6 deployments default to MIRROR_IMAGES=true but the local registry CA trust patch only ran when ENABLE_LOCAL_REGISTRY was explicitly set. This caused CAPI to crashloop with x509 certificate errors when pulling from the local registry. This fix aligns the condition with the pattern used elsewhere in the codebase (utils.sh:150, 474, network.sh:206) to check if MIRROR_IMAGES is active, ensuring the trust bundle is added whenever the local registry is actually in use. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> Made-with: Cursor Agent: Auto
155a3d6 to
9a6aa66
Compare
|
Code Rabbit's review 🐰 |
|
/ok-to-test |
|
@jaypoulz: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
IPv6 deployments default to MIRROR_IMAGES=true but the local registry CA trust patch only ran when ENABLE_LOCAL_REGISTRY was explicitly set. This caused CAPI to crashloop with x509 certificate errors when pulling from the local registry.
This fix aligns the condition with the pattern used elsewhere in the codebase (utils.sh:150, 474, network.sh:206) to check if MIRROR_IMAGES is active, ensuring the trust bundle is added whenever the local registry is actually in use.