- Jun 28, 2018
-
-
southquist authored
-
- Jun 22, 2018
-
-
Yumo Yang authored
-
- Jun 21, 2018
-
-
rongzhang authored
-
- Jun 18, 2018
-
-
Matthew Mosesohn authored
-
- Jun 12, 2018
-
-
rongzhang authored
-
- Jun 07, 2018
-
-
rongzhang authored
-
- Jun 06, 2018
-
-
Matthew Mosesohn authored
-
- Jun 04, 2018
-
-
Ben Meier authored
-
Dmitry authored
-
Rong Zhang authored
-
- May 30, 2018
-
-
Matthew Mosesohn authored
-
- May 27, 2018
-
-
Oleg Ozimok authored
-
- May 22, 2018
-
-
dvazar authored
-
- May 18, 2018
-
-
dvazar 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.
-
- 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
-
Christopher J. Ruwe authored
-
- 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
-
- May 08, 2018
-
-
Ryo Nishikawa authored
-
Michal Rostecki authored
OpenSSL 1.1 package in openSUSE Tumbleweed is named openssl-1_1, not openssl-1_1_0.
-
- May 03, 2018
-
-
Miouge1 authored
-
- May 01, 2018
-
-
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
-
- Apr 26, 2018
-
-
Markos Chandras authored
This reverts commit 51f4e658.
-
- Apr 24, 2018
-
-
Matthew Mosesohn authored
-
- Apr 23, 2018
-
-
Matthew Mosesohn authored
-
Suzuka Asagiri authored
-
- Apr 22, 2018
-
-
Romain DEQUIDT authored
-
- Apr 19, 2018
-
-
Paul Montero authored
-
- Apr 12, 2018
-
-
Matthew Mosesohn authored
-
Chad Swenson authored
-
- Apr 11, 2018
-
-
Markos Chandras authored
Add path for certificate location for SUSE distributions. Also make sure the 'update-ca-certificates' command is executed on SUSE hosts as well.
-
Nirmoy Das authored
The openssl package on Tumbleweed is actually a virtual package covering openssl-1.0.0 and openssl-1.1.0 implementations. It defaults to 1.1.0 so when trying to install it and openssl-1.0.0 is installed, zypper fails with conflicts. As such, lets explicitly pull the package that we need which also updates the virtual one. Co-authored-by: Markos Chandras <mchandras@suse.de>
-
Markos Chandras authored
Add support for installing package dependencies and refreshing metadata on SUSE distributions Co-authored-by: Nirmoy Das <ndas@suse.de>
-
- Apr 10, 2018
-
-
Christian Phu authored
-