-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
Added support for traefik2 #27
Conversation
I have tested this with the base config, and it appears stable, although I have done no further testing as yet :)
Also tested as follows with cert manager referring the the nginx-ingress and longhorn fails with the same error every time (unrelated)
|
Hi @garutilorenzo does that mean that the default install works with this Oracle cluster? I'd understood proxy mode was enabled and a NodePort rather than a LB is used in your PR, as well as routing from the Oracle loadbalancer. I am not clear if those things are true with the default k3s traefik install? |
Ok @mannp, now with the last commits:
|
Added variable disable_ingress default to False. |
Only metrics, coredns and localpathprovisioner are in kube-system / deployements. It doesn't appear that any traefik is installed with fresh pull or the repo and pr-27. |
Fixed
|
Okay @garutilorenzo, I pulled and then couldn't clear the cluster config with terraform destroy, so never tried. Are you planning on merging the previous commits or still testing? Basic tests for me had it working fine. I was unable to route cloudflared directly to traefik2 internal ip, but that was probably outside the scope of your changes. |
Added support for traefik2