Closed relyt0925 closed 1 year ago
Is only release image going to be multi-arch or even the individual components also will be a fat manifest so that any cluster wide daemonsets deployed for the infra will run smoothly on different architectures.
@relyt0925 - so is the request here to have OCP release images leverage fat manifests? Or can we do this in the Armada registry?
Prototype can be done in IBM registries.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle stale
There is an enhancement proposal created for publishing the multi-arch fat manifest release images here - https://github.com/openshift/enhancements/pull/1014 and also there are few release images published here - https://multi.ocp.releases.ci.openshift.org
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle stale
Now oc command also enabled to mirror the multi-arch images easily from the quay repo to any other repositories, e.g:
$ oc adm release mirror --from=quay.io/openshift-release-dev/ocp-release@sha256:4f368662af3bc46fb7c58327c7e07b4520119380bee4d6875c3fffbba8e2cb3b --to=icr.io/openshift-release-dev/ocp-release --keep-manifest-list --max-per-registry=32
Warning: the default reading order of registry auth file will be changed from "${HOME}/.docker/config.json" to podman registry config locations in the future version of oc. "${HOME}/.docker/config.json" is deprecated, but can still be used for storing credentials as a fallback. See https://github.com/containers/image/blob/main/docs/containers-auth.json.5.md for the order of podman registry config locations.
warning: An image was retrieved that failed verification: unable to verify sha256:1889075049eda7cd9646de074164844522a972a2aa238816a82c2cb76db49ff8 against keyrings: verifier-public-key-redhat
info: Mirroring 172 images to icr.io/openshift-release-dev/ocp-release ...
Warning: the default reading order of registry auth file will be changed from "${HOME}/.docker/config.json" to podman registry config locations in the future version of oc. "${HOME}/.docker/config.json" is deprecated, but can still be used for storing credentials as a fallback. See https://github.com/containers/image/blob/main/docs/containers-auth.json.5.md for the order of podman registry config locations.
icr.io/
openshift-release-dev/ocp-release
blobs:
quay.io/openshift-release-dev/ocp-release sha256:fa7d3d3fed5d2fc0d5c4b1cb4c1111b2ddb338b467c6d28bec0d7c0f2be2eee5 1.75KiB
.........
..........
info: Mirroring completed in 43m10.92s (17.94MB/s)
Success
Update image: icr.io/openshift-release-dev/ocp-release:4.11.0-0.nightly-multi-2022-07-06-015348-x86_64
Mirror prefix: icr.io/openshift-release-dev/ocp-release
To use the new mirrored repository to install, add the following section to the install-config.yaml:
imageContentSources:
- mirrors:
- icr.io/openshift-release-dev/ocp-release
source: quay.io/openshift-release-dev/ocp-release
- mirrors:
- icr.io/openshift-release-dev/ocp-release
source: quay.io/openshift-release-dev/ocp-v4.0-art-dev
To use the new mirrored repository for upgrades, use the following to create an ImageContentSourcePolicy:
apiVersion: operator.openshift.io/v1alpha1
kind: ImageContentSourcePolicy
metadata:
name: example
spec:
repositoryDigestMirrors:
- mirrors:
- icr.io/openshift-release-dev/ocp-release
source: quay.io/openshift-release-dev/ocp-release
- mirrors:
- icr.io/openshift-release-dev/ocp-release
source: quay.io/openshift-release-dev/ocp-v4.0-art-dev
Release information using the oc adm command:
$ oc adm release info icr.io/openshift-release-dev/ocp-release:4.11.0-0.nightly-multi-2022-07-06-015348-x86_64
Warning: the default reading order of registry auth file will be changed from "${HOME}/.docker/config.json" to podman registry config locations in the future version of oc. "${HOME}/.docker/config.json" is deprecated, but can still be used for storing credentials as a fallback. See https://github.com/containers/image/blob/main/docs/containers-auth.json.5.md for the order of podman registry config locations.
Name: 4.11.0-0.nightly-multi-2022-07-06-015348
Digest:
Created: 2022-07-06T01:59:05Z
OS/Arch: linux/ppc64le
Manifests: 593
Metadata files: 1
Pull From: icr.io/openshift-release-dev/ocp-release
Release Metadata:
Version: 4.11.0-0.nightly-multi-2022-07-06-015348
Upgrades: <none>
Metadata:
release.openshift.io/architecture: multi
Component Versions:
kubernetes 1.24.0
machine-os 411.86.202207011902-0 Red Hat Enterprise Linux CoreOS
Images:
NAME DIGEST
agent-installer-api-server sha256:27917beada48515273d901c0708f19a7f8ea4c653bf716ae84b6b9881dd69066
agent-installer-csr-approver sha256:47ac1f47737e3c2df1e4651c7b1d2b3256de5529e3027206dacf348d13664d2a
agent-installer-node-agent sha256:e426e9062344885b3fd34d8af6c0e18653648faf22f5fe3e3c6c9c03cbfef077
agent-installer-orchestrator sha256:e7bbec234db1848a78934656828f4404bc774b75db4fd69937dbbf1f91351cd8
alibaba-cloud-controller-manager sha256:b9f4bd851c1727df88cad077568919b5c04e768cafa7a02a5003509f076fda1b
alibaba-cloud-csi-driver sha256:d30eacb0d371241fcfe9750e3800f5e2e0a6e1f3286e3e2f484dbed0a9311320
alibaba-disk-csi-driver-operator sha256:853d2a8418e4110baed08bc415acee39a92f78f3db05bf82df8eb9f8596f3f38
alibaba-machine-controllers sha256:435accbc3489c92deca58502010515046c6027c744a089fb5da05a9b03399007
apiserver-network-proxy sha256:78af37cc332ced08af7364ae8c164e65028771471047928a9ec431c18a49e683
aws-cloud-controller-manager sha256:4160d446cc43dd49360e5b303cc8714c2e6765cb983803087fb28a8ee3a72d0f
aws-cluster-api-controllers sha256:4457d19a10c37ccc4d575a76804c367442ad6ba3c3009044fa6953b46ebf31c3
aws-ebs-csi-driver sha256:364b7e52a4f95febec01c705df511f5a67d922d24744c83d6673447c08683f7a
aws-ebs-csi-driver-operator sha256:7cab5a3aca304494c073ffa1999664f7476392a9f1aee7d108a0cd984acc5bee
aws-machine-controllers sha256:25bfa56dc4e672116a7ea233b3c2b11575aadb77c141ff7556f7b34921e4fd34
aws-pod-identity-webhook sha256:2ee1e0eb394971c345e98ee6f3e88872e1be8c9f725d60aa84bf71ec68f7b9f0
azure-cloud-controller-manager sha256:b46ac6be399245a44da410079950fb7382af2f98eb9bd315bd6f584dea0c9849
azure-cloud-node-manager sha256:d7fe30928ad45d6d3349dfc00dedcab4580a8119c4ad1fdcbe9eed13b47c4c38
azure-cluster-api-controllers sha256:df528c3f798fa35771a3d55f165c07bac6250debc5f368462f5101d6939f6b67
azure-disk-csi-driver sha256:ba34be4cb7063775308583f670b9f1f43e430e2b7256a11bee8052d87935011a
azure-disk-csi-driver-operator sha256:15048badf1ec5b7ad2042771cd0d3478089f862019f82768e11f079f160488db
azure-file-csi-driver sha256:9300b67c38a3c552925b4e86c4ac0980adab514b39810ff8ed4789e5c2536b67
azure-file-csi-driver-operator sha256:b90d3ea290b5ef1d9770cf4ab14650c505e030dfe5deb1e174be9e4d09271a46
azure-machine-controllers sha256:cf99bc7ed24037697c9a6d7e68b9d2ffb5dbaa09d769cc41cc3d0d9f6aa9e112
baremetal-installer sha256:cdd4b94cc2e6c42015ef73cb4bf97eeaa5a26dc7ca05297fad30e1b56eeb6ea2
baremetal-machine-controllers sha256:7a1cd69c9de20e5340c7f10592b1d03b933106a68373595552965a217ef9e241
baremetal-operator sha256:a328c718da230e5cd8420515350a0662d3f066f7f626b10130c4120252dc9d79
baremetal-runtimecfg sha256:a1295b3368981af39f8e4802582bf2a7af4963093922cfe60bc062ec50b1b71f
cli sha256:281a557349318bacbb598cf0c14c91803caec1bf65db0a397084def97ce2a0cc
cli-artifacts sha256:b0974897b9ed24e753817914cd09e45f9cef55e9dcd37c56360fc701a08b5b26
cloud-credential-operator sha256:0fd1cea2218208b78a9d5a7f492466b7f293b9cc7b6ed14435f3329f62ca9177
cloud-network-config-controller sha256:5f1fbca68f989cd22c84fee9014fc65cec15917b9fb903f3703ba4a4afeb1fa3
cluster-authentication-operator sha256:74a1b9848b0155e0331cda46be47f058517d9d9eeb284e534995f24c17394130
cluster-autoscaler sha256:9e9554983a2b74bb68fd3540b1202be34fbb2c500617f42046f447a7373712a1
cluster-autoscaler-operator sha256:6282eca76ceb9fa94edd202611b740268d376184327de98221a2c0da9a393dc4
cluster-baremetal-operator sha256:501f7be1b035a4fb1b19b4f8e9e55d5d0426b3e2994404b31dd4e7c5bc5cca09
cluster-bootstrap sha256:a76052ecf4902b18e68437d52a45a9002328dc011f80ec22a2ac021702054f19
cluster-capi-controllers sha256:c8111b4de62339046b2705a41dea0af3fff06e91f62093a069641de008a08130
cluster-capi-operator sha256:57c3702aa1129b8468d92c8b5b0f8a049c6776791a1bc4f5410fe249628bbf18
cluster-cloud-controller-manager-operator sha256:b71d279cca4774a3369e917578230ee01cedd1c33b3747dbd1c89d55fab2e8e3
cluster-config-operator sha256:80350202de7c6e5f9515a19467ac92d2cddfadb95a53bbf7e0aa7f95f85503b8
cluster-csi-snapshot-controller-operator sha256:6efaa702c65d57a91f992223bd75b249c24749596651ba27d3f7e1ff3dd89e4d
cluster-dns-operator sha256:eee4221e68e5dbf7cad7b3a20d5638eae5e1a72bb3a200848cf482666bb257ee
cluster-etcd-operator sha256:732a7e775fe34feac5e4874d1e20973bbd64966e90b5b520658265f588c3de56
cluster-image-registry-operator sha256:1c7a2d71217f6ddd33b60efee624d9f57c8ff06bb69c5671e865cce31b55370f
cluster-ingress-operator sha256:b38b2d382bbc1c9b9d511de5464f11c5da4adae4c85923886ea7c32f2c7f2c49
cluster-kube-apiserver-operator sha256:bfa41c63d991c40c42ff6e59e5a8985e5fbc43ff4ba817c8bdecaaa574b518af
cluster-kube-cluster-api-operator sha256:826067995900ba018e4e65c8da578c5ceb2b245f72b4aec9eb7ffe169a2d7406
cluster-kube-controller-manager-operator sha256:c3a6bd9e2b7ed3aa9d4fa687c6fc5bc2f848c28bd762365e18f4d995753f9387
cluster-kube-scheduler-operator sha256:0633ff2c9f58ac00802a66ac593ae70d0347486f7caf1eef335900343559ead0
cluster-kube-storage-version-migrator-operator sha256:dca79c0b9ea20bab1e55bd7dfafc10425c18481849aa81f22df67c2f2fc753ba
cluster-machine-approver sha256:e0e181bff7ecf655278b5d23c17c2c2ef20fe9927dae538def1d234fc56f3faa
cluster-monitoring-operator sha256:2f1c926783c9d3a93a8d779928596cedcf75a2289c19b7eb4150803ef98c57f1
cluster-network-operator sha256:5417daaf40a4eee33c9a01cc698e52052dc005ff957da13f8525ae9a695c4515
cluster-node-tuning-operator sha256:163f2de4a2cabde49739ca05df0280891e598397e34f9c3f765ff2b1bf42857f
cluster-openshift-apiserver-operator sha256:008b97deb473956c5906e63dc7c65a7ca560289982d9a7b55f9cdd2b10dd4af8
cluster-openshift-controller-manager-operator sha256:b929bd2a4d441906557c351b5242f6e81e7115dd9f3adde6060634dec9a2302e
cluster-policy-controller sha256:ebb5f200179b15432f44cf1cb8aa0eadf8143bc4447139005eddaa220b4a687c
cluster-samples-operator sha256:483936fcfb626eda53b7046b481932f6cfdd43530dfbe8f841f0c99dbab97cea
cluster-storage-operator sha256:4d2ed2b1fbec7f2e623d10bb30192fdd9c87dca2e87eafaef61356809cc82f6e
cluster-update-keys sha256:1821c5f2a2929d9006e46a341d8b215782973aecade86ce8658a3563336c88c2
cluster-version-operator sha256:afb448f89e2c8986daaa7ce386d98f16de748e514d94095fe388c87e3a2d325d
configmap-reloader sha256:10b6e222a9704d00ea27ad196e299ba39e2d13d6bdc31a951cd6a2a345cc49b4
console sha256:26f9fa7b81c16097f1ed96c89350f0bd9978e1ed3dc6472de5bda59bf9d0cb2d
console-operator sha256:0ae34934e3ae5ebb2afcc678b2022e09665b7afd41caceb845f8cf4c251e2462
container-networking-plugins sha256:e1ff9cda7b5600d6dadf078eb30e6cb9abe0f78e17bb165ab0f777646319bf3d
coredns sha256:3fe8735ff80aef208dcc7899b5441683d8547e5c563356bf6ec2cfbc32329ad3
csi-driver-manila sha256:06c466a897592dd6760da869f17fddb66748878d4134bc48a174e805ec551cf5
csi-driver-manila-operator sha256:0befa8e5a0b92c61ba912143b009f1604c66f8faac01e529bd4fe3ce1ebbf1be
csi-driver-nfs sha256:74e6904f9ed8605a4b674d7cf66fe0e097e8ee6e1c16c653444518b5dd9b4338
csi-driver-shared-resource sha256:ba7704bcce8f46a712525343094cd5a6fa5b3eec4d0c2bec4d9a0b6e4aee65ff
csi-driver-shared-resource-operator sha256:c87556000cac9cbbefeab97aefee554492b7e140137da8a14f056d9153476bbd
csi-driver-shared-resource-webhook sha256:27cc7f9ebf5b68acf475f95bd6f701699e81a647042f84d63706b62dd4a6bab7
csi-external-attacher sha256:7b51cbd6a667597797ba27c844621bc0d24d2dfa9ca0682f9fa96bc80c179221
csi-external-provisioner sha256:a29c7f6c99ad6dd94e3c749c3ae5b100cb24ffa83cfaf89a84cbf14ace557dd5
csi-external-resizer sha256:cabbbc7e6c833accce4ebc58d90367d30c2185016f2d58e5b542d387d0f8748f
csi-external-snapshotter sha256:42e37ac08f3cd75c1de5502ab23ee73e669190c42887792584fa066f0d8cf341
csi-livenessprobe sha256:c23feff6bbf95838014803f10118c186b16eb998e37346bd9dd9129fa19cb0cc
csi-node-driver-registrar sha256:7cb46256bda6ba634273aa5275572790cc20fac84a4dca95443417e01906d5b3
csi-snapshot-controller sha256:5ea320a33bb8d3dee1862f49b7710e5fbdb179dd1608361f9b362814186cf9c1
csi-snapshot-validation-webhook sha256:b6e467a995e70e66bba914a692b34fad2140712e9deefcb21f8fbeb802468d32
deployer sha256:5875ea12ec965adf4dccbf6a6870ceb644bbe4ab60dcd58fb15e2317fb1fc159
docker-builder sha256:c0869b4dc84c29978e76d4e8f0d7daad860960f8bdd0fc8d137bee71a9312485
docker-registry sha256:3a922b31c2c22762580888d93d773249638dc380273307832f3b9ff7b3c2dd7a
driver-toolkit sha256:c024193b758e33f046cd7692dd2a8a712dc4fdc4244bf501c4a6e741212cb0d0
egress-router-cni sha256:9809ad50d3b75a170157506eac14f1841f8fc8f87d260f0d3d49349ade0b05ce
etcd sha256:91ebefeb7e9e84d623f58f4496e637645e05cd835e410c3219c4c5782e36b911
gcp-cloud-controller-manager sha256:39d9e2e2cbd1eedb974202e0382a8966f8a9d6bcb72426d9ab33b3af13d461cb
gcp-cluster-api-controllers sha256:7563366926280c74fc01b43745a47fcc1e6dec658b677f220535d76755ef1d8e
gcp-machine-controllers sha256:a1d643c236e6e7c86c863b52b0297e1a898efbe79a0cdd0c12d54b5ac435ed93
gcp-pd-csi-driver sha256:ca88efbff4c31ce4a984baec9bdd388cbed23b60bb6b8eee0701adde21ab9aba
gcp-pd-csi-driver-operator sha256:800b70ba8940fdfa5378920027702868cf152958a1dbae24a38e2e4ff1c71d54
haproxy-router sha256:15e6470632cd2c0cd1c789a537e6e076181ed11ba535719790b1d0ad0e209312
hyperkube sha256:695214e1c4a0ff28e646cc16d881d2dffe4715570fb270c961d05fd34da9a974
hypershift sha256:0300680605a063af34281a2b1af42e073f5c0c5fe79819c80d01332994a4a0c7
ibm-cloud-controller-manager sha256:8c19ac0ef116d10844e926255ad37b26168716d4c168264fabc6af8d864eaab9
ibm-vpc-block-csi-driver sha256:f281369c893f317011842d25c30d95d76399a01b09e684700da39549842d52ba
ibm-vpc-block-csi-driver-operator sha256:c498a1e8a1eea3bf59e891a2e43cb99e1b38c03e5376dcad25ca55ff3e8d5244
ibm-vpc-node-label-updater sha256:af239c590f4ca8d032d7b0c7fb1f59e63f1e25944ffb03f871710e3dcfe9ff58
ibmcloud-machine-controllers sha256:6003d2b99265e8b03029e4a92041d1151363cb190e3aff4b1c4fb4270493011e
insights-operator sha256:23c0bcce153596ea80e3a3946f7c4694364353fe8e4af2e326c7d68e7f04a2e5
installer sha256:91bed00fb484e011c1220fa96330f1e4d23d96bb92b7e00582436d23419e50f6
installer-artifacts sha256:dca4b9c490d7a2f0c4121b744d2078ebdf3986d889fa7728fc9340d264543d56
ironic sha256:724c5593cf57c3b0a96e16c77b88111750f2bd2690a46b6185a8d4ab5b7ac543
ironic-agent sha256:b34a227c5b513972c5a8866221d7ab70877c42c6a7308c0ee0c0ef693359171e
ironic-machine-os-downloader sha256:ca9f38f45122880016976c3e43b8645135ea61f4d6e1bd42e56979e770872021
ironic-static-ip-manager sha256:04ab936b6da53adc4f6dff851725197db34e4cea6057be02f4d81790d61b7a74
k8s-prometheus-adapter sha256:d22839af2c76b452b94e2cb089f8d3d957bf1402f4b9b786e35a69a1f4df4d89
keepalived-ipfailover sha256:061ac8d0564f50110efe5793f9ec5b958ac3b151a9924b389c2004e3344f7573
kube-proxy sha256:0f217e817688481cce6ea5fa4008c9a572b3a146dcf3b9e6dd78fe1bce9d7e56
kube-rbac-proxy sha256:0f1734b988caaa37e4aca554e4c974a3665d6101e7200997f9b3ea81484b7245
kube-state-metrics sha256:16f8528cdea2001308a8c49c3ea73b405b0142e44245a052934c18c6f29763e8
kube-storage-version-migrator sha256:76a526d2f206d3b7834340a73dbb8410d463a93c0992931262a1d049c2bd8f60
kuryr-cni sha256:7199f882ea35ad1419398560f3c6df1088ad897f05bb2042806467ecea3beee7
kuryr-controller sha256:f512a864ed3846fa06a8e8a4eccb2c8995804a21ead701e5339d5acf39253061
libvirt-machine-controllers sha256:b3d82f0780a4fdcbed5ea69c1ac035af350e6b3b47df828d93d29ea038c7bd94
machine-api-operator sha256:19eee279a191093f4a32c04564130817d12a77469765b7183aeafe89569f26f8
machine-config-operator sha256:ef8579ea6e007da9ed8e95772cfb238c77a660d2ba9aa69346a58908d9c7c422
machine-image-customization-controller sha256:d1ff032bd55a5ea29cf0165bb536ab65ff0fd0dd742dc5331965e2a2d3c3781c
machine-os-content sha256:36bad0f207e201e4e14452f95d4db09a143f2c20010dd3d3939d05ce8e2ecb19
machine-os-images sha256:1c3e1edbf78e8332a921df58fc22b62adc83fabfc3883063c05b38c733ae5d3e
multus-admission-controller sha256:7594b465baf7522da4dd878e4d06cbac94432b5547d1d25a8d3cf83c88412139
multus-cni sha256:76ca7e53add31e2d6ce471ea9485b9543e42f7a1e9f330c16c7d1c202db2f898
multus-networkpolicy sha256:69d33df8978297746051dfff00f5299bc09fba636fa419368335ff30c8d8413d
multus-route-override-cni sha256:a3ed5432f8a354361c03954a55892fbd727a1614a92f85edfa7afa48d2234e0f
multus-whereabouts-ipam-cni sha256:17ff2b57b1e0637eedb0a191926da80daf0eee0b3520aef85c34c016992b2d4f
must-gather sha256:a1c37a26688e76ab02c53529b8f99846f6feed2ef1c38ab19aec8ad859d421f4
network-interface-bond-cni sha256:f18a8abe36cd8b90ab33cdd3796822e47559a471fab397efe9e3e1beeb8f3973
network-metrics-daemon sha256:3913c8edd5cbb97f8ee9ca0e95d7d9a1c96d261f28f6239a57fb7ab0da4c2148
network-tools sha256:77171035483bc281ad76926d1d3f5854ce4d478bccec80a117db090a421618d3
nutanix-machine-controllers sha256:1e4d727a332c8ba95de6c2c918d034038514a1a2dc1fb43c53b6c1c0dd0fb23e
oauth-apiserver sha256:b2a0a99f01c034f12e9be606b54f01708c61ab44219a6df41c15e2602b319fc6
oauth-proxy sha256:78cceca8b240e3b65e9cb129d57d843183c073296b6956067fabd9ec33d291c6
oauth-server sha256:6ef162e2b727e6cca77f1a3302b897c753270bf82d394b888d0b14a31d44449d
oc-mirror sha256:504f05ca7fdd79e9b51fd1aeb8efe49bef7ef323ff9f57e004b53f4d8784fc65
openshift-apiserver sha256:bc5f104d687c7289c41047ad37201a9171751d287b18c843110079a25796a5d4
openshift-controller-manager sha256:ff5e52269354d7477d42a4d0e0e6bd3ef29b5ad3e2c245298e130ab5029833f0
openshift-state-metrics sha256:6b893888f7baf749b182e8df2762273c3b2a6bbb5ca56f662f205884285d3f25
openstack-cinder-csi-driver sha256:68b70a70ab18979b18e6ae90fa29092f63ac4c560880b90e7a37dfc512adde4a
openstack-cinder-csi-driver-operator sha256:7de01c8605cdd24f78da854b6c134f6843f95263e0e77b62ae3751132ed8bbda
openstack-cloud-controller-manager sha256:10e19be62831271cd7d3c7bb589824eff965ffe7bbe1b866711551b287d12bf8
openstack-machine-api-provider sha256:ad83b250ddacb235e6d506f34b9c688fc4f918282ecf0a6ae864be473f175249
openstack-machine-controllers sha256:a8c8161bb84d726b1b84df8f81fd26e12a76489edab8f9b1060b9fa37e650006
operator-lifecycle-manager sha256:08d9c92fae8270ae24e7b2d398bc5c7c896fdadaa50558ea8754ccf9792b7998
operator-marketplace sha256:dd68f44fff21fc26e35253388ee2a0cfa08b5ada5054d52f8dbd6c986ce5778f
operator-registry sha256:ab417b7f45790bd296fc28a930a3695fe931930b4fba742a20c76b362951d3ac
ovirt-csi-driver sha256:d439e61bd4c8b4dcc748340720cd2adab1bcf0beb0c64823c18f1d322566f73f
ovirt-csi-driver-operator sha256:060031403e5168cbf7aa1b82f5e4ee97b31e6cce0809ca1c4498d2b8ac229547
ovirt-machine-controllers sha256:cbbdb4a69bf568a62a8cca648d67a01715c2d51e816a08d2479da2cc79273110
ovn-kubernetes sha256:906619183cd7d936ef8d8db29d105e91d12b05144a847f87ed1131bc960de9ba
pod sha256:9e8a1095753a6758bb5ed5f83dbc4f62abebad80949538d6334cbd39e6a49797
powervs-cloud-controller-manager sha256:1baa31b58685d4a73aad656438a8d143db9a46d9b8d4e6f29a647a2fef8fd67e
powervs-machine-controllers sha256:06810c5c9cd9d95130bf9e26b4708ff8dcbac27fd131568e7100ab6fbff2c457
prom-label-proxy sha256:8496be21525939cbbba7e8346934d8341bd56042630c3d39334e90ccb87d39f8
prometheus sha256:880fc438258e6ecea8a40da82d9ebf50cf77ced3ea4a4e59bdbaab251f08a3c4
prometheus-alertmanager sha256:5a0ddbbd0da27536750d1a2da15eaefe52f09b87e4fab183c5235bc9869a6fe3
prometheus-config-reloader sha256:dab2f010f8375291b1bcf49e30187397580a7aa61eb5d6d277c6a26d8390932b
prometheus-node-exporter sha256:9b0680c06fa501bae7f6a2715156f249a7a3ce201a3d5f722d77d4e909c198d3
prometheus-operator sha256:2b4c1711ecbaed25b1a8db95842ab028e16b9948520f585e8cd5eff0276a9568
prometheus-operator-admission-webhook sha256:5f2f2bde97effc1f567aec83d55e0323e5e027048bcf9881bf2321425aefdeea
sdn sha256:14930a3cd92d3cf0eec9bd46ae5c8b9cab0786bb832bfea33bf453c6106b98de
service-ca-operator sha256:b9e27d5ac7d4e9e28d952bca1d8a762500703d51d9dc084aec605292747e256e
telemeter sha256:ea62cebd9d40c1bc317e16f10c08c83a94c48c0b9694bcbf8b689a37d0dc731d
tests sha256:bd2b2f79a77903973c99f68745dfae3bf153812866675c5d128a022658841c95
thanos sha256:6d0811a5f63d738726f09173896046b6353e5be703796131a69954365ffecbb4
tools sha256:5e673b18ee85b14ed164f3b75cf58d5a83ced937c9d76d9494cff5971d862a12
vsphere-cloud-controller-manager sha256:0d315221eef79e970186e19d25a55c41e776e566561f517f03e00664d0122e8a
vsphere-cluster-api-controllers sha256:f066f17258f6043a4648cca39ce4a32557063473a1735cff193c0399629bfc51
vsphere-csi-driver sha256:7384884e2bcab2aea2a152c1dce00c4b1ece92d14f1bf7466d2f4b3ad84aa2cb
vsphere-csi-driver-operator sha256:5fb605ff2f7feaf9682a7c0d4f217c9fc7e643b938a41c64e74f5e290bda02d4
vsphere-csi-driver-syncer sha256:6fc5ea5e92fda07c33a96a0e6d73b964841f0e0f8e4c8cf858b6eb42c48f556d
vsphere-problem-detector sha256:de728ef5cb5b2d8006414dacdb767816420a8db05db17ca3d9cd11df61a56415
docker manifest command to print the manifest
$ docker manifest inspect icr.io/openshift-release-dev/ocp-release:4.11.0-0.nightly-multi-2022-07-06-015348-x86_64
{
"schemaVersion": 2,
"mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
"manifests": [
{
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"size": 1583,
"digest": "sha256:1889075049eda7cd9646de074164844522a972a2aa238816a82c2cb76db49ff8",
"platform": {
"architecture": "amd64",
"os": "linux"
}
},
{
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"size": 1583,
"digest": "sha256:e5c64dbcc739e8c47503100f0fe754b3d186be0c5ed852e09024c76abeff9424",
"platform": {
"architecture": "ppc64le",
"os": "linux"
}
},
{
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"size": 1583,
"digest": "sha256:848d3adc60c426ac40b8e458b78e6aa8e2f15ad7bb70d815a574e28d0bddd74a",
"platform": {
"architecture": "s390x",
"os": "linux"
}
},
{
"mediaType": "application/vnd.docker.distribution.manifest.v2+json",
"size": 1583,
"digest": "sha256:01c1987b828d24bc82d54f701fb19c98df6e9d6fa297bb8fe4e086d4ce8eb262",
"platform": {
"architecture": "arm64",
"os": "linux"
}
}
]
}
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
@openshift-bot: Closing this issue.
There's a few critical steps to this: 1) The power/Z functional equivalent of every image in the release payload needs to be built appropriately. This will form the link to that architecture in the multiarch image. 2) A sample registry path should be setup like registry.ng.bluemix.net/armadamultiarch (it exists from previous experiments with the power/Z team). In this registry: the team should handle first cloning the existing release images for power/Z/and x86_64 to unique images with unique tags. 3) Next need to properly link all images into a general multi-arch manifest to where a multiarch image could be referenced and then when pulled at runtime on a node it will be able to select the appropriate x86_64 image or power image. For more details on that see: https://www.docker.com/blog/multi-arch-build-and-images-the-simple-way/
This is critical in order to support a split control plane where the nodes holding master components are x86_64 and the workers joining that cluster are power based. Without this: there will be no potential for a split control plane.
Ultimately the desired outcome is laying the groundwork for instead of using a release image like
A release image would be used like
And through the multiarch CRI support you would successfully be able to have a split control plane where x86 images are used control plane side and power/z images are used for the power/z nodes that make up the cluster.