Closed yogesh-reddy closed 1 year ago
Can you provide the values used here - is externalHostname
set to ingress.local
or ***.com
? (where ***.com
is an externally resolvable DNS name pointing to the ingress endpoint for the cluster)
external hostname is set externally resolvable DNS name.
Can you provide the values used here - is
externalHostname
set toingress.local
or***.com
? (where***.com
is an externally resolvable DNS name pointing to the ingress endpoint for the cluster)
I think ingress-nginx must be using ingress.local
for the ingress endpoint CA cert?
I'm not familiar with how to fix that but perhaps @mjudeikis can suggest something as it relates to the work in https://github.com/kcp-dev/helm-charts/pull/27/
@hardys @mjudeikis here is how I tried the kcp installation
Let me know if anything different is expected
Also @hardys i was looking at ingress resources.. looks like the secret name is not set.
should spec of Tls hosts contain this secret name ?
secretName: kcp-front-proxy-cert
I know ingress might be with a few hiccups now and secret name might be wrong. I have bunch of changes in my fork, but I want to merge #27 first. TL:DR: There might be issues :)
@mjudeikis found the issue. the ingress was not honoring the certs .. so we need some extra configurations in ingress to honor the tls certs and add some lua scripting to forward these. i am able to access the kcp locally now.
Installed the latest helm chart. and followed https://github.com/kcp-dev/helm-charts/pull/30 to create admin kubeconfig. When tried to access kcp with the generated configs..