c12s-kubespray/roles/network_plugin/contiv/templates/contiv-etcd-proxy.yml.j2

---
kind: DaemonSet
apiVersion: extensions/v1beta1
metadata:
  name: contiv-etcd-proxy
  namespace: kube-system
  labels:
    k8s-app: contiv-etcd-proxy
spec:
  selector:
    matchLabels:
      k8s-app: contiv-etcd-proxy
  template:
    metadata:
      labels:
        k8s-app: contiv-etcd-proxy
      annotations:
        scheduler.alpha.kubernetes.io/critical-pod: ''
    spec:
{% if kube_version is version('v1.11.1', '>=') %}
      priorityClassName: system-node-critical
{% endif %}
      hostNetwork: true
      hostPID: true
      nodeSelector:
        node-role.kubernetes.io/node: "true"
      containers:
        - name: contiv-etcd-proxy
          image: {{ contiv_etcd_image_repo }}:{{ contiv_etcd_image_tag }}
          env:
            - name: ETCD_LISTEN_CLIENT_URLS
              value: 'http://127.0.0.1:{{ contiv_etcd_listen_port }}'
            - name: ETCD_PROXY
              value: "on"
            - name: ETCD_INITIAL_CLUSTER
              value: '{{ contiv_etcd_endpoints }}'
Split contiv etcd and etcd-proxy into two daemonsets Putting contiv etcd and etcd-proxy into the same daemonset and manage the difference by a env file is not good for scaling (adding nodes). This commit split them into two daemonsets so that when adding nodes, k8s could automatically starting a etcd-proxy on new nodes without need to run related play that putting env file. 2017-12-06 01:06:52 +00:00			`---`
			`kind: DaemonSet`
			`apiVersion: extensions/v1beta1`
			`metadata:`
			`name: contiv-etcd-proxy`
Stop templating kube-system namespace and creating it (#2545) Kubernetes makes this namespace automatically, so there is no need for kubespray to manage it. 2018-03-30 11:29:13 +00:00			`namespace: kube-system`
Split contiv etcd and etcd-proxy into two daemonsets Putting contiv etcd and etcd-proxy into the same daemonset and manage the difference by a env file is not good for scaling (adding nodes). This commit split them into two daemonsets so that when adding nodes, k8s could automatically starting a etcd-proxy on new nodes without need to run related play that putting env file. 2017-12-06 01:06:52 +00:00			`labels:`
			`k8s-app: contiv-etcd-proxy`
			`spec:`
			`selector:`
			`matchLabels:`
			`k8s-app: contiv-etcd-proxy`
			`template:`
			`metadata:`
			`labels:`
			`k8s-app: contiv-etcd-proxy`
			`annotations:`
			`scheduler.alpha.kubernetes.io/critical-pod: ''`
			`spec:`
Fix ansible syntax to avoid ansible deprecation warnings (#3512) * failed * version_compare * succeeded * skipped * success * version_compare becomes version since ansible 2.5 * ansible minimal version updated in doc and spec * last version_compare 2018-10-16 22:33:30 +00:00			`{% if kube_version is version('v1.11.1', '>=') %}`
Adding pod priority for all the components. (#3361) * Changes to assign pod priority to kube components. * Removed the boolean flag pod_priority_assignment * Created new priorityclass k8s-cluster-critical * Created new priorityclass k8s-cluster-critical * Fixed the trailing spaces * Fixed the trailing spaces * Added kube version check while creating Priority Class k8s-cluster-critical * Moved k8s-cluster-critical.yml * Moved k8s-cluster-critical.yml to kube_config_dir 2018-09-25 14:50:22 +00:00			`priorityClassName: system-node-critical`
			`{% endif %}`
Split contiv etcd and etcd-proxy into two daemonsets Putting contiv etcd and etcd-proxy into the same daemonset and manage the difference by a env file is not good for scaling (adding nodes). This commit split them into two daemonsets so that when adding nodes, k8s could automatically starting a etcd-proxy on new nodes without need to run related play that putting env file. 2017-12-06 01:06:52 +00:00			`hostNetwork: true`
			`hostPID: true`
contiv 1.2.1 2018-09-17 14:45:05 +00:00			`nodeSelector:`
			`node-role.kubernetes.io/node: "true"`
Split contiv etcd and etcd-proxy into two daemonsets Putting contiv etcd and etcd-proxy into the same daemonset and manage the difference by a env file is not good for scaling (adding nodes). This commit split them into two daemonsets so that when adding nodes, k8s could automatically starting a etcd-proxy on new nodes without need to run related play that putting env file. 2017-12-06 01:06:52 +00:00			`containers:`
			`- name: contiv-etcd-proxy`
			`image: {{ contiv_etcd_image_repo }}:{{ contiv_etcd_image_tag }}`
			`env:`
			`- name: ETCD_LISTEN_CLIENT_URLS`
Add quote for etcd endpoints 2017-12-14 02:35:12 +00:00			`value: 'http://127.0.0.1:{{ contiv_etcd_listen_port }}'`
Split contiv etcd and etcd-proxy into two daemonsets Putting contiv etcd and etcd-proxy into the same daemonset and manage the difference by a env file is not good for scaling (adding nodes). This commit split them into two daemonsets so that when adding nodes, k8s could automatically starting a etcd-proxy on new nodes without need to run related play that putting env file. 2017-12-06 01:06:52 +00:00			`- name: ETCD_PROXY`
			`value: "on"`
			`- name: ETCD_INITIAL_CLUSTER`
Add quote for etcd endpoints 2017-12-14 02:35:12 +00:00			`value: '{{ contiv_etcd_endpoints }}'`