Skip to content

Conversation

@sebrandon1
Copy link
Member

Summary

Add enhancement for HTTP01 Challenge Proxy as a controller within cert-manager-operator, following the istio-csr-controller pattern.

This enables cert-manager to complete HTTP01 challenges for the API endpoint (api.cluster.example.com) on baremetal platforms where DNS01 is not available.

Supersedes: #1773

Key Design Decisions

  • New HTTP01Proxy CRD in cert-manager-operator (not openshift/api)
  • Optional day-2 feature (not core payload)
  • Follows same pattern as istiocsrs.operator.openshift.io
  • DaemonSet on control plane nodes with nftables traffic redirection

Changes from Previous Approach

The original enhancement proposed adding configuration to the APIServer CRD in cluster-kube-apiserver-operator. This updated approach:

  1. Moves the feature to cert-manager-operator where it logically belongs
  2. Creates a new HTTP01Proxy CRD following the istio-csr-controller pattern
  3. Makes it an optional day-2 feature rather than a core payload component
  4. Simplifies the implementation by keeping it within the cert-manager domain

Tracking

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

openshift-ci-robot commented Jan 26, 2026

@sebrandon1: This pull request references CNF-18992 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 "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

Add enhancement for HTTP01 Challenge Proxy as a controller within cert-manager-operator, following the istio-csr-controller pattern.

This enables cert-manager to complete HTTP01 challenges for the API endpoint (api.cluster.example.com) on baremetal platforms where DNS01 is not available.

Supersedes: #1773

Key Design Decisions

  • New HTTP01Proxy CRD in cert-manager-operator (not openshift/api)
  • Optional day-2 feature (not core payload)
  • Follows same pattern as istiocsrs.operator.openshift.io
  • DaemonSet on control plane nodes with nftables traffic redirection

Changes from Previous Approach

The original enhancement proposed adding configuration to the APIServer CRD in cluster-kube-apiserver-operator. This updated approach:

  1. Moves the feature to cert-manager-operator where it logically belongs
  2. Creates a new HTTP01Proxy CRD following the istio-csr-controller pattern
  3. Makes it an optional day-2 feature rather than a core payload component
  4. Simplifies the implementation by keeping it within the cert-manager domain

Tracking

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
Copy link
Contributor

openshift-ci bot commented Jan 26, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign trilokgeer 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

@sebrandon1 sebrandon1 force-pushed the enhancement_cert_manager_http01_proxy branch from 23bfec3 to 58b2f96 Compare January 26, 2026 21:15
@sebrandon1
Copy link
Member Author

/retest

Add enhancement for HTTP01 Challenge Proxy as a controller within
cert-manager-operator, following the istio-csr-controller pattern.

This enables cert-manager to complete HTTP01 challenges for the API
endpoint (api.cluster.example.com) on baremetal platforms where DNS01
is not available.

Key design decisions:
- New HTTP01Proxy CRD in cert-manager-operator (not openshift/api)
- Optional day-2 feature (not core payload)
- Follows same pattern as istiocsrs.operator.openshift.io
- DaemonSet on control plane nodes with nftables traffic redirection

Supersedes: openshift#1773

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@sebrandon1 sebrandon1 force-pushed the enhancement_cert_manager_http01_proxy branch from 58b2f96 to f1cbdfd Compare January 27, 2026 15:14
@sebrandon1
Copy link
Member Author

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2026

@sebrandon1: all tests passed!

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

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants