The GCE Ingress controller used to expose a cluster-uid command line flag that users could modify to have their cloud resources tagged with a specific suffix. For the flag to take effect, one needed to restart the ingress controller. This was possible because in previous versions of Kubernetes, the Ingress controller ran as a cluster addon.
In Kubernetes 1.3, the Ingress controller runs on the master. If you'd still like to set the command line flag, you need to do 2 things: 1. Modify the ingress config map created in the kube-system namespace, via `kubectl edit`, and set the "uid" field to the uid you want. 2. Restart the Ingress controller. If you're on GCE, 2 involves sshing into your master and docker stop-ing the glbc container. If you're on GKE, reply privately to me and I'll have it restarted for you. The modified configmap is not detected automatically because of a bug. Sorry for the inconvenience. -- You received this message because you are subscribed to the Google Groups "Containers at Google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-containers. For more options, visit https://groups.google.com/d/optout.
