The UpstreamSpec_HTTP struct has a Subdomain field, but UpstreamSpec_HTTPS only has CustomDomains.
frp itself supports subdomain for both HTTP and HTTPS type proxies (docs). When frps has subdomainHost configured, customDomains cannot overlap with it — the only way to register an HTTPS proxy under subdomainHost is to use subdomain.
This makes the operator's HTTPS upstream unusable with subdomainHost-based FRP servers.
Source: api/v1alpha1/upstream_types.go — UpstreamSpec_HTTPS struct needs:
// +optional
Subdomain string `json:"subdomain,omitempty"`
Workaround: Standalone frpc deployment with a manually managed ConfigMap using subdomain for the HTTPS proxy.
The
UpstreamSpec_HTTPstruct has aSubdomainfield, butUpstreamSpec_HTTPSonly hasCustomDomains.frp itself supports
subdomainfor both HTTP and HTTPS type proxies (docs). When frps hassubdomainHostconfigured,customDomainscannot overlap with it — the only way to register an HTTPS proxy undersubdomainHostis to usesubdomain.This makes the operator's HTTPS upstream unusable with
subdomainHost-based FRP servers.Source:
api/v1alpha1/upstream_types.go—UpstreamSpec_HTTPSstruct needs:Workaround: Standalone frpc deployment with a manually managed ConfigMap using
subdomainfor the HTTPS proxy.