You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adds the HTTP01 Challenge Proxy controller to cert-manager-operator,
enabling cert-manager to complete HTTP01 ACME challenges for the API
endpoint on baremetal platforms where the API VIP is not exposed via
OpenShift Ingress.
When a user creates an HTTP01Proxy CR with mode DefaultDeployment,
the operator validates the platform is BareMetal with distinct API
and Ingress VIPs, then deploys a DaemonSet on control plane nodes
running a reverse proxy. The proxy uses nftables to redirect HTTP
traffic from API_VIP:80 to a local proxy port (default 8888). Only
/.well-known/acme-challenge/* requests are forwarded to the Ingress
VIP; all other requests are rejected.
Feature gate: HTTP01Proxy (Alpha, disabled by default)
Enable via: --unsupported-addon-features=HTTP01Proxy=true
Jira: https://issues.redhat.com/browse/CM-716
Enhancement: openshift/enhancements#1929
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,9 +5,9 @@ This repository contains Cert Manager Operator designed for OpenShift. The opera
5
5
## The operator architecture and design assumptions
6
6
7
7
The Operator uses the [upstream deployment manifests](https://github.com/cert-manager/cert-manager/releases). It divides them into separate files and deploys using 3 controllers:
// HTTP01ProxySpec is the specification of the desired behavior of the HTTP01Proxy.
75
+
// +kubebuilder:validation:XValidation:rule="self.mode == 'CustomDeployment' ? has(self.customDeployment) : !has(self.customDeployment)",message="customDeployment is required when mode is CustomDeployment and forbidden otherwise"
76
+
typeHTTP01ProxySpecstruct {
77
+
// mode controls whether the HTTP01 challenge proxy is active and how it should be deployed.
78
+
// DefaultDeployment enables the proxy with default configuration.
79
+
// CustomDeployment enables the proxy with user-specified configuration.
80
+
// +kubebuilder:validation:Required
81
+
// +required
82
+
ModeHTTP01ProxyMode`json:"mode"`
83
+
84
+
// customDeployment contains configuration options when mode is CustomDeployment.
85
+
// This field is only valid when mode is CustomDeployment.
0 commit comments