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.

Sign up for GitHub

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

Add workaround for Firewall bug in ingress-gce #440

Merged
merged 2 commits into from
Jun 3, 2020
Merged

Add workaround for Firewall bug in ingress-gce #440

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7abcf0c
Add workaround for Firewall bug in ingress-gce
zohrehj Jun 3, 2020
c6cac90
Update README.md
zohrehj Jun 3, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions kubernetes/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -240,3 +240,6 @@ If the cluster has issues, there are a few things you can check:
* Follow a troubleshooting guide. Examples are
[this](https://learnk8s.io/troubleshooting-deployments) and
[this](https://kubernetes.io/docs/tasks/debug-application-cluster/debug-cluster/).
* As of now there is a known issue with Firewalls in ingress-gce. If you notice this issue showing up in
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest: reference kubernetes/ingress-gce#485 and/or kubernetes/ingress-gce#584

ingress logs, follow the steps provided in https://github.com/kubernetes/ingress-gce/issues/584, and give
Kubernetes Engine Service Agent (service account) `roles/compute.securityAdmin` and `roles/compute.networkAdmin`.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest: Add an alternative:

  1. Run kubectl describe ingress <ingress-name>
  2. Look at the suggested commands under "Events", in the form of "Firewall change required by network admin: <gcloud command>". Run each of the suggested commands.