Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TLS certs failing #346

Closed
chrislovecnm opened this issue Apr 19, 2022 · 2 comments
Closed

TLS certs failing #346

chrislovecnm opened this issue Apr 19, 2022 · 2 comments

Comments

@chrislovecnm
Copy link

Summary

Setup via terraform and I am getting certificate errors

Steps to reproduce the behavior

See #344

Expected behavior

The system is using letsencrypt for the certificates.

Actual behavior

 k -n jx-git-operator logs jx-boot-db5ff8d2-8bff-4771-9734-daa9b248c475-7fs7z
Error from server (InternalError): error when creating "config-root/namespaces/jx/jx-pipelines-visualizer/jx-pipelines-visualizer-ingress.yaml": Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "https://ingress-nginx-controller-admission.nginx.svc:443/networking/v1/ingresses?timeout=10s": x509: certificate signed by unknown authority
Error from server (InternalError): error when creating "config-root/namespaces/jx/jxboot-helmfile-resources/chartmuseum-ingress.yaml": Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "https://ingress-nginx-controller-admission.nginx.svc:443/networking/v1/ingresses?timeout=10s": x509: certificate signed by unknown authority
Error from server (InternalError): error when creating "config-root/namespaces/jx/jxboot-helmfile-resources/hook-ingress.yaml": Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post "https://ingress-nginx-controller-admission.nginx.svc:443/networking/v1/ingresses?timeout=10s": x509: certificate signed by unknown authority
make: *** [versionStream/src/Makefile.mk:290: kubectl-apply] Error 1

See See #344 for the rest

@ankitm123
Copy link
Member

See this: #344 (comment)

@chrislovecnm
Copy link
Author

The problem was actually upper level dns, and then had another problem with the certificate manager. Both are fixed, and now I am closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants