- Apr 12, 2018
-
-
Chad Swenson authored
-
- Mar 30, 2018
-
-
Matthew Mosesohn authored
Kubernetes makes this namespace automatically, so there is no need for kubespray to manage it.
-
Andreas Kruger authored
-
woopstar authored
-
- Mar 29, 2018
-
-
georgejdli authored
-
- Mar 24, 2018
-
-
Dann Bohn authored
-
- Mar 23, 2018
-
-
Dann Bohn authored
-
- Mar 20, 2018
-
-
Bharat Kunwar authored
As requested
-
Bharat Kunwar authored
-
Bharat Kunwar authored
-
Bharat Kunwar authored
-
Bharat Kunwar authored
Ensure that kube-apiserver will respond even if one of the nodes are down.
-
woopstar authored
-
- Mar 15, 2018
-
-
woopstar authored
-
Andreas Krüger authored
* Added option for encrypting secrets to etcd * Fix keylength to 32 * Forgot the default * Rename secrets.yaml to secrets_encryption.yaml * Fix static path for secrets file to use ansible variable * Rename secrets.yaml.j2 to secrets_encryption.yaml.j2 * Base64 encode the token * Fixed merge error * Changed path to credentials dir * Update path to secrets file which is now readable inside the apiserver container. Set better file permissions * Add encryption option to k8s-cluster.yml
-
- Mar 14, 2018
-
-
Andreas Krüger authored
Setting the following: ``` kube_kubeadm_controller_extra_args: address: 0.0.0.0 terminated-pod-gc-threshold: "100" ``` Results in `terminated-pod-gc-threshold: 100` in the kubeadm config file. But it has to be a string to work.
-
- Mar 13, 2018
-
-
Andreas Krüger authored
Explicitly defines the --kubelet-preferred-address-types parameter #2418 Fixes #2453
-
- Mar 05, 2018
-
-
Ayaz Ahmed Khan authored
to the API server configuration. This solves the problem where if you have non-resolvable node names, and try to scale the server by adding new nodes, kubectl commands start to fail for newly added nodes, giving a TCP timeout error when trying to resolve the node hostname against a public DNS.
-
- Mar 01, 2018
-
-
RongZhang authored
Add etcd-events cluster for kube-apiserver
-
- Feb 22, 2018
-
-
Nedim Haveric authored
-
- Feb 17, 2018
-
-
melkosoft authored
* Added cilium support * Fix typo in debian test config * Remove empty lines * Changed cilium version from <latest> to <v1.0.0-rc3> * Add missing changes for cilium * Add cilium to CI pipeline * Fix wrong file name * Check kernel version for cilium * fixed ci error * fixed cilium-ds.j2 template * added waiting for cilium pods to run * Fixed missing EOF * Fixed trailing spaces * Fixed trailing spaces * Fixed trailing spaces * Fixed too many blank lines * Updated tolerations,annotations in cilium DS template * Set cilium_version to iptables-1.9 to see if bug is fixed in CI * Update cilium image tag to v1.0.0-rc4 * Update Cilium test case CI vars filenames * Add optional prometheus flag, adjust initial readiness delay * Update README.md with cilium info
-
Dann Bohn authored
-
- Feb 16, 2018
-
-
Miouge1 authored
-
- Feb 12, 2018
-
-
Maxim Krasilnikov authored
-
- Feb 09, 2018
-
-
Chia-liang Kao authored
`FAILED! => {"changed": false, "msg": "AnsibleFilterError: Version comparison: unorderable types: str() < int()"}`
-
mlushpenko authored
-
- Feb 07, 2018
- Feb 05, 2018
-
-
woopstar authored
-
Maxim Krasilnikov authored
-
- Feb 01, 2018
-
-
Dann Bohn authored
-
- Jan 30, 2018
-
-
rong.zhang authored
Support ipvs mode for kube-proxy
-
- Jan 23, 2018
-
-
Virgil Chereches authored
Renamed variable from disable_volume_zone_conflict to volume_cross_zone_attachment and removed cloud provider condition; fix identation
-
- Jan 18, 2018
-
-
Virgil Chereches authored
-
- Jan 12, 2018
-
-
Virgil Chereches authored
-
Virgil Chereches authored
-
- Dec 25, 2017
-
-
Matthew Mosesohn authored
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
-
- Dec 05, 2017
-
-
Chad Swenson authored
This allows `kube_apiserver_insecure_port` to be set to 0 (disabled). Rework of #1937 with kubeadm support Also, fixed an issue in `kubeadm-migrate-certs` where the old apiserver cert was copied as the kubeadm key
-
- Nov 29, 2017
-
-
Steven Hardy authored
* Allow setting --bind-address for apiserver hyperkube This is required if you wish to configure a loadbalancer (e.g haproxy) running on the master nodes without choosing a different port for the vip from that used by the API - in this case you need the API to bind to a specific interface, then haproxy can bind the same port on the VIP: root@overcloud-controller-0 ~]# netstat -taupen | grep 6443 tcp 0 0 192.168.24.6:6443 0.0.0.0:* LISTEN 0 680613 134504/haproxy tcp 0 0 192.168.24.16:6443 0.0.0.0:* LISTEN 0 653329 131423/hyperkube tcp 0 0 192.168.24.16:6443 192.168.24.16:58404 ESTABLISHED 0 652991 131423/hyperkube tcp 0 0 192.168.24.16:58404 192.168.24.16:6443 ESTABLISHED 0 652986 131423/hyperkube This can be achieved e.g via: kube_apiserver_bind_address: 192.168.24.16 * Address code review feedback * Update kube-apiserver.manifest.j2
-