- Jun 12, 2018
-
-
rongzhang authored
-
- Jun 08, 2018
-
-
Wong Hoi Sing Edison authored
-
- Jun 07, 2018
-
-
rongzhang authored
-
Wong Hoi Sing Edison authored
-
- Jun 06, 2018
-
-
Brad Beam authored
-
Brad Beam authored
-
Matthew Mosesohn authored
-
- Jun 04, 2018
-
-
Ben Meier authored
-
Dmitry authored
-
Rong Zhang authored
-
- May 31, 2018
-
-
Erwan Miran authored
-
- May 30, 2018
-
-
Matthew Mosesohn authored
-
- May 29, 2018
-
-
Erwan Miran authored
-
Dmitrii Shuvar authored
Changed /etc/systemd/system/docker.service.d/docker-options.conf file for successful parsing mount aguments try fix ci error previous commit
-
- May 28, 2018
-
-
dshuvar authored
fix error message: '[/etc/systemd/system/docker.service.d/docker-options.conf:3] Failed to parse mount flag , ignoring.'
-
Julien Girardin authored
-
Erwan Miran authored
-
- May 27, 2018
-
-
Oleg Ozimok authored
-
- May 21, 2018
-
-
Miouge1 authored
-
Mikhail Vasilenko authored
-
- May 16, 2018
-
-
Christopher J. Ruwe authored
The number of pods on a given node is determined by the --max-pods=k directive. When the address space is exhausted, no more pods can be scheduled even if from the --max-pods-perspective, the node still has capacity. The special case that a pod is scheduled and uses the node IP in the host network namespace is too "soft" to derive a guarantee. Comparing kubelet_max_pods with kube_network_node_prefix when given allows to assert that pod limits match the CIDR address space.
-
Aivars Sterns authored
-
- May 15, 2018
-
-
Matthew Mosesohn authored
* Upgrade k8s to 1.10.2 Bumped etcd version to 3.2.16 as recommended * Add ipvs fix for v1.10 * change flannel addons test to ha
-
Anatoly Rugalev authored
-
Christopher J. Ruwe authored
-
rongzhang authored
Upgrade kube-dns to 1.14.10 https://github.com/kubernetes/kubernetes/tree/master/cluster/addons/dns
-
- May 14, 2018
-
-
Christopher J. Ruwe authored
Almost certainly, the .kube/config file (YAML) should not be executable.
-
Miouge1 authored
-
- May 11, 2018
-
-
Matthew Mosesohn authored
* Move front-proxy-client certs back to kube mount We want the same CA for all k8s certs * Refactor vault to use a third party module The module adds idempotency and reduces some of the repetitive logic in the vault role Requires ansible-modules-hashivault on ansible node and hvac on the vault hosts themselves Add upgrade test scenario Remove bootstrap-os tags from tasks * fix upgrade issues * improve unseal logic * specify ca and fix etcd check * Fix initialization check bump machine size
-
woopstar authored
-
- May 08, 2018
-
-
Cédric de Saint Martin authored
-
Michal Rostecki authored
OpenSSL 1.1 package in openSUSE Tumbleweed is named openssl-1_1, not openssl-1_1_0.
-
woopstar authored
-
- May 02, 2018
-
-
Andreas Kruger authored
-
- May 01, 2018
-
-
ashon authored
-
Wong Hoi Sing Edison authored
-
Maxime Gaillard authored
-
- Apr 30, 2018
-
-
Tomasz Majchrowski authored
ISSUE-2706: Provide consistent usage of supplementary_addresses_in_ssl_keys across vault and script mode (#2707)
-
- Apr 29, 2018
-
-
mirwan authored
-
- Apr 27, 2018
-
-
mirwan authored
* sysctl file should be in defaults so that it can be overriden * Change sysctl_file_path to be consistent with roles/kubernetes/preinstall/defaults/main.yml
-