Migrate ocp-e2e-ovn-agent-remote-libvirt-multi-z-z to VPN (orange zone) for 4.17-4.22#76332
Conversation
…e) for 4.17-4.22 - Switch cluster_profile from libvirt-s390x-1/2 to libvirt-s390x-vpn - Use openshift-e2e-libvirt-vpn workflow for orange zone connectivity - Add intranet capability and USE_EXTERNAL_DNS for VPN environment - Preserve agent installer and existing env (ETCD_DISK_SPEED, NODE_TUNING, etc.) - No changes to 4.23 or 5.0 configs
openshift-ci
bot
added
do-not-merge/work-in-progress
|
Hi @ibm-adarsh. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain 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. |
|
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ibm-adarsh 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 |
2 participants
What
Migrate the
ocp-e2e-ovn-agent-remote-libvirt-multi-z-zperiodic jobs (IBM Z s390x, agent-based OVN e2e) from the existing libvirt cluster profiles to VPN connectivity (orange zone) for releases 4.17 through 4.22. No changes to 4.23 or 5.0.Why
Run these jobs in the orange zone (VPN) so they use the same connectivity and DNS model as other IBM Z VPN jobs (e.g.
ocp-e2e-ovn-vpn-z-z, image-ecosystem, serial, FIPS, etc.).Changes
libvirt-s390x-1/libvirt-s390x-2→libvirt-s390x-vpnopenshift-e2e-libvirt-upi→openshift-e2e-libvirt-vpnsshd-bastion→intranet(required for orange zone)USE_EXTERNAL_DNS: "true"for VPN/orange zone DNS; kept existing env (ARCH,BRANCH,INSTALLER_TYPE: agent,ETCD_DISK_SPEED,NODE_TUNING,TEST_TYPE,VOLUME_CAPACITYwhere applicable)Scope
openshift-multiarch-main__nightly-4.{17,18,19,20,21,22}.yamlonlyci-operator/jobs/openshift/multiarch/openshift-multiarch-main-periodics.yaml(regenerated)