You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a few minutes, the ingress lb can't be access anymore.
Restart cluster
k3d cluster stop demo
k3d cluster start demo
I expect it will have the same block behavior. However, no matter what I do to the network policy, I was able to access the ingress lb. I tried to wait but it's still the same. Upon inspection, seems like before restarting the cluster, there are a lot of iptables rules from KUBE-ROUTER, but after restarting, the iptables have just a few rules.
I suspect that the embedded kube-router was not started upon restarting, or do I miss something here?
The text was updated successfully, but these errors were encountered:
Question / Where do you need Help?
Scope of your Question
k3d version
hereCluster setup
Apply
Apply deny all network policy to namespace kube-system
After a few minutes, the ingress lb can't be access anymore.
Restart cluster
I expect it will have the same block behavior. However, no matter what I do to the network policy, I was able to access the ingress lb. I tried to wait but it's still the same. Upon inspection, seems like before restarting the cluster, there are a lot of iptables rules from KUBE-ROUTER, but after restarting, the iptables have just a few rules.
I suspect that the embedded kube-router was not started upon restarting, or do I miss something here?
The text was updated successfully, but these errors were encountered: