Add PodCertificateRequest feature gate to TechPreview

[redhat-chai-bot]

Summary

Register the PodCertificateRequest feature gate and enable it under TechPreviewNoUpgrade and DevPreviewNoUpgrade feature sets.

Details

This adds the upstream Kubernetes PodCertificateRequest feature gate (KEP 4317) to OpenShift.

• Feature gate: PodCertificateRequest
• Product scope: Kubernetes
• Enabled in: TechPreviewNoUpgrade, DevPreviewNoUpgrade
• Jira component: kube-apiserver
• Contact: ibihim

Changed files

• features/features.go — feature gate definition
• features.md — documentation table update
• payload-manifests/featuregates/featureGate-*.yaml — generated manifest updates for all SelfManagedHA and Hypershift profiles

Companion PR: cluster-kube-apiserver-operator#2266 (runtime-config mapping)

---

AI-generated. Review for accuracy.

@dgoodwin requested in Slack thread

[openshift-merge-bot]

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]

Hello @redhat-chai-bot! 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.

[coderabbitai]

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: fef23a3d-e850-446e-987e-77d8c5ea50d6

📥 Commits

Reviewing files that changed from the base of the PR and between d4bb0b4 and 0ed3a20.

📒 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

---

📝 Walkthrough

Walkthrough

The change registers the PodCertificateRequest feature gate with Kubernetes ownership and preview metadata. The feature support matrix marks it enabled for DevPreviewNoUpgrade and TechPreviewNoUpgrade profiles. Hypershift and SelfManagedHA manifests enable the feature in preview profiles and disable it in Default and OKD profiles.

Merge Risk: ⚪ Minimal · up to 0ed3a

This PR adds the PodCertificateRequest feature gate to the documented preview feature sets and updates the corresponding generated manifests. No actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: adding the PodCertificateRequest feature gate to TechPreview.
Description check	✅ Passed	The description directly explains the feature gate registration, enablement profiles, affected files, and companion runtime configuration change.
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 diff changes only feature metadata, documentation, and YAML manifests; it adds or changes no Ginkgo It, Describe, Context, When, or similar test title.
Test Structure And Quality	✅ Passed	The PR changes only feature registration, documentation, and YAML manifests; it adds no Ginkgo tests, It blocks, resource setup, waits, or assertions to review.
Microshift Test Compatibility	✅ Passed	The HEAD diff adds only feature-gate metadata and YAML manifests; it adds no Ginkgo tests or test references to MicroShift-unavailable APIs.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The PR diff contains only feature-gate metadata, documentation, and YAML manifests; it adds no Ginkgo tests or topology assumptions.
Topology-Aware Scheduling Compatibility	✅ Passed	The HEAD diff only registers PodCertificateRequest, updates documentation, and changes FeatureGate status lists; it adds no deployment, controller, or scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	The diff adds only feature metadata, manifests, and a pure top-level feature registration chain; no OTE binary, suite setup, or stdout write is introduced.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The diff changes only feature metadata, documentation, and YAML manifests; it adds no Ginkgo e2e tests or test connectivity, IPv4, or external-service assumptions.
No-Weak-Crypto	✅ Passed	The parent diff adds only PodCertificateRequest registration, documentation, and feature-gate manifest entries; no introduced line uses MD5, SHA1, DES, RC4, Blowfish, ECB, or custom crypto.
Container-Privileges	✅ Passed	The commit adds only PodCertificateRequest metadata and FeatureGate name entries; all changed YAML objects are FeatureGate configs with no privileged, host namespace, SYS_ADMIN, root, or allowPrivi...
No-Sensitive-Data-In-Logs	✅ Passed	The PR only adds feature metadata, documentation, and manifest entries; the parent-to-HEAD diff introduces no logging calls or sensitive data in logs.

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[dgoodwin]

/payload-job-with-prs periodic-ci-openshift-release-main-ci-5.0-e2e-aws-ovn-techpreview openshift/cluster-kube-apiserver-operator#2266/payload-job-with-prs periodic-ci-openshift-release-main-ci-5.0-e2e-aws-ovn-techpreview-serial openshift/cluster-kube-apiserver-operator#2266

[openshift-ci]

@dgoodwin: An error was encountered. No known errors were detected, please see the full error message for details.

Full error message.

unable to get additional pr info from string: openshift/cluster-kube-apiserver-operator#2266/payload-job-with-prs: string: openshift/cluster-kube-apiserver-operator#2266/payload-job-with-prs doesn't match expected format: org/repo#number

Please contact an administrator to resolve this issue.

[JoelSpeed]

/lgtm

@dgoodwin verified on you once you've worked out the payload testing you were trying

[openshift-merge-bot]

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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:

• OWNERS [JoelSpeed]

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

[dgoodwin]

/payload-job-with-prs periodic-ci-openshift-release-main-ci-5.0-e2e-aws-ovn-techpreview openshift/cluster-kube-apiserver-operator#2266

/payload-job-with-prs periodic-ci-openshift-release-main-ci-5.0-e2e-aws-ovn-techpreview-serial openshift/cluster-kube-apiserver-operator#2266

[openshift-ci]

@dgoodwin: given command is invalid: at least one of the commands given is only supported on a one-command-per-comment basis, please separate out commands as multiple comments

[dgoodwin]

/payload-job-with-prs periodic-ci-openshift-release-main-ci-5.0-e2e-aws-ovn-techpreview openshift/cluster-kube-apiserver-operator#2266

[openshift-ci]

@dgoodwin: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[dgoodwin]

/payload-job-with-prs periodic-ci-openshift-release-main-ci-5.0-e2e-aws-ovn-techpreview-serial openshift/cluster-kube-apiserver-operator#2266

[openshift-ci]

@dgoodwin: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[dgoodwin]

/payload-job-with-prs periodic-ci-openshift-release-main-ci-5.0-e2e-aws-ovn-techpreview-serial openshift/cluster-kube-apiserver-operator#2266

[openshift-ci]

@dgoodwin: trigger 3 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-main-ci-5.0-e2e-aws-ovn-techpreview-serial-1of3
• periodic-ci-openshift-release-main-ci-5.0-e2e-aws-ovn-techpreview-serial-2of3
• periodic-ci-openshift-release-main-ci-5.0-e2e-aws-ovn-techpreview-serial-3of3

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ad466c10-9a2f-11f1-9d41-29316589e5d5-0

[dgoodwin]

/payload-job-with-prs periodic-ci-openshift-release-main-ci-5.0-e2e-aws-ovn-techpreview openshift/cluster-kube-apiserver-operator#2266

[openshift-ci]

@dgoodwin: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-main-ci-5.0-e2e-aws-ovn-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c0d5e620-9a2f-11f1-9453-547627e4939d-0

[dgoodwin]

/retest

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-ci]

@redhat-chai-bot: 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-ovn-hypershift	0ed3a20	link	true	/test e2e-aws-ovn-hypershift
ci/prow/e2e-aws-serial-techpreview-2of2	0ed3a20	link	true	/test e2e-aws-serial-techpreview-2of2
ci/prow/e2e-aws-serial-techpreview-1of2	0ed3a20	link	true	/test e2e-aws-serial-techpreview-1of2
ci/prow/minor-e2e-upgrade-minor	0ed3a20	link	true	/test minor-e2e-upgrade-minor
ci/prow/e2e-aws-ovn-techpreview	0ed3a20	link	true	/test e2e-aws-ovn-techpreview
ci/prow/e2e-aws-ovn	0ed3a20	link	true	/test e2e-aws-ovn

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.

[JoelSpeed]

CC @everettraven