Skip to content

OCPNODE-3833: PodAndContainerStatsFromCRI as Tech-Preview - #2942

Open
dgrisonnet wants to merge 1 commit into
openshift:masterfrom
dgrisonnet:cri-stats-beta
Open

OCPNODE-3833: PodAndContainerStatsFromCRI as Tech-Preview#2942
dgrisonnet wants to merge 1 commit into
openshift:masterfrom
dgrisonnet:cri-stats-beta

Conversation

@dgrisonnet

Copy link
Copy Markdown
Member

The feature graduated to Beta in Kubernetes 1.37: kubernetes/enhancements#2371. We want to start enabling as TP as soon as 5.0 to test it downstream ahead of 5.1.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 22, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 22, 2026

Copy link
Copy Markdown

@dgrisonnet: This pull request references OCPSTRAT-2556 which is a valid jira issue.

Details

In response to this:

The feature graduated to Beta in Kubernetes 1.37: kubernetes/enhancements#2371. We want to start enabling as TP as soon as 5.0 to test it downstream ahead of 5.1.

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 Jul 22, 2026

Copy link
Copy Markdown
Contributor

Hello @dgrisonnet! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

@dgrisonnet

Copy link
Copy Markdown
Member Author

/cc @haircommander @JoelSpeed

@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 121ed37c-7c75-45fe-85d0-74ab1e93cd9c

📥 Commits

Reviewing files that changed from the base of the PR and between bd6d9df and 4c7166a.

📒 Files selected for processing (10)
  • features.md
  • features/features.go
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-Default.yaml
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-DevPreviewNoUpgrade.yaml
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-OKD.yaml
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-TechPreviewNoUpgrade.yaml
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-Default.yaml
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-DevPreviewNoUpgrade.yaml
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-OKD.yaml
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-TechPreviewNoUpgrade.yaml
🚧 Files skipped from review as they are similar to previous changes (10)
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-OKD.yaml
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-Default.yaml
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-DevPreviewNoUpgrade.yaml
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-Default.yaml
  • features.md
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-OKD.yaml
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-DevPreviewNoUpgrade.yaml
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-TechPreviewNoUpgrade.yaml
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-TechPreviewNoUpgrade.yaml
  • features/features.go

📝 Walkthrough

Walkthrough

Adds and registers the PodAndContainerStatsFromCRI feature gate. Enables it for DevPreviewNoUpgrade and TechPreviewNoUpgrade in Hypershift and SelfManagedHA. Lists it as disabled for Default and OKD profiles.

Suggested reviewers: haircommander, joelspeed, everettraven

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies enabling PodAndContainerStatsFromCRI as a Tech Preview feature.
Description check ✅ Passed The description explains the feature's Kubernetes Beta graduation and the goal of downstream Tech Preview testing.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The PR changes 10 feature metadata and YAML files, with no test files or Ginkgo title declarations; therefore no unstable test names were introduced.
Test Structure And Quality ✅ Passed The commit changes only feature registration, documentation, and YAML manifests; it adds no Ginkgo tests or test-like files, so these test-quality requirements are not applicable.
Microshift Test Compatibility ✅ Passed The PR adds no Ginkgo e2e tests: its 10 changed files are feature metadata, a feature declaration, and feature-gate manifests.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The pull request changes only feature-gate documentation, Go registration, and YAML manifests. It adds no Ginkgo e2e tests, so SNO compatibility checks do not apply.
Topology-Aware Scheduling Compatibility ✅ Passed The patch only adds a feature-gate declaration, matrix row, and FeatureGate status entries; it adds no workloads, replicas, affinity, selectors, tolerations, topology constraints, or PDBs.
Ote Binary Stdout Contract ✅ Passed The only process-level change is a feature-gate initializer; it calls registration helpers, and the changed files contain no stdout writes or OTE suite entry points.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The pull request changes only feature metadata and YAML manifests; it adds no Ginkgo e2e tests, IPv4 assumptions, or test-time external connectivity.
No-Weak-Crypto ✅ Passed The diff only adds a feature-gate registration and YAML/Markdown entries; it introduces no weak crypto, custom crypto, or secret/token comparisons.
Container-Privileges ✅ Passed The PR adds only a feature-gate declaration, documentation, and FeatureGate status entries; added-content scans found no privileged, hostPID/Network/IPC, SYS_ADMIN, root, or allowPrivilegeEscalatio...
No-Sensitive-Data-In-Logs ✅ Passed The PR adds only feature-gate metadata, documentation, and YAML entries; the diff introduces no logging calls or log messages that could expose sensitive data.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.12.2)

Error: build linters: unable to load custom analyzer "kubeapilinter": tools/_output/bin/kube-api-linter.so, plugin: not implemented
The command is terminated due to an error: build linters: unable to load custom analyzer "kubeapilinter": tools/_output/bin/kube-api-linter.so, plugin: not implemented


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@openshift-ci openshift-ci Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jul 22, 2026
@openshift-ci
openshift-ci Bot requested a review from everettraven July 22, 2026 13:21
@qodo-for-rh-openshift

Copy link
Copy Markdown

PR Summary by Qodo

Enable PodAndContainerStatsFromCRI as Tech Preview / Dev Preview (no-upgrade)

✨ Enhancement ⚙️ Configuration changes 📝 Documentation 🕐 20-40 Minutes

Grey Divider

AI Description

• Register PodAndContainerStatsFromCRI as a supported feature gate (KEP-2371).
• Enable the gate for TechPreviewNoUpgrade and DevPreviewNoUpgrade feature sets.
• Propagate the gate into payload FeatureGate manifests and the feature matrix docs.
Diagram

graph TD
  A["features/features.go"] --> B["FeatureGate registry"] --> C["payload featuregates"] --> D[("Cluster FeatureGate")]
  A --> E["features.md"]
  D --> F["Kubelet/CRI stats"]

  subgraph Legend
    direction LR
    _code["Code"] ~~~ _cfg["Config manifest"] ~~~ _cr[("Cluster CR")]
  end
Loading
High-Level Assessment

This matches the established pattern for introducing/graduating a Kubernetes feature gate in this repo: register it once with metadata, enable it only in the intended preview feature-sets, and ensure payload manifests and docs reflect the same policy. Alternatives like component-specific toggles or deferring until the next major release would reduce downstream test coverage and diverge from the feature-set mechanism.

Files changed (10) +33 / -0

Enhancement (1) +8 / -0
features.goRegister PodAndContainerStatsFromCRI and enable for TP/DevPreview (no-upgrade) +8/-0

Register PodAndContainerStatsFromCRI and enable for TP/DevPreview (no-upgrade)

• Adds a new FeatureGate definition for PodAndContainerStatsFromCRI with node ownership metadata and a link to KEP-2371. Enables it specifically in TechPreviewNoUpgrade and DevPreviewNoUpgrade.

features/features.go

Documentation (1) +1 / -0
features.mdAdd PodAndContainerStatsFromCRI to the feature-set matrix +1/-0

Add PodAndContainerStatsFromCRI to the feature-set matrix

• Documents the PodAndContainerStatsFromCRI gate in the feature table so consumers can discover it and understand its availability across feature-sets.

features.md

Other (8) +24 / -0
featureGate-4-10-Hypershift-Default.yamlInclude PodAndContainerStatsFromCRI in HyperShift Default manifest (disabled list) +3/-0

Include PodAndContainerStatsFromCRI in HyperShift Default manifest (disabled list)

• Adds PodAndContainerStatsFromCRI to the HyperShift Default FeatureGate payload manifest so the gate is explicitly tracked for that feature-set (kept non-enabled by default via placement in the disabled list).

payload-manifests/featuregates/featureGate-4-10-Hypershift-Default.yaml

featureGate-4-10-Hypershift-DevPreviewNoUpgrade.yamlEnable PodAndContainerStatsFromCRI in HyperShift DevPreviewNoUpgrade manifest +3/-0

Enable PodAndContainerStatsFromCRI in HyperShift DevPreviewNoUpgrade manifest

• Adds PodAndContainerStatsFromCRI to the HyperShift DevPreviewNoUpgrade FeatureGate payload manifest so clusters in that preview channel can exercise the CRI stats behavior.

payload-manifests/featuregates/featureGate-4-10-Hypershift-DevPreviewNoUpgrade.yaml

featureGate-4-10-Hypershift-OKD.yamlInclude PodAndContainerStatsFromCRI in HyperShift OKD manifest (disabled list) +3/-0

Include PodAndContainerStatsFromCRI in HyperShift OKD manifest (disabled list)

• Adds PodAndContainerStatsFromCRI to the HyperShift OKD FeatureGate payload manifest so the gate is represented in OKD, without enabling it by default.

payload-manifests/featuregates/featureGate-4-10-Hypershift-OKD.yaml

featureGate-4-10-Hypershift-TechPreviewNoUpgrade.yamlEnable PodAndContainerStatsFromCRI in HyperShift TechPreviewNoUpgrade manifest +3/-0

Enable PodAndContainerStatsFromCRI in HyperShift TechPreviewNoUpgrade manifest

• Adds PodAndContainerStatsFromCRI to the HyperShift TechPreviewNoUpgrade FeatureGate payload manifest to allow early downstream validation ahead of broader enablement.

payload-manifests/featuregates/featureGate-4-10-Hypershift-TechPreviewNoUpgrade.yaml

featureGate-4-10-SelfManagedHA-Default.yamlInclude PodAndContainerStatsFromCRI in SelfManagedHA Default manifest (disabled list) +3/-0

Include PodAndContainerStatsFromCRI in SelfManagedHA Default manifest (disabled list)

• Adds PodAndContainerStatsFromCRI to the SelfManagedHA Default FeatureGate payload manifest so the gate is explicitly enumerated for Default (kept non-enabled by default via placement in the disabled list).

payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-Default.yaml

featureGate-4-10-SelfManagedHA-DevPreviewNoUpgrade.yamlEnable PodAndContainerStatsFromCRI in SelfManagedHA DevPreviewNoUpgrade manifest +3/-0

Enable PodAndContainerStatsFromCRI in SelfManagedHA DevPreviewNoUpgrade manifest

• Adds PodAndContainerStatsFromCRI to the SelfManagedHA DevPreviewNoUpgrade FeatureGate payload manifest to support preview testing on the SelfManagedHA topology.

payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-DevPreviewNoUpgrade.yaml

featureGate-4-10-SelfManagedHA-OKD.yamlInclude PodAndContainerStatsFromCRI in SelfManagedHA OKD manifest (disabled list) +3/-0

Include PodAndContainerStatsFromCRI in SelfManagedHA OKD manifest (disabled list)

• Adds PodAndContainerStatsFromCRI to the SelfManagedHA OKD FeatureGate payload manifest so the gate is represented in OKD without being enabled by default.

payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-OKD.yaml

featureGate-4-10-SelfManagedHA-TechPreviewNoUpgrade.yamlEnable PodAndContainerStatsFromCRI in SelfManagedHA TechPreviewNoUpgrade manifest +3/-0

Enable PodAndContainerStatsFromCRI in SelfManagedHA TechPreviewNoUpgrade manifest

• Adds PodAndContainerStatsFromCRI to the SelfManagedHA TechPreviewNoUpgrade FeatureGate payload manifest to allow early downstream coverage in the Tech Preview channel.

payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-TechPreviewNoUpgrade.yaml

@dgrisonnet dgrisonnet changed the title OCPSTRAT-2556: PodAndContainerStatsFromCRI as Tech-Preview OCPNODE-3833: PodAndContainerStatsFromCRI as Tech-Preview Jul 22, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 22, 2026

Copy link
Copy Markdown

@dgrisonnet: This pull request references OCPNODE-3833 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 epic to target the "5.0.0" version, but no target version was set.

Details

In response to this:

The feature graduated to Beta in Kubernetes 1.37: kubernetes/enhancements#2371. We want to start enabling as TP as soon as 5.0 to test it downstream ahead of 5.1.

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.

@qodo-for-rh-openshift

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Qodo Logo

@JoelSpeed

JoelSpeed commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

/lgtm
/override-sticky ci/prow/verify-hypershift-integration

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 22, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-techpreview
/test e2e-aws-serial-1of2
/test e2e-aws-serial-2of2
/test e2e-aws-serial-techpreview-1of2
/test e2e-aws-serial-techpreview-2of2
/test e2e-azure
/test e2e-gcp
/test e2e-upgrade
/test e2e-upgrade-out-of-change
/test minor-e2e-upgrade-minor

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 22, 2026
@dgrisonnet

Copy link
Copy Markdown
Member Author

/retest-required

1 similar comment
@dgrisonnet

Copy link
Copy Markdown
Member Author

/retest-required

@haircommander

Copy link
Copy Markdown
Member

what are the plans for exposing the stats config to container runtime config? i personally think that'll be a promising aspect of this feature, where customers can choose which controllers they want to collect stats for. That also could allow for us to tune the stats collection aspects (like eventually https://redhat.atlassian.net/browse/OCPSTRAT-2346 as well as collection period)

@dgrisonnet

Copy link
Copy Markdown
Member Author

For https://redhat.atlassian.net/browse/OCPSTRAT-2346 I am working on a different approach than the stats API one.

To me it should be treated as an actual bug in how cri-o (and cadvisor) report network metrics. I want to leverage the fact that the runtime is aware of host network enabled pods: https://github.com/cri-o/cri-o/blob/11f2b51a5b6e9ff42dcd148b3df16858b2c2897f/internal/lib/sandbox/sandbox.go#L70 to filter-out pod-specific interfaces.

This could take two shapes:

  1. I build a cache of pod-owned interfaces and skip them from host-network pod metrics
  2. I get the list of interfaces from netlink and remove the veth ones. This approach could be brittle if the CNI plugins ever decide to use another type of interfaces for pods

@haircommander

Copy link
Copy Markdown
Member

yeah I was thinking something like approach 1, though I worry about treating it like a bug and unilaterally making the change, in case users have problems with it. I'm open to how you want to approach, but I was imagining it'd be configurable (default on, but upgrades would keep off with an MC or smth)

@dgrisonnet

Copy link
Copy Markdown
Member Author

I am still on the fence on whether this should be configurable or on by default. Once I have a proof of concept ready, I'll open a PR and we can discuss that there

/retest-required

@JoelSpeed

Copy link
Copy Markdown
Contributor

/retest

@JoelSpeed

Copy link
Copy Markdown
Contributor

/override-sticky ci/prow/verify-hypershift-integration

This is an unrelated failure blocked on hypershift updating their 1.36 deps

@openshift-ci

openshift-ci Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/verify-hypershift-integration

These overrides will persist across retests on the current HEAD SHA. Pushing a new commit will clear them. Use /override-cancel to remove them.

Details

In response to this:

/override-sticky ci/prow/verify-hypershift-integration

This is an unrelated failure blocked on hypershift updating their 1.36 deps

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.

@dgrisonnet

Copy link
Copy Markdown
Member Author

/retest-required

@Chandan9112

Copy link
Copy Markdown

/verified by @Chandan9112 . Tested PodAndContainerStatsFromCRI=true with containerd, metrics reported correctly via CRI path.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 967cc4c and 2 for PR HEAD bd6d9df in total

@dgrisonnet

Copy link
Copy Markdown
Member Author

/retest-required

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 8ba0b25 and 1 for PR HEAD bd6d9df in total

@dgrisonnet

Copy link
Copy Markdown
Member Author

/retest-required

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD b9305b7 and 0 for PR HEAD bd6d9df in total

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/hold

Revision bd6d9df was retested 3 times: holding

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 29, 2026
@dgrisonnet

Copy link
Copy Markdown
Member Author

The failures are unrelated flakes.

/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 30, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 72624b9 and 2 for PR HEAD bd6d9df in total

@dgrisonnet

Copy link
Copy Markdown
Member Author

There is a bug in cri-o.

/hold

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 30, 2026
@dgrisonnet

Copy link
Copy Markdown
Member Author

Opened cri-o/cri-o#10206 to address the issue

@dgrisonnet

Copy link
Copy Markdown
Member Author

/retest-required

@openshift-ci openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 9, 2026
Signed-off-by: Damien Grisonnet <dgrisonn@redhat.com>
@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Aug 9, 2026
@openshift-ci openshift-ci Bot removed lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Aug 9, 2026
@dgrisonnet

Copy link
Copy Markdown
Member Author

/retest-required

@dgrisonnet

Copy link
Copy Markdown
Member Author

/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 9, 2026
@bitoku

bitoku commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 10, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-techpreview
/test e2e-aws-serial-1of2
/test e2e-aws-serial-2of2
/test e2e-aws-serial-techpreview-1of2
/test e2e-aws-serial-techpreview-2of2
/test e2e-azure
/test e2e-gcp
/test e2e-upgrade
/test e2e-upgrade-out-of-change
/test minor-e2e-upgrade-minor

@openshift-ci

openshift-ci Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bitoku, JoelSpeed

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

The pull request process is described 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

openshift-ci Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

@dgrisonnet: 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/e2e-aws-serial-techpreview-2of2 4c7166a link true /test e2e-aws-serial-techpreview-2of2
ci/prow/e2e-aws-serial-techpreview-1of2 4c7166a link true /test e2e-aws-serial-techpreview-1of2
ci/prow/e2e-aws-ovn-techpreview 4c7166a link true /test e2e-aws-ovn-techpreview
ci/prow/verify-hypershift-integration 4c7166a link true /test verify-hypershift-integration
ci/prow/e2e-aws-ovn-hypershift-conformance 4c7166a link true /test e2e-aws-ovn-hypershift-conformance

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.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants