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
{{ message }}
Repository navigation
Auth Flow page lists the wrong names for the HTTPRoute, SecurityPolicy and Certificate #38
The resource names on the Auth Flow page don't match what the operator creates (internal/controller/utils/naming/naming.go:46-104). The suffixes are the same in alpha.19, alpha.20 and v0.1.1, so the page was never right.
<name>-route, plus <name>-public-route when publicRoutes is set
Certificate
<name>-tls in the app namespace (:263)
<name>-<namespace>-cert in envoy-gateway-system
Certificate secretName
<name>-tls (:265)
<name>-<namespace>-tls
The OIDC secret (<name>-oidc-client) and the Role (<name>-oidc-secret-reader) are correct. The CI log for this repo shows the real names (my-pack-route, my-pack-security).
Fix
Correct the table and YAML on the page and in the docs/auth-flow.md mirror.
Note that the Certificate only exists when the operator has a ClusterIssuer and tls.secretName is unset.
Fix README.md:846, which runs kubectl get certificate -n my-pack; Certificates live in envoy-gateway-system.
Verified against this repo at 4e50cd0, nebari-operator v0.1.1 (same commit as operator main), and NIC v0.14.0.
Activity
Correct resource names and locations in the auth and troubleshooting …