Nuke NetworkPolicy

gistfile1.txt

#documented steps, in the rancher docs, to identify/clean up network policies from rancher/k8s. if your k8s cluster started with an early version of rancher, chances are you have network policies defined. This could prevent traffic routing from the ingress controller to rancher.
#check if cluster has a network policy enabled
kubectl get cluster -o=custom-columns=ID:.metadata.name,NAME:.spec.displayName,NETWORKPOLICY:.spec.enableNetworkPolicy

#disable the network policy at the cluster level
kubectl get cluster -o jsonpath='{range .items[*]}{@.metadata.name}{"\n"}{end}' | xargs -I {} kubectl patch cluster {} --type merge -p '{"spec": {"enableNetworkPolicy": false}}'

#delete network policies for each of the following namespaces
for namespace in kube-system kube-public cattle-system cattle-alerting cattle-logging cattle-pipeline ingress-nginx; do
    kubectl -n $namespace delete networkpolicy --all;
done

#smaller delete hammer
for namespace in kube-system kube-public cattle-system ingress-nginx; do
    echo "$namespace";
    kubectl -n $namespace delete networkpolicy --all;
done