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
What happened:
If the default gw want to be explicitly removed or ICMP is not working at next-hop-address the probes are not going to work as expected.
What you expected to happen:
Probes to run when needed towards what user want to check.
We need to add some knobs to NNCP to activate/deactivate ping and dns proba and also set the address to ping or resolv.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
NodeNetworkState on affected nodes (use kubectl get nodenetworkstate <node_name> -o yaml):
What happened:
If the default gw want to be explicitly removed or ICMP is not working at next-hop-address the probes are not going to work as expected.
What you expected to happen:
Probes to run when needed towards what user want to check.
We need to add some knobs to NNCP to activate/deactivate ping and dns proba and also set the address to ping or resolv.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
NodeNetworkState
on affected nodes (usekubectl get nodenetworkstate <node_name> -o yaml
):NodeNetworkConfigurationPolicy
:kubectl get pods --all-namespaces -l app=kubernetes-nmstate -o jsonpath='{.items[0].spec.containers[0].image}'
):nmcli --version
)kubectl version
):The text was updated successfully, but these errors were encountered: