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

Ingress with both http and https enabled yields two separate IPs #993

Closed
skmatti opened this issue Jan 16, 2020 · 1 comment · Fixed by #994
Closed

Ingress with both http and https enabled yields two separate IPs #993

skmatti opened this issue Jan 16, 2020 · 1 comment · Fixed by #994
Assignees

Comments

@skmatti
Copy link
Contributor

skmatti commented Jan 16, 2020

The following sequence of configuration changes to an ingress leads to split IPs with ingress v1.8 (with enable-delete-unused-frontends set)

  1. Create an Ingress with both http and https enabled. (Static IP is used)
  2. Disable http (Static IP is retained and used by https forwarding rule)
  3. Re-enable http (New ephemeral IP is created for http forwarding rule, but https forwarding rule uses static IP)

Ingress versions older than v1.8 do not run this issue because http forwarding rule is not deleted when disabled. But, manual deletion of http forwarding rule results in separate IPs.

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

Successfully merging a pull request may close this issue.

2 participants