Add cifmw_crc_additional_insecure_registries support#3938
Conversation
|
Skipping CI for Draft Pull Request. |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 5h 02m 14s |
vyzigold
force-pushed
the
allow-additional-insecure-registries
branch
from
c833b72 to
24509a6
Compare
vyzigold
force-pushed
the
allow-additional-insecure-registries
branch
3 times, most recently
from
7b5ab65 to
ef7048e
Compare
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 5h 40m 23s |
|
recheck |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 4h 04m 06s |
|
recheck |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 4h 29m 05s |
|
recheck |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 4h 13m 22s |
|
recheck to see if the whitebox test still fails |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 27m 53s |
vyzigold
force-pushed
the
allow-additional-insecure-registries
branch
from
ef7048e to
300a9ba
Compare
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 4h 13m 07s |
|
recheck |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 4h 06m 41s |
vyzigold
force-pushed
the
allow-additional-insecure-registries
branch
from
300a9ba to
8aca10d
Compare
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 48m 11s |
vyzigold
force-pushed
the
allow-additional-insecure-registries
branch
from
8aca10d to
3007a4d
Compare
vyzigold
force-pushed
the
allow-additional-insecure-registries
branch
from
4436ddc to
04574c5
Compare
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 4h 03m 05s |
…support Allow content-provider jobs to register additional insecure registries on the CRC node via zuul_return. This patches insecureRegistries in image.config.openshift.io/cluster and configures crio, paralleling the existing cifmw_crc_additional_allowed_registries mechanism. Generated-By: Claude-Code claude-opus-4-6 Signed-off-by: Jaromir Wysoglad <jwysogla@redhat.com>
vyzigold
force-pushed
the
allow-additional-insecure-registries
branch
from
04574c5 to
482e94d
Compare
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 28m 01s |
|
recheck |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 4h 00m 42s |
|
recheck |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 4h 06m 41s |
|
recheck |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: evallesp The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-merge-bot
Bot
merged commit 44c0639
into
openstack-k8s-operators:main
4 participants
Allow content-provider jobs to register additional insecure registries on the CRC node. This patches insecureRegistries in image.config.openshift.io/cluster and configures crio, paralleling the existing cifmw_crc_additional_allowed_registries mechanism.
This will be used with a custom content-provider job, which will build and provide images of sg-core, mysqld_exporter and prometheus-podman-exporter. The mechanism is generic and can be used with other custom content-provider jobs providing other non-operator, non-openstack-service images in the future.
Depends-On: #4003
Generated-By: Claude-Code claude-opus-4-6