Skip to content

CNTRLPLANE-1137: Add ci for cilium e2e test - #71383

Closed
wewang58 wants to merge 1 commit into
openshift:mainfrom
wewang58:add_ci_to_run_cilium_e2e
Closed

CNTRLPLANE-1137: Add ci for cilium e2e test#71383
wewang58 wants to merge 1 commit into
openshift:mainfrom
wewang58:add_ci_to_run_cilium_e2e

Conversation

@wewang58

Copy link
Copy Markdown
Contributor

Add ci for e2e test codes: openshift/hypershift#7077

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 14, 2025
@openshift-ci

openshift-ci Bot commented Nov 14, 2025

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@mgencur mgencur left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two minor comments (see inline). Otherwise I think it looks good.

With this job we'd be able to run Hypershift E2E test suite on AKS. That's fine. But there would be a mismatch between AKS and other platforms (AWS, Baremetal, Kubevirt) where we run Conformance tests for Cilium and Calico.
I will leave this to someone else to consider if this is ok. But later, if we want to get to the same level of support for AKS and other platforms we'd need to run the conformance tests as well. Thanks

OCP_IMAGE_N3: release:n3minor
OCP_IMAGE_N4: release:n4minor
env:
AUTH_THROUGH_CERTS: "true"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose EXTERNAL_CNI_PROVIDER needs to be set here. Otherwise it won't run with Cilium.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated.

# Run test with external CNI provider if specified
if [[ -n "${EXTERNAL_CNI_PROVIDER:-}" ]]; then
run_e2e_test "--e2e.external-cni-provider=${EXTERNAL_CNI_PROVIDER}"
fi

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you use the same approach like the rest of variables? For example, there's this (see below). The N1_NP_VERSION_TEST_ARGS is always passed to the command but sometimes it is empty, sometimes not.

N1_NP_VERSION_TEST_ARGS=""
if [[ ${OCP_IMAGE_N1} != "${OCP_IMAGE_LATEST}" ]]; then
  N1_NP_VERSION_TEST_ARGS="--e2e.n1-minor-release-image=${OCP_IMAGE_N1}"
fi

In our new case, it would be something like this:

EXTERNAL_CNI_PROVIDER_ARGS=""
if [[ -n ${EXTERNAL_CNI_PROVIDER:-} ]]; then
  EXTERNAL_CNI_PROVIDER_ARGS="--e2e.external-cni-provider=${EXTERNAL_CNI_PROVIDER}"
fi

And then it would be used like this:

hack/ci-test-e2e.sh -test.v \
  -test.run=${CI_TESTS_RUN:-} \
  -test.parallel=20 \
  --e2e.platform=Azure \
  --e2e.azure-credentials-file=/etc/hypershift-ci-jobs-azurecreds/credentials.json \
  --e2e.pull-secret-file=/etc/ci-pull-credentials/.dockerconfigjson \
  --e2e.base-domain=hypershift.azure.devcluster.openshift.com \
  --e2e.azure-location=${HYPERSHIFT_AZURE_LOCATION} \
  --e2e.oidc-issuer-url=${AZURE_OIDC_ISSUER_URL} \
  --e2e.sa-token-issuer-private-key-path=${AZURE_SA_TOKEN_ISSUER_KEY_PATH} \
    ${EXTERNAL_CNI_PROVIDER_ARGS:-} \ //<--------------------- HERE -------
    ${EXTERNAL_DNS_ARGS:-} \
    ${AKS_ANNOTATIONS:-} \
    ${N1_NP_VERSION_TEST_ARGS:-} \
    ${N2_NP_VERSION_TEST_ARGS:-} \
    ${N3_NP_VERSION_TEST_ARGS:-} \
    ${N4_NP_VERSION_TEST_ARGS:-} \
    ${MI_ARGS:-} \
    ${DP_ARGS:-} \
    ${AZURE_MULTI_ARCH_PARAMS:-} \
  --e2e.azure-encryption-key-id=${AKS_KMS_KEY} \
  --e2e.azure-kms-credentials-secret-name=${AKS_KMS_CREDENTIALS_SECRET} \
  ${MARKETPLACE_IMAGE_PARAMS} \
  --e2e.latest-release-image="${OCP_IMAGE_LATEST}" \
  --e2e.previous-release-image="${OCP_IMAGE_PREVIOUS}" &

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated, thanks reviewing.

@wewang58 wewang58 changed the title Add ci for cilium e2e test CNTRLPLANE-1137: Add ci for cilium e2e test Nov 14, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 14, 2025
@openshift-ci-robot

openshift-ci-robot commented Nov 14, 2025

Copy link
Copy Markdown
Contributor

@wewang58: This pull request references CNTRLPLANE-1137 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

Details

In response to this:

Add ci for e2e test codes: openshift/hypershift#7077

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 openshift-eng/jira-lifecycle-plugin repository.

@wewang58
wewang58 force-pushed the add_ci_to_run_cilium_e2e branch from 30fb9af to 6772385 Compare November 19, 2025 02:41
@openshift-bot

Copy link
Copy Markdown
Contributor

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d 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

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 19, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 19, 2025
@openshift-bot

Copy link
Copy Markdown
Contributor

Stale issue in openshift/release rot after 15d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 15d 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

@openshift-ci openshift-ci Bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 3, 2026
MARKETPLACE_IMAGE_PARAMS="--e2e.azure-marketplace-publisher ${HYPERSHIFT_AZURE_MARKETPLACE_IMAGE_PUBLISHER} --e2e.azure-marketplace-offer ${HYPERSHIFT_AZURE_MARKETPLACE_IMAGE_OFFER} --e2e.azure-marketplace-sku ${HYPERSHIFT_AZURE_MARKETPLACE_IMAGE_SKU} --e2e.azure-marketplace-version ${HYPERSHIFT_AZURE_MARKETPLACE_IMAGE_VERSION}"
fi
EXTERNAL_CNI_PROVIDER_ARGS=""
if [[ -n ${EXTERNAL_CNI_PROVIDER:-} ]]; then

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose this also needs to atomatically set --network-type=Other ?
Otherwise the condition if platform != hyperv1.NonePlatform && hostedCluster.Spec.Networking.NetworkType != hyperv1.Other { here won't match and it will try to "validate" the cluster even though the CNI is Cilium https://github.com/openshift/hypershift/pull/7423/files#diff-65fe136e12a7c2756931254c4f076ef0b5bc990b0fc13a8407647f421ddfa328R128

@wewang58
wewang58 force-pushed the add_ci_to_run_cilium_e2e branch from 6772385 to 01943fd Compare January 11, 2026 00:21
@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jan 11, 2026
@openshift-bot

Copy link
Copy Markdown
Contributor

Rotten issues in openshift/release close after 15d 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-ci openshift-ci Bot closed this Jan 26, 2026
@openshift-ci

openshift-ci Bot commented Jan 26, 2026

Copy link
Copy Markdown
Contributor

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues in openshift/release close after 15d 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

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.

@wewang58

Copy link
Copy Markdown
Contributor Author

/reopen

@openshift-ci openshift-ci Bot reopened this Jan 28, 2026
@openshift-ci-robot

openshift-ci-robot commented Jan 28, 2026

Copy link
Copy Markdown
Contributor

@wewang58: This pull request references CNTRLPLANE-1137 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Add ci for e2e test codes: openshift/hypershift#7077

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci

openshift-ci Bot commented Jan 28, 2026

Copy link
Copy Markdown
Contributor

@wewang58: Reopened this PR.

Details

In response to this:

/reopen

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.

@wewang58

wewang58 commented Feb 6, 2026

Copy link
Copy Markdown
Contributor Author

@mgencur Recently busy with jobset operator GA test, when have time will update the pr.

@wewang58
wewang58 force-pushed the add_ci_to_run_cilium_e2e branch from 01943fd to e07706d Compare February 12, 2026 04:03
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 12, 2026
@openshift-ci

openshift-ci Bot commented Feb 12, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: wewang58
Once this PR has been reviewed and has the lgtm label, please assign bryan-cox for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot removed the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Feb 12, 2026
@wewang58

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aks-cilium

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@wewang58: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@wewang58
wewang58 force-pushed the add_ci_to_run_cilium_e2e branch from e07706d to 8b30474 Compare February 12, 2026 05:56
@wewang58

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aks-cilium

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@wewang58: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@wewang58
wewang58 force-pushed the add_ci_to_run_cilium_e2e branch from 8b30474 to bcddc4e Compare February 12, 2026 08:57
@wewang58

Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aks-cilium

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@wewang58: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@wewang58: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-hypershift-main-e2e-aks-cilium openshift/hypershift presubmit Presubmit changed
pull-ci-openshift-hypershift-main-e2e-aks openshift/hypershift presubmit Registry content changed
pull-ci-openshift-hypershift-main-e2e-aks-4-21 openshift/hypershift presubmit Registry content changed
pull-ci-openshift-hypershift-main-e2e-aks-override openshift/hypershift presubmit Registry content changed
pull-ci-openshift-hypershift-release-4.23-e2e-aks openshift/hypershift presubmit Registry content changed
pull-ci-openshift-hypershift-release-4.23-e2e-aks-4-21 openshift/hypershift presubmit Registry content changed
pull-ci-openshift-hypershift-release-4.23-e2e-aks-override openshift/hypershift presubmit Registry content changed
pull-ci-openshift-hypershift-release-4.22-e2e-aks openshift/hypershift presubmit Registry content changed
pull-ci-openshift-hypershift-release-4.22-e2e-aks-4-21 openshift/hypershift presubmit Registry content changed
pull-ci-openshift-hypershift-release-4.22-e2e-aks-override openshift/hypershift presubmit Registry content changed
pull-ci-openshift-hypershift-release-4.21-e2e-aks openshift/hypershift presubmit Registry content changed
pull-ci-openshift-hypershift-release-4.21-e2e-aks-override openshift/hypershift presubmit Registry content changed
pull-ci-openshift-hypershift-release-4.20-e2e-aks openshift/hypershift presubmit Registry content changed
pull-ci-openshift-hypershift-release-4.19-e2e-aks openshift/hypershift presubmit Registry content changed
pull-ci-openshift-cloud-network-config-controller-main-hypershift-e2e-aks openshift/cloud-network-config-controller presubmit Registry content changed
pull-ci-openshift-cloud-network-config-controller-release-4.23-hypershift-e2e-aks openshift/cloud-network-config-controller presubmit Registry content changed
pull-ci-openshift-cloud-network-config-controller-release-4.22-hypershift-e2e-aks openshift/cloud-network-config-controller presubmit Registry content changed
pull-ci-openshift-cloud-network-config-controller-release-4.21-hypershift-e2e-aks openshift/cloud-network-config-controller presubmit Registry content changed
pull-ci-openshift-cloud-network-config-controller-release-4.20-hypershift-e2e-aks openshift/cloud-network-config-controller presubmit Registry content changed
pull-ci-openshift-cloud-network-config-controller-release-4.19-hypershift-e2e-aks openshift/cloud-network-config-controller presubmit Registry content changed
pull-ci-openshift-cluster-ingress-operator-master-hypershift-e2e-aks openshift/cluster-ingress-operator presubmit Registry content changed
pull-ci-openshift-cluster-ingress-operator-release-4.23-hypershift-e2e-aks openshift/cluster-ingress-operator presubmit Registry content changed
pull-ci-openshift-cluster-ingress-operator-release-4.22-hypershift-e2e-aks openshift/cluster-ingress-operator presubmit Registry content changed
pull-ci-openshift-cluster-ingress-operator-release-4.21-hypershift-e2e-aks openshift/cluster-ingress-operator presubmit Registry content changed
pull-ci-openshift-cluster-ingress-operator-release-4.20-hypershift-e2e-aks openshift/cluster-ingress-operator presubmit Registry content changed

A total of 67 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@openshift-ci

openshift-ci Bot commented Feb 12, 2026

Copy link
Copy Markdown
Contributor

@wewang58: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/yamllint 01943fd link true /test yamllint
ci/rehearse/openshift/hypershift/main/e2e-aks-cilium bcddc4e link unknown /pj-rehearse pull-ci-openshift-hypershift-main-e2e-aks-cilium

Full PR test history. Your PR dashboard.

Details

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.

@openshift-bot

Copy link
Copy Markdown
Contributor

Rotten issues in openshift/release close after 15d 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-ci openshift-ci Bot closed this Feb 27, 2026
@openshift-ci

openshift-ci Bot commented Feb 27, 2026

Copy link
Copy Markdown
Contributor

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues in openshift/release close after 15d 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

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants