Update install-anp.yaml #101
Conversation
don't use the default queue number to avoid conflict with kindnet
k8s-ci-robot
added
the
cncf-cla: yes
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
approved
| @@ -80,7 +80,7 @@ spec: | |||
| - name: kube-network-policies | |||
| image: registry.k8s.io/networking/kube-network-policies:v0.6.0 | |||
| command: ["/bin/netpol"] | |||
| args: ["-v=2", "-admin-network-policy=true", "-baseline-admin-network-policy=true","--hostname-override=$(MY_NODE_NAME)"] | |||
| args: ["-v=2", "-admin-network-policy=true", "-baseline-admin-network-policy=true","--hostname-override=$(MY_NODE_NAME)","--nfqueue-id=99"] | |||
There was a problem hiding this comment.
lgtm, since default I guess is 0 what kube-net-pol uses will conflict with that kube-net-pol in kind uses so safer to use a custom value..
There was a problem hiding this comment.
default is 100
kube-network-policies/cmd/main.go
Line 44 in d3eeb55
There was a problem hiding this comment.
so kube-net-pol in KIND uses 100 and hence the conflict... when we install it separately.. I see
|
/lgtm |
k8s-ci-robot
added
the
lgtm
don't use the default queue number to avoid conflict with kindnet