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

HTTP -> HTTPS redirection does not work in 1.8 cluster with AWS cert manager #639

Closed
tamalsaha opened this issue Oct 17, 2017 · 7 comments
Closed

Comments

@tamalsaha
Copy link
Member

@tamalsaha tamalsaha commented Oct 17, 2017

The underlying issue is that in Kubernetes 1.8, Services do not allow duplicate targetPort .
kubernetes/kubernetes#47222

@tamalsaha

This comment has been minimized.

Copy link
Member Author

@tamalsaha tamalsaha commented Oct 17, 2017

There is not much we can do. As a work around, users can avoid HTTP -> HTTPS redirection by setting annotation ingress.kubernetes.io/ssl-redirect: "false" .

cc: @julianvmodesto

@julianvmodesto

This comment has been minimized.

Copy link
Contributor

@julianvmodesto julianvmodesto commented Oct 18, 2017

Yikes!

Less relevant to my use case currently because we're switching to using NodePort Services/Ingresses instead of LoadBalancer Services/Ingresses, but if we want to switch back this is unfortunate :(

@julianvmodesto

This comment has been minimized.

Copy link
Contributor

@julianvmodesto julianvmodesto commented Oct 18, 2017

That issue is really interesting btw, thanks for the tag. Seems like a lot of projects also use that behavior. Will continue to watch upstream...

@tamalsaha

This comment has been minimized.

Copy link
Member Author

@tamalsaha tamalsaha commented Oct 18, 2017

Why are you switching to NodePort mode? Are you using the new ALB/NLB stuff ?

@julianvmodesto

This comment has been minimized.

Copy link
Contributor

@julianvmodesto julianvmodesto commented Oct 18, 2017

We encountered this upstream issue with LoadBalancer Services where instances would all be deregistered them re-registered to our ELB on cluster scaling very occasionally: kubernetes/kubernetes#34267

@tamalsaha

This comment has been minimized.

Copy link
Member Author

@tamalsaha tamalsaha commented Oct 18, 2017

That issue is open since Oct, 2016 and not fixed yet. Sigh! Thanks for the info.

@tamalsaha

This comment has been minimized.

Copy link
Member Author

@tamalsaha tamalsaha commented Nov 3, 2017

This is being reverted kubernetes/kubernetes#53576

@tamalsaha tamalsaha closed this Nov 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.