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
About the protocol: HTTPS property in the example, it lacks the tls and hostname properties. I guess it also concerns the protocol: TLS
If we don't put the tls property, there is an error message in the console when we do kubectl apply: Invalid value: "array": tls must be specified for protocols ['HTTPS', 'TLS']
2.If don't put the hostname property, there is an error message in the Ingress Controller pod: ["must be a valid hostname with a wildcard prefix '*' ornwithout"],"type":"ERROR_TYPE_FIELD"}])
What did you expect to happen?
Having a HTTPS and TLS proper example like this:
Create a kong-secret-proxy with kubectl create secret tls
Where is the problem?
https://docs.konghq.com/kubernetes-ingress-controller/latest/concepts/gateway-api/#gateway-management
What happened?
About the
protocol: HTTPS
property in the example, it lacks thetls
andhostname
properties. I guess it also concerns theprotocol: TLS
tls
property, there is an error message in the console when we dokubectl apply
:Invalid value: "array": tls must be specified for protocols ['HTTPS', 'TLS']
2.If don't put the
hostname
property, there is an error message in the Ingress Controller pod:["must be a valid hostname with a wildcard prefix '*' ornwithout"],"type":"ERROR_TYPE_FIELD"}])
What did you expect to happen?
Having a
HTTPS
andTLS
proper example like this:kong-secret-proxy
withkubectl create secret tls
Code of Conduct and Community Expectations
The text was updated successfully, but these errors were encountered: