rewrite all links to issues to k8s links

cluster/gce/util.sh

@@ -636,7 +636,7 @@ function kube-up {
   # Generate a bearer token for this cluster. We push this separately
   # from the other cluster variables so that the client (this
   # computer) can forget it later. This should disappear with
-  # https://github.com/GoogleCloudPlatform/kubernetes/issues/3168
+  # http://issue.k8s.io/3168
   KUBELET_TOKEN=$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64 | tr -d "=+/" | dd bs=32 count=1 2>/dev/null)
   KUBE_PROXY_TOKEN=$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64 | tr -d "=+/" | dd bs=32 count=1 2>/dev/null)
 
@@ -1083,7 +1083,7 @@ function kube-push {
   # is solved (because that's blocking automatic dynamic nodes from
   # working). The node-kube-env has to be composed with the KUBELET_TOKEN
   # and KUBE_PROXY_TOKEN.  Ideally we would have
-  # https://github.com/GoogleCloudPlatform/kubernetes/issues/3168
+  # http://issue.k8s.io/3168
   # implemented before then, though, so avoiding this mess until then.
 
   echo

cluster/juju/charms/trusty/kubernetes/hooks/lib/registrator.py

@@ -87,7 +87,7 @@ class Registrator:
             'message', '').startswith('The requested resource does not exist'):
             # There's something fishy in the kube api here (0.4 dev), first time we
             # go to register a new minion, we always seem to get this error.
-            # https://github.com/GoogleCloudPlatform/kubernetes/issues/1995
+            # http://issue.k8s.io/1995
             time.sleep(1)
             print("Retrying registration...")
             raise ValueError("Registration returned 500, retry")

cluster/saltbase/salt/kube-apiserver/init.sls

@@ -33,7 +33,7 @@
 # boot, run-salt will installs kube-apiserver.manifest files to
 # kubelet config directory before the installation of proper version
 # kubelet. Please see
-# https://github.com/GoogleCloudPlatform/kubernetes/issues/10122#issuecomment-114566063
+# http://issue.k8s.io/10122#issuecomment-114566063
 # for detail explanation on this very issue.
 /etc/kubernetes/manifests/kube-apiserver.manifest:
   file.managed:

cluster/saltbase/salt/kube-controller-manager/init.sls

@@ -2,7 +2,7 @@
 # The ordering of salt states for service docker, kubelet and
 # master-addon below is very important to avoid the race between
 # salt restart docker or kubelet and kubelet start master components.
-# Please see https://github.com/GoogleCloudPlatform/kubernetes/issues/10122#issuecomment-114566063
+# Please see http://issue.k8s.io/10122#issuecomment-114566063
 # for detail explanation on this very issue.
 /etc/kubernetes/manifests/kube-controller-manager.manifest:
   file.managed:

cluster/saltbase/salt/kube-scheduler/init.sls

@@ -2,7 +2,7 @@
 # The ordering of salt states for service docker, kubelet and
 # master-addon below is very important to avoid the race between
 # salt restart docker or kubelet and kubelet start master components.
-# Please see https://github.com/GoogleCloudPlatform/kubernetes/issues/10122#issuecomment-114566063
+# Please see http://issue.k8s.io/10122#issuecomment-114566063
 # for detail explanation on this very issue.
 /etc/kubernetes/manifests/kube-scheduler.manifest:
   file.managed:

cluster/update-storage-objects.sh

@@ -32,7 +32,7 @@ KUBECTL="${KUBE_OUTPUT_HOSTBIN}/kubectl"
 
 # List of resources to be updated.
 # TODO: Get this list of resources from server once
-# https://github.com/GoogleCloudPlatform/kubernetes/issues/2057 is fixed.
+# http://issue.k8s.io/2057 is fixed.
 declare -a resources=(
     "endpoints"
     "events"