-
Notifications
You must be signed in to change notification settings - Fork 21
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
Using nginx this way is a kubernetes anti-pattern #26
Comments
+1, maybe even consider switching to cloudnative solutions like Traefik CE with cert-manager. Also @KyleTryon consider switching to @onedr0p container images (: |
Probably another issue for tracking but feel free to read my mission statement on the containers I build: |
@aleksasiriski I'm curious about the traefik recommendation - any particular reason to use it over nginx? Since most of the config is abstracted away by the ingress config anyways. |
Personally I would not use Traefik as an ingress controller in k8s and instead use ingress-nginx. See my comments here: |
Personal preference, but go with either one. Some of the statements onedr0p mentions I can agree with but other not so much. So, again, it's personal preference for me but both are fine. |
The author of this project is aware of this now and is up to them to wether or not to update their project, closing... |
The proper was to get outside access to your cluster apps is to use an ingress controller like ingress-nginx and define ingress resources per application. For SSL the proper way to add certificates is to use cert-manager.
Once cert-manager is configured with the dns01 challenge you can put a common annotation on the ingresses to request, apply and use SSL certificates.
The text was updated successfully, but these errors were encountered: