mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-11-01 14:22:17 +00:00
d2c66d5909
The documentation defines a couple of replication-controller and service to provision a docker-registry somewhere on the cluster and have it available by the name viz. A record of kube-registry.default.svc.<clustername>. On each node, http-proxies are placed as daemon-set with the kube-registry DNS name set as upstream, so that the registry is available on each host under endpoint localhost:5000 Because in the documentation, selector-identifiers are the same for "upstream" registry and proxies, the proxies themselves register under the service intended for the upstream and now have themselves as upstream under a different port, where connection attempts result in "connection refused". Adapting selectors to be unique as in this patch fixes the problem. modified: cluster/addons/registry/README.md modified: cluster/addons/registry/registry-rc.yaml modified: cluster/addons/registry/registry-svc.yaml
18 lines
375 B
YAML
18 lines
375 B
YAML
apiVersion: v1
|
|
kind: Service
|
|
metadata:
|
|
name: kube-registry
|
|
namespace: kube-system
|
|
labels:
|
|
k8s-app: kube-registry-upstream
|
|
kubernetes.io/cluster-service: "true"
|
|
addonmanager.kubernetes.io/mode: Reconcile
|
|
kubernetes.io/name: "KubeRegistry"
|
|
spec:
|
|
selector:
|
|
k8s-app: kube-registry-upstream
|
|
ports:
|
|
- name: registry
|
|
port: 5000
|
|
protocol: TCP
|