kubernetes-sigs
/
kubespray
mirror of https://github.com/kubernetes-sigs/kubespray.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
kubespray/roles/network_plugin/contiv/templates/contiv-etcd-proxy.yml.j2

39 lines
1.0 KiB
Plaintext
Raw Normal View History

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 09:06:52 +08:00
---
kind: DaemonSet
Add support for k8s v1.16.0-beta.2 (#5148) Cleaned up deprecated APIs: apps/v1beta1 apps/v1beta2 extensions/v1beta1 for ds,deploy,rs Add workaround for deploying helm using incompatible deployment manifest. Change-Id: I78b36741348f47a999df3841ee63cf4e6f377830
2019-09-11 03:06:55 +08:00
apiVersion: apps/v1
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 09:06:52 +08:00
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 19:29:13 +08: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 09:06:52 +08:00
labels:
k8s-app: contiv-etcd-proxy
spec:
selector:
matchLabels:
k8s-app: contiv-etcd-proxy
template:
metadata:
labels:
k8s-app: contiv-etcd-proxy
spec:
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 22:50:22 +08:00
priorityClassName: system-node-critical
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 09:06:52 +08:00
hostNetwork: true
Set dnsPolicy to ClusterFirstWithHostNet when hostNetwork is true (#4843)
2019-06-05 18:17:56 +08:00
dnsPolicy: ClusterFirstWithHostNet
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 09:06:52 +08:00
hostPID: true
Fix nodeselectors for contiv and nginx-ingress (#4662) * Fix nodeselectors for contiv and nginx-ingress Change-Id: Ib3eb6bd87193c69a90ee944c9164a0b6792c79ba * Set kube proxy mode to iptables for addons task Change-Id: Iff71a71f672405c74b4708c71db15ddc4391a53a
2019-04-29 14:36:19 +08:00
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: node-role.kubernetes.io/master
operator: DoesNotExist
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 09:06:52 +08: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 10:35:12 +08: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 09:06:52 +08:00
- name: ETCD_PROXY
value: "on"
- name: ETCD_INITIAL_CLUSTER
Add quote for etcd endpoints
2017-12-14 10:35:12 +08:00
value: '{{ contiv_etcd_endpoints }}'