Make minimal modifications to make dual-stack-negs work with self-managed controller

docs/deploy/gke/README.md

@@ -122,3 +122,17 @@ issue.
 If you have issues with the controller after the script execution and you do not
 know what it causing it, invoke the script in its cleanup mode. The is a quick
 and simple way of going back to how everything was before.
+
+## Script stuck on "Waiting for old GLBC service and pod to be removed..."
+
+This is usually the case when turning off HTTPLoadBalancing in the cluster does
+not delete the resources for the default-http-backend. This can be easily
+resolved by manually deleting them:
+
+```
+# Delete the service for the default-http-backend.
+kubectl delete svc -n kube-system default-http-backend
+
+# Delete the deployment for the default-http-backend.
+kubectl delete deploy -n kube-system l7-default-backend
+```

docs/deploy/resources/glbc.yaml

@@ -64,7 +64,7 @@ spec:
         - --gce-ratelimit=ga.HealthChecks.Get,qps,1.8,1
         - --gce-ratelimit=alpha.HealthChecks.Get,qps,1.8,1
         - --enable-frontend-config
-        - --enable-endpoint-slices
+        - --enable-dual-stack-neg
       volumes:
       - name: google-cloud-key
         secret:

docs/deploy/resources/rbac.yaml

@@ -76,6 +76,12 @@ rules:
 - apiGroups: ["networking.k8s.io"]
   resources: ["ingressclasses"]
   verbs: ["get", "list", "watch", "update", "create", "patch"]
+- apiGroups: ["coordination.k8s.io"]
+  resources: ["leases"]
+  verbs: ["*"]
+- apiGroups: ["discovery.k8s.io"]
+  resources: ["endpointslices"]
+  verbs: ["get", "list", "watch"]
 ---
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding