kubespray/roles/kubernetes/kubeadm/templates/kubeadm-client.conf.v1alpha...

apiVersion: kubeadm.k8s.io/v1alpha1
kind: NodeConfiguration
caCertPath: {{ kube_cert_dir }}/ca.crt
token: {{ kubeadm_token }}
discoveryTokenAPIServers:
{% if kubeadm_config_api_fqdn is defined %}
- {{ kubeadm_config_api_fqdn }}:{{ loadbalancer_apiserver.port | default(kube_apiserver_port) }}
{% else %}
- {{ kubeadm_discovery_address }}
{% endif %}
discoveryTokenCACertHashes:
- sha256:{{ kubeadm_ca_hash.stdout }}
kubeadm support (#1631) * kubeadm support * move k8s master to a subtask * disable k8s secrets when using kubeadm * fix etcd cert serial var * move simple auth users to master role * make a kubeadm-specific env file for kubelet * add non-ha CI job * change ci boolean vars to json format * fixup * Update create-gce.yml * Update create-gce.yml * Update create-gce.yml 2017-09-14 02:00:51 +08:00			`apiVersion: kubeadm.k8s.io/v1alpha1`
			`kind: NodeConfiguration`
Upgrade kubernetes to v1.13.0 (#3810) * Upgrade kubernetes to v1.13.0 * Remove all precense of scheduler.alpha.kubernetes.io/critical-pod in templates * Fix cert dir * Use kubespray v2.8 as baseline for gitlab 2018-12-07 04:11:48 +08:00			`caCertPath: {{ kube_cert_dir }}/ca.crt`
kubeadm support (#1631) * kubeadm support * move k8s master to a subtask * disable k8s secrets when using kubeadm * fix etcd cert serial var * move simple auth users to master role * make a kubeadm-specific env file for kubelet * add non-ha CI job * change ci boolean vars to json format * fixup * Update create-gce.yml * Update create-gce.yml * Update create-gce.yml 2017-09-14 02:00:51 +08:00			`token: {{ kubeadm_token }}`
			`discoveryTokenAPIServers:`
controlPlaneEndpoint set up through load balancer should be possible … (#3888) * controlPlaneEndpoint set up through load balancer should be possible even in single master setups Enable load balancer for single-master setups Fixes an issue where single-master setups are not reachable using the usual admin.conf from outside the cluster. controlPlaneEndpoint set up through load balancer should be possible even in single master setups * add fix to other api versions * remove obsolete check completely * remove check, pass 2 * removes checks in client configuration * delete 'and' 2018-12-25 16:03:32 +08:00			`{% if kubeadm_config_api_fqdn is defined %}`
Fix ports for kubeadm client and master configs for ha setups 2018-09-02 00:02:52 +08:00			`- {{ kubeadm_config_api_fqdn }}:{{ loadbalancer_apiserver.port \| default(kube_apiserver_port) }}`
Fix kubeadm LB configure 1. join node add LB discoveryTokenAPIServers 2. kubeadm_config_api_fqdn support ipddress and domain_name 2018-08-20 21:17:48 +08:00			`{% else %}`
kubeadm_discovery_address should not contain proto (#4930) 2019-06-28 15:37:37 +08:00			`- {{ kubeadm_discovery_address }}`
Fix kubeadm LB configure 1. join node add LB discoveryTokenAPIServers 2. kubeadm_config_api_fqdn support ipddress and domain_name 2018-08-20 21:17:48 +08:00			`{% endif %}`
Fix kubeadm client conf Fix DiscoveryTokenCACertHashes key to discoveryTokenCACertHashes in kubeadm-client.conf 2018-07-20 15:15:27 +08:00			`discoveryTokenCACertHashes:`
Update Kubernetes to v1.9.0 (#2100) Update checksum for kubeadm Use v1.9.0 kubeadm params Include hash of ca.crt for kubeadm join Update tag for testing upgrades Add workaround for testing upgrades Remove scale CI scenarios because of slow inventory parsing in ansible 2.4.x. Change region for tests to us-central1 to improve ansible performance 2017-12-25 16:57:45 +08:00			`- sha256:{{ kubeadm_ca_hash.stdout }}`