-
Notifications
You must be signed in to change notification settings - Fork 228
Fix network policy #667
Fix network policy #667
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of comments
- namespaceSelector: {} | ||
podSelector: | ||
matchLabels: | ||
app: nginx-ingress |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why was this removed? Shouldn't it be ingress-nginx now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I relocated it to edge-router and gateway specific policies since afaict those are the only openfaas
pods ingress nginx needs to access.
- namespaceSelector: {} | ||
podSelector: | ||
matchLabels: | ||
app.kubernetes.io/name: ingress-nginx |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to keep both for legacy users? ingress-nginx and nginx-ingress?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
re-added the old label
95ac2e4
Please could you raise an issue with the issues you've found? The Nginx Ingress label name change is here: As I mentioned on Slack, I think it will take me a day away from work to verify this PR, so whatever we can do to make that smoother would go a long way. |
audit-event needs access to gateway with echo function as the default slack_url Fixes openfaas#669 Signed-off-by: Brandon Wilson <[email protected]>
Update helm chart network policy. Signed-off-by: Brandon Wilson <[email protected]>
95ac2e4
to
6031e1b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@wilsonianb did you get an issue raised? If so please link it back here through adding a comment or editing its description - GitHub will work out the rest. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved
There was a much bigger PR I remembered, was that not needed? Can you link it here if it is still around? |
here's the original changeset
|
Description
Fixes #669 by giving
audit-event
access togateway
since echo function is the defaultslack_url
.This would need to be reflected in ofc-bootstrap's stack.yml (as should 2c836f3).
Re-adds support for legacy ingress nginx network policy label (1713d32).
How Has This Been Tested?
Tested on k3s with calico
Followed ofc-bootstrap user guide (without oauth) with network policies enabled and
openfaas_cloud_version
set to0.14.1
Used pre-release ofc-bootstrap v0.9.6 with
role: openfaas-system
label added toaudit-event
intemplates/stack.yml
.GitHub events no longer time out with this PR change.
Ran helm chart tests with
go test
in$GO_PATH/src/openfaas-cloud/chart/test/
and randiff
onchart/test/tmp/openfaas-cloud/templates/network-policy/ns-openfaas-net-policy.yml
andyaml/network-policy/ns-openfaas-net-policy.yml
files.How are existing users impacted? What migration steps/scripts do we need?
Should only help OpenFaaS Cloud cluster administrators who had network policies previously enabled and re-run ofc-bootstrap.
Checklist:
I have:
git commit -s