-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
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
oci supported #6405
oci supported #6405
Conversation
adriengentil
commented
Jun 5, 2024
•
edited by openshift-ci
bot
Loading
edited by openshift-ci
bot
- NO-ISSUE: rename docker image for postgres 12 as latest tag disappeared (NO-ISSUE: rename docker image for postgres 12 as latest tag disappeared #6116)
- MGMT-17354: Update CBO to support dual stack SNO hub deploying an IPv6 spoke (MGMT-17354: Update CBO to support dual stack SNO hub deploying an IPv6 spoke #6113)
- NO-ISSUE: Bump OCP versions: 4.15, 4.11 (NO-ISSUE: Bump OCP versions: 4.15, 4.11 #6118)
- Update RHTAP references (NO-ISSUE: Update RHTAP references #6117)
- MGMT-17367: Use ICSP in install-config for older OCP releases (MGMT-17367: Use ICSP in install-config for older OCP releases #6125)
- MGMT-17361: Changing the addition of configuration release images to run when the instance becomes leader instead of skipping if it not (MGMT-17361: Changing the addition of configuration release images to run when the instance becomes leader instead of skipping if it not #6115)
- MGMT-17369: Add multi-arch release images to as well when setting only_latest=true in .../openshift-versions (MGMT-17369: Add multi-arch release images to as well when setting "only_latest=true" in ".../openshift-versions" #6119)
- Revert "MGMT-16980: Change the default value of ENABLE_SKIP_MCO_REBOOT to false (OCPBUGS-29818: Spoke will not boot after agent install with error "Failed to mount /sysroot #6011)" (Revert "MGMT-16980: Change the default value of ENABLE_SKIP_MCO_REBOOT to false (#6011)" #6139)
- NO-ISSUE: Add doc for iPXE HTTP (NO-ISSUE: Add doc for iPXE HTTP #6146)
- OCPBUGS-31631: Deploy dual stack with IPv6 on top of bond/vlan fails (OCPBUGS-31631: Deploy dual stack with IPv6 on top of bond/vlan fails #6149)
- NO-ISSUE: replace minio quay.io image repository (NO-ISSUE: replace minio quay.io image repository #6151)
- MGMT-17438: bugfix, make sure ODF and LVM requirements do not change if MCE is not selected (MGMT-17438: bugfix, make sure ODF and LVM requirements do not change if MCE not selected #6150)
- NO-ISSUE: Bump OCP versions: 4.15, 4.14, 4.12 (NO-ISSUE: Bump OCP versions: 4.15, 4.14, 4.12 #6157)
- MGMT-17412: Change fallbck behavior when error occuring in OpenShift Release Syncer - if there are release images already in the DB, continue using the stale data instead of failing / truncating the table (MGMT-17412: Change fallbck behavior when error occuring in OpenShift Release Syncer #6145)
- Update RHTAP references (NO-ISSUE: Update RHTAP references #6148)
- MGMT-17489: Fix disconnected capi tests (MGMT-17489: Fix disconnected CAPI tests #6163)
- NO-ISSUE: Prevent false positive host connectivity (NO-ISSUE: Prevent false positive host connectivity #6162)
- MGMT-17181: Add a LocalClusterImportController (MGMT-17180: Add a LocalClusterImportController #6079)
- MGMT-17414: Adding new requirements for LVM on 4.16 (MGMT-17414: Changing requirements for LVM on 4.16 #6165)
- NO-ISSUE: Bump OCP versions: 4.16, 4.15, 4.12, 4.14, 4.13 (NO-ISSUE: Bump OCP versions: 4.16, 4.15, 4.12, 4.14, 4.13 #6199)
- MGMT-17518: Bump x/net to 0.24.0 to mitigate CVE-2023-45288 (MGMT-17518: Bump x/net to 0.24.0 to mitigate CVE-2023-45288 #6176)
- MGMT-17468: Use x86_64 over amd64 and arm64 over aarch64 for CPU architecture of both release and OS images to comply with ABI current behavior (MGMT-17468: Use x86_64 over amd64 and arm64 over aarch64 for CPU architecture of both release and OS images to comply with ABI current behavior #6190)
- MGMT-17513: Change the latest release image retrieved in GetReleaseImage using major.minor OpenShift version to latest non-beta release image if exists, or latest beta release image otherwise (MGMT-17513: Change the latest release image retrieved in GetReleaseImage using major.minor OpenShift version to latest non-beta release image if exists, or latest beta release image otherwise #6185)
- MGMT-17313: Create day 2 BMH and Machine for control plane nodes (MGMT-17313: Create day 2 BMH and Machine for control plane nodes #6142)
- MGMT-17365: Add support for setting agent labels in BMH as annotations (MGMT-17365: Add support for setting agent labels in BMH as annotations #6124)
- MGMT-17503: Fix the cpu architectures retrieved in ../openshift-versions endpoint (MGMT-17503: Fix the cpu architectures retrieved in ../openshift-versions endpoint #6184)
- MGMT-17412: Change fallbck behavior when error occuring in OpenShift Release Syncer - if there are release images already in the DB, continue using the stale data instead of failing / truncating the table (MGMT-17412: Change fallbck behavior when error occuring in OpenShift Release Syncer #6145) (MGMT-17515: Fix the CPU architecture query for in GetReleaseImage to having the necessary CPU architecture in the list and the list must be of size one to exclude multi architecture release images #6186)
- MGMT-17558: Allow installation on iSCSI volume (MGMT-17558: Allow installation on iSCSI volume #6218)
- NO-ISSUE: Change only-latest api response to compare versions according to pre-release suffix as well instead of just base version (NO-ISSUE: Change only-latest api response to compare versions according to pre-release suffix as well instead of just base version #6209)
- OCPBUGS: Bump x/net to 0.24.0 to mitigate CVE-2023-45288 (api go.mod) (MGMT-17518: Bump x/net to 0.24.0 to mitigate CVE-2023-45288 (api go.mod) #6212)
- MGMT-17620: Change the way release images are handled in RestAPI flow to retrieve multiarch release image in case a multi-arch OpenShift version, single-arch requested and it exist. (MGMT-17620: Change the way multi-arch release images are handled in RestAPI flow #6227)
- Update RHTAP references (NO-ISSUE: Update RHTAP references (master) #6181)
- NO-ISSUE: Update OKD images to 4.16 (NO-ISSUE: Update OKD images to 4.16 #6231)
- MGMT-17413: Change pull secret validation on register/update cluster/infraenv to run only against the required images (MGMT-17413: Change pull secret validation on register/update cluster/infraenv to run only against the required images #6158)
- Move to rhel9, decouple from cli image (CORS-2750: Move to rhel9, decouple from cli image #5792)
- NO-ISSUE: Fix hypershift destroy in CI test script (NO-ISSUE: Fix hypershift destroy in CI test script #6246)
- NO-ISSUE: Bump OCP versions: 4.13, 4.12, 4.14, 4.15 (NO-ISSUE: Bump OCP versions: 4.13, 4.12, 4.14, 4.15 #6250)
- MGMT-17697: Change L3 connectivity to use connected addresses instead of majority groups (MGMT-17697: Change L3 connectivity to use connected addresses instead of majority groups #6252)
- NO-ISSUE: Bump OCP versions: 4.16 (NO-ISSUE: Bump OCP versions: 4.16 #6254)
- OCPBUGS-31733: Remove CPMS manifest for vsphere platform (OCPBUGS-31733: Remove CPMS manifest for vSphere platform #6239)
- NO-ISSUE: Bump OCP versions: 4.13, 4.15, 4.14 (NO-ISSUE: Bump OCP versions: 4.13, 4.15, 4.14 #6259)
- MGMT-17523: Fail when OS images CPU architecture is missing instead of giving it default value (MGMT-17523: Fail when OS images CPU architecture is missing instead of giving it default value #6256)
- MGMT-17194: Ensure releaseImage is not tag based when mirror registry enabled. (MGMT-17194: Ensure releaseImage is not tag based when mirror registry enabled. #6260)
- Revert "MGMT-17194: Ensure releaseImage is not tag based when mirror registry enabled. (MGMT-17194: Ensure releaseImage is not tag based when mirror registry enabled. #6260)" (Revert "MGMT-17194: Ensure releaseImage is not tag based when mirror registry enabled. (#6260) #6268)
- NO-ISSUE: Add openshift-edge-bot as an OWNER in order to run konflux pipelines on its PRs (NO-ISSUE: Add openshift-edge-bot as an OWNER #6255)
- MGMT-17764: Update the latest image search functionality in the RestAPI flow to correctly compare pre-release versions (MGMT-17764: Update the latest image search functionality in the RestAPI flow to correctly compare pre-release versions #6276)
- MGMT-17194: Ensure that we improve error messages for mirror registry tagged images (MGMT-17194: Ensure that we improve error messages for mirror registry tagged images #6266)
- MGMT-17775: Ensure that patch manifest filenames are consistent and correct (MGMT-17775: Ensure that patch manifest filenames are consistent and correct. #6289)
- Use openshift-install binary for releases >= 4.16 (OCPBUGS-33227: Use openshift-install binary for releases >= 4.16 #6304)
- MGMT-17866: Assisted service change for F5 DNS load balancer (MGMT-17866: Assisted service change for F5 DNS load balancer #6339)
- OCPBUGS-34181: Don't use the statically linked installer if FIPS is enabled (OCPBUGS-34181: Don't use the statically linked installer if FIPS is enabled #6355)
- MGMT-17811: Do not create local cluster namespace (MGMT-17811: Do not create local cluster namespace #6314)
- NO-ISSUE: [master] Bump OCP versions: 4.16, 4.14, 4.12, 4.15 (NO-ISSUE: [master] Bump OCP versions: 4.16, 4.14, 4.12, 4.15 #6358)
- MGMT-17770: Split ignition handling file (MGMT-17770: Split ignition handling file #6283)
- NO-ISSUE: Add 4.16 rhcos images (NO-ISSUE: Add 4.16 rhcos images #6326)
- MGMT-17850: Bump k8s.io modules to v0.29 (MGMT-17850: Bump k8s.io modules to v0.29 #6345)
- MGMT-17618: NMStateConfig interfaces presence should be validated (MGMT-17618: NMStateConfig interfaces presence should be validated #6305)
- fix: dev-requirements.txt to reduce vulnerabilities (NO-ISSUE: [Snyk] Security upgrade requests from 2.31.0 to 2.32.0 #6348)
- OCPBUGS-31727: Invalid Pull-Secret when using password which contains a colon character (OCPBUGS-31727: Invalid Pull-Secret when using password which contains a colon character #6258)
- fix: deploy/olm-catalog/requirements.txt to reduce vulnerabilities (NO-ISSUE: [Snyk] Security upgrade requests from 2.31.0 to 2.32.0 #6346)
- MGMT-17896: Add separate Dockerfile for assisted-service with an el8 base (MGMT-17896: Add separate Dockerfile for assisted-service with an el8 base #6347)
- MGMT-17823: Cleanup the install manifest generator (MGMT-17823: Cleanup the install manifest generator #6361)
- MGMT-17700: Assign none platform node-ips based on connected addresses and etcd restrictions (MGMT-17700: Assign none platform node-ips based on connected addresses and etcd restrictions #6257)
- MGMT-17849: escape '%' in agent.service proxy urls (MGMT-17849: escape '%' in agent.service proxy urls #6356)
- NO-ISSUE: wait for lso to be installed (NO-ISSUE: wait for LSO to be installed #6374)
- Deprecate and disable support for OCM offline token (NO-ISSUE: Deprecate and disable support for OCM offline token #6307)
- MGMT-17848: Assisted service should not format multipath devices (MGMT-17848: Assisted service should not format multipath devices #6360)
- MGMT-9589: Distribute sdist package to PyPI in addition to wheel one (MGMT-9589: Distribute sdist package to PyPI in addition to wheel one #6294)
- MGMT-17901: Add mirror registries to the list of ignored registires for pull secret validation (MGMT-17901: Ignore mirror registries during pull secret validation #6371)
- MGMT-17763: Setting Machine network CIDR is forbidden" error is only present on cluster updates (MGMT-17763: Setting Machine network CIDR is forbidden" error is only present on cluster updates #6359)
- Use the EL8 assisted-service image when requested by annotation (MGMT-17898: Use the EL8 assisted-service image when requested by annotation #6349)
- NO-ISSUE: [master] Bump OCP versions: 4.14, 4.15, 4.13, 4.16 (NO-ISSUE: [master] Bump OCP versions: 4.14, 4.15, 4.13, 4.16 #6378)
- MGMT-17353: Debug pod left in ImagePullBackOff after install in disconnected environment (MGMT-17353: Debug pod left in ImagePullBackOff after install in disconnected environment #6332)
- MGMT-17901: Add the exteranl registry to the list of ignored registires for pull secret validation instead of the mirror one (MGMT-17901: Add the external registry to the list of ignored registries for pull secret validation instead of the mirror one #6377)
- MGMT-17353: Debug pod left in ImagePullBackOff after install in disconnected environment (MGMT-17353: Debug pod left in ImagePullBackOff after install in disconnected environment #6333)
- Use the static installer for 4.16 nightlies when not FIPS-enabled (MGMT-18010: Use the static installer for 4.16 nightlies when not FIPS-enabled #6386)
- MGMT-18059: Mark OCI as supported integration
…ed (openshift#6116) Signed-off-by: Riccardo Piccoli <rpiccoli@redhat.com>
…6 spoke (openshift#6113) * Update CBO dependency to 82df158cd2e9 This includes openshift/cluster-baremetal-operator#380 which is required for a single stack ipv6 cluster to be deployed from a dual-stack hub when the hub is a single node. https://issues.redhat.com/browse/MGMT-17354 * Update call to GetIronicIPs to use a provisioning pointer This was changed in openshift/cluster-baremetal-operator#380 Resolves https://issues.redhat.com/browse/MGMT-17354
Co-authored-by: danmanor <infrastructure-operator@redhat.com>
Co-authored-by: red-hat-konflux <123456+red-hat-konflux[bot]@users.noreply.github.com>
…ift#6125) Openshift releases earlier than 4.14 do not support the ImageDigestMirrorSet so configure ImageContentSources when building the install-config for these versions.
…run when the instance becomes leader instead of skipping if it not (openshift#6115)
…y_latest=true in .../openshift-versions (openshift#6119)
…T to false (openshift#6011)" (openshift#6139) This reverts commit 0eb0c73.
Plain HTTP is supported, and this adds doc on how to use it.
…penshift#6149) IPv6 L2 connectivity check uses nmap. nmap uses NDP (Network Discovery Protocol) to check L2 connectivty to IPv6 hosts. There are cases that NDP response does not arrive or it is not captured by nmap which means that the system assumes there is no connectivity to the host. However, there might be L3 connectivity (ping) to the same host. So change adds fallback for IPv6 L2 connectivity. In case there is failure in L2 connectivity to IPv6 host and success in L3 connecivity to the same host, the host is assumed connected on L2, providing that the remote address is part of the L2 subnet being checked.
Signed-off-by: Riccardo Piccoli <rpiccoli@redhat.com>
…if MCE is not selected (openshift#6150) Signed-off-by: Riccardo Piccoli <rpiccoli@redhat.com>
Co-authored-by: danmanor <infrastructure-operator@redhat.com>
…Release Syncer - if there are release images already in the DB, continue using the stale data instead of failing / truncating the table (openshift#6145)
Co-authored-by: red-hat-konflux <123456+red-hat-konflux[bot]@users.noreply.github.com>
Now that hypershift is compiled with CGO_ENABLED=1 the hypershift CLI fails with /lib64/libc.so.6: version `GLIBC_2.32' not found (required by hypershift) /lib64/libc.so.6: version `GLIBC_2.34' not found (required by hypershift) So instead we'll try to run it in a pod as we do for connected tests.
Hosts were incorrectly marked as connected to each other even if there were no IP address connections found.
Presently, we import The Local ACM Hub Cluster on the startup of assisted-service. This is causing issues with the finalizers on the ClusterDeployment and AgentClusterInstall objects that are created as part of this process. When a user attempts to delete the AgentServiceConfig, this will result in the assisted-service being taken down and this renders it unable to handle the finalizers on the AgentClusterInstall and ClusterDeployment. The remedy for this is to move the creation and deletion of these objects to an independent controller that will place a finalizer on AgentServiceConfig, this will allow the AgentClusterInstall and ClusterDeployment to be removed prior to removal of the service.
…6199) Co-authored-by: danmanor <infrastructure-operator@redhat.com>
…t#6176) The version bump is being performed to mitigate CVE-2023-45288
…itecture of both release and OS images to comply with ABI current behavior (openshift#6190)
…age using major.minor OpenShift version to latest non-beta release image if exists, or latest beta release image otherwise (openshift#6185)
…nshift#6142) https://issues.redhat.com/browse/MGMT-17313 Previously, only day 2 workers had BMH and Machines created for them. We want the same behavior for day 2 control plane nodes (added in https://issues.redhat.com/browse/MGMT-8578) so that their CSRs will be approved automatically.
openshift#6124) BMH is the custom resource that is used to add a new host. Agent on the other hand is created automatically when a host registers. Since there is a need to control agent labels the following agent label support was added: In order to add an entry that controls agent label, a new BMH annotation needs to be added. The annotation key is prefixed with the string 'bmac.agent-install.openshift.io.agent-label.'. The remainder of the annotation is considered the label key. The value of the annotation is identical to the agent label value. Note: agent labels cannot be deleted by usage of BMH annotations.
…Release Syncer - if there are release images already in the DB, continue using the stale data instead of failing / truncating the table (openshift#6145) (openshift#6186)
Open installation of OCP on iSCSI boot volume to all platforms. Remove `ip=ibft` from the kernel arguments as it prevent proper network configuration when several NICs are in use. RHCOS team recommend to leave DHCP configuration.
…ng to pre-release suffix as well instead of just base version (openshift#6209)
…openshift#6212) Bump x/net to 0.24.0 to mitigate CVE-2023-45288 (api go.mod) Forgot to deal with api/go.mod, this PR addresses that.
…penshift#6346) The following vulnerabilities are fixed by pinning transitive dependencies: - https://snyk.io/vuln/SNYK-PYTHON-REQUESTS-6928867 Co-authored-by: snyk-bot <snyk-bot@snyk.io>
…base (openshift#6347) * Add separate Dockerfile for assisted-service with an el8 base This is required to ensure that users have an option to install FIPS clusters for versions where the installer is linked against el8 crypto libraries. The resulting image will be deployed by the operator when the user indicates that clusters requiring the el8 libraries will be installed in FIPS mode (versions < 4.16). Resolves https://issues.redhat.com/browse/MGMT-17896 * Use a build arg to determine the base image Instead of a separate Dockerfile for the el8 image an single build arg will determine the base image.
* Use envconfig directly for release image mirror This is more clear if it's fetched directly from the ENV in the package rather than being set in main. * Remove ServiceBaseURL from ignition generator It's not used when running the installer * Remove ServiceIPs This was only ever used for the on-prem ISO which was never released as a product and was eventually removed. * Move ABI tls certs override into generator package This is only used in the generator package so it can be a part of its config directly rather than in main. * Remove auth handler from install config generator This was only used for the auth type and that isn't being used in the function that it is passed to. * Remove bonus interface ISOInstallConfigGenerator and InstallConfigGenerator were exactly the same * Stop saving failed cluster dirs The error handling here is incorrect (it was checking the error from the S3 upload) and to my knowledge no one has ever looked in this saved cluster directory to debug an issue.
…s and etcd restrictions (openshift#6257) When none platform is in use, if there is ambiguity in node-ip assignment, then incorrect assignment might lead to installation failure. This happens when etcd detects that the socket address from an etcd node does not match the expected address in the peer certificate. In this case etcd rejects such connection. Example: assuming two networks - net1 and net2. master node 1 has 1 address that belongs to net1. master node 2 has 2 addresses. one that belongs to net 1, and another that belongs to net 2 master node 3 has 1 address that belongs to net 1. If the selected node-ip of master node 2 belongs to net 2, then when it will create a connection with any other master node, the socket address will be the address that belongs to net 1. Since etcd expects it to be the same as the node-ip, it will reject the connection. This can be solved by node-ips selection that will not cause such a conflict. Node ips assignment should be done through ignition. To correctly set bootstrap ip, the machine-network for the cluster must be set to match the selected node-ip for that host. MGMT-17701: Add capability to calculate none platform node-ips based on L3 connected addresses and connectivity Calculate the node-ips for none platform cluster. Node ip calculation is actually calculation of the node-ip, hint, and cidr. Node-ip is the ip address that exists on the host that was selected as the node-ip. Hint is actually an IP address that does not exist on the host, but must belong to the subnet of the node-ip. Cidr is the subnet in cidr notation that the node-ip and hint belong to. Node-ip calculation is either done for all cluster hosts or none of them. MGMT-17702: Modify ignition to use calculated node-ips for none platform In order to set node-ip, ignition is modified. A file called /etc/default/nodeip-configuration contains the hint as was set by node-ip generation. In addition the bootstrap-ip is set in ignition as was set in node-ip generation. This is set as environment variable called "OPENSHIFT_INSTALL_BOOTSTRAP_NODE_IP". MGMT-17703: Modify machine-network based on calculated node-ips The etcd in boostrap uses he machine-network to set the IP address. Therefore during install-config generation the machine-network may be replaced by the cidr from the node-ip generation.
* Refactor ignition_file_contains_http_proxy unit test to use DescribeTable The change is done in order to avoid duplicate code. Signed-off-by: Alona Paz <alkaplan@redhat.com> * Expand ignition_file_contains_http_proxy to check agent.service proxy This commit expands the ignition_file_contains_http_proxy existing unit test to verify the agent.service proxy setting in the ignition file are correct. Signed-off-by: Alona Paz <alkaplan@redhat.com> * MGMT-17849: escape '%' in agent.service proxy urls The proxy url format is http://<user>:<password>@<ipaddr>:<port> The user and password may contain url escaped characters (starting with '%'). systemd rejects unknown '%' specifiers on unit configuration [1]. Therefore, agent.service proxy urls should escape '%' -> '%%' to avoid being rejected. Environment=HTTP_PROXY=http://usr%40name:passwd%5D@10.10.1.1:3128 should become Environment=HTTP_PROXY=http://usr%%40name:passwd%%5D@10.10.1.1:3128 [1] https://github.com/systemd/systemd/blob/a1b2c92d8290c76a29ccd0887a92ac064e1bb5a1/NEWS#L10 Signed-off-by: Alona Paz <alkaplan@redhat.com> * Add ignition_file_contains_asterisk_no_proxy as an entry to a similar test Signed-off-by: Alona Paz <alkaplan@redhat.com> --------- Signed-off-by: Alona Paz <alkaplan@redhat.com>
Currently or `ocm/client` package supports authentication to OCM using an offline token via the `OCM_SELF_TOKEN` environment variable. But the OCM team has deprecated this authentication mechanism and will remove it in the future. The alternative is to use a client identifier and client secret, which is what we use in the SaaS environment. This patch disables by default that support, and will make the server fail with an explicit error message if it is used. Users that really need to use it will need to explicitly enable it setting the `ACKNOWLEDGE_DEPRECATED_OCM_SELF_TOKEN` environment variable to `yes`. In that case the server will start, but a warning will be written to the log. Signed-off-by: Juan Hernandez <juan.hernandez@redhat.com>
…or pull secret validation (openshift#6371)
…present on cluster updates (openshift#6359) When a cluster is single stack and DHCP VIP allocation is off, the machine-network is calculated by selecting a host network that the VIPs belong to. So machine network update is forbidden in this case. This is undesirable for KubeAPI where the machine-network is specified in a custom resource. So this change allows machine-network update if the update arrived from KubeAPI (non interactive).
…shift#6349) A user should request the EL8 image when they are running in a FIPS-enabled cluster and intend to only install OCP versions <4.16. This can be done by setting the `agent-install.openshift.io/service-image-base` annotation to `el8` on the AgentServiceConfig resource Resolves https://issues.redhat.com/browse/MGMT-17898
…ft#6378) Co-authored-by: danmanor <infrastructure-operator@redhat.com>
…nnected environment (openshift#6332) Pass a flag in the installation command instructing the controller if notify reboots functionality is enabled. The flag is enabled only if kube-api is not enabled in the service
…es for pull secret validation instead of the mirror one (openshift#6377)
…nnected environment (openshift#6333) Fot day2 hosts the functionality is removed since we don't want to enable it for kube-api Revert "MGMT-15902: Trigger reboots for node event when day2 node moves to done (openshift#5648)" This reverts commit 652202c.
…enshift#6386) Previously this code would use the dynamic binary for 4.16 nighlies this change ensures all 4.16 releases will get the static binary when FIPS is not enabled. Resolves https://issues.redhat.com/browse/OCPBUGS-34701
Remove OCI from technology preview as it is now a supported integration.
PR needs rebase. 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-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adriengentil 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 |
@adriengentil: The following tests failed, say
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-sigs/prow repository. I understand the commands that are listed here. |