d9cea93eb6
Also build the hyperkube docker image on-the-fly. This is only a temporary fix until the proposal in issue https://github.com/kubernetes/kubernetes/issues/28630 is implemented. Also, the new build/deployment method completely obviates this step. We use debian image instead of busybox and do not build hyperkube as a static binary yet. Wait until PR https://github.com/kubernetes/kubernetes/pull/26028 is merged to build static hyperkube binaries.
45 lines
1.3 KiB
YAML
45 lines
1.3 KiB
YAML
apiVersion: extensions/v1beta1
|
|
kind: Deployment
|
|
metadata:
|
|
name: {{.FEDERATION_CONTROLLER_MANAGER_DEPLOYMENT_NAME}}
|
|
namespace: {{.FEDERATION_NAMESPACE}}
|
|
labels:
|
|
app: federated-cluster
|
|
spec:
|
|
template:
|
|
metadata:
|
|
name: federation-controller-manager
|
|
labels:
|
|
app: federated-cluster
|
|
module: federation-controller-manager
|
|
spec:
|
|
volumes:
|
|
- name: ssl-certs
|
|
hostPath:
|
|
path: /etc/ssl/certs
|
|
containers:
|
|
- name: controller-manager
|
|
volumeMounts:
|
|
- name: ssl-certs
|
|
readOnly: true
|
|
mountPath: /etc/ssl/certs
|
|
image: {{.FEDERATION_CONTROLLER_MANAGER_IMAGE_REPO}}:{{.FEDERATION_CONTROLLER_MANAGER_IMAGE_TAG}}
|
|
command:
|
|
- /usr/local/bin/hyperkube
|
|
- federation-controller-manager
|
|
- --master=https://{{.FEDERATION_APISERVER_DEPLOYMENT_NAME}}:443
|
|
- --dns-provider={{.FEDERATION_DNS_PROVIDER}}
|
|
- --dns-provider-config={{.FEDERATION_DNS_PROVIDER_CONFIG}}
|
|
- --federation-name={{.FEDERATION_NAME}}
|
|
- --zone-name={{.DNS_ZONE_NAME}}
|
|
ports:
|
|
- containerPort: 443
|
|
name: https
|
|
- containerPort: 8080
|
|
name: local
|
|
env:
|
|
- name: POD_NAMESPACE
|
|
valueFrom:
|
|
fieldRef:
|
|
fieldPath: metadata.namespace
|