Revisions of kubernetes-salt
Containers Team (containersteam)
committed
(revision 357)
new commit from concourse: Commit b91cbbf by Miquel Sabaté Solà msabate@suse.com caasp_filters: properly parse IP addresses As it appears, for Python 2 Salt is using a custom module for providing the ipaddress from Python 3. This implementation turned out to have bugs (e.g. accepting something70.domain.net as a valid IPv4 record). I've re-implemented the is_ip* functions so they are using socket.inet_pton instead, which should suffice in our use case. bsc#1123291
Containers Team (containersteam)
committed
(revision 356)
new commit from concourse: Commit 73b87c4 by Maximilian Meister mmeister@suse.de [bsc#1116049] don't fail timing out on a drain we want to ensure that the platform 'survives' even if an application is not 'drainable' it already happened that some applications are getting stuck in a termination process and won't recover anymore. This can happen for various reasons (volume not detachable, podDisruptionBudget ...) as we are using the drain during every update, we are likely to run into this issue multiple times per cluster Signed-off-by: Maximilian Meister <mmeister@suse.de>
Containers Team (containersteam)
committed
(revision 355)
new commit from concourse: Commit d1af183 by Miquel Sabaté Solà msabate@suse.com Added instructions for running unit tests Signed-off-by: Miquel Sabaté Solà <msabate@suse.com>
buildservice-autocommit
accepted
request 669475
from
Containers Team (containersteam)
(revision 354)
baserev update by copy to link target
Jordi Massaguer (jordimassaguerpla)
committed
(revision 353)
fix changelog
Containers Team (containersteam)
committed
(revision 352)
new commit from concourse: Commit ed1b79e by Maximilian Meister mmeister@suse.de adapt flannel config for k8s > 1.12 this is already fixed in higher flannel versions (0.11.1) see: https://github.com/coreos/flannel/commit/bc79dd1505b0c8681ece4de4c0d86c5cd2643275 Signed-off-by: Maximilian Meister <mmeister@suse.de> Commit b2ae73b by Maximilian Meister mmeister@suse.de cadvisor-port flag is not valid anymore it has been deprecated since 1.10 and now dropped Signed-off-by: Maximilian Meister <mmeister@suse.de>
Containers Team (containersteam)
committed
(revision 351)
new commit from concourse: Commit 9f8728a by Michal Jura mjura@suse.com [CPI] Sanitize the values from the pillar (bsc#1122439)
Containers Team (containersteam)
committed
(revision 350)
new commit from concourse: Commit 7776b4b by Rafael Fernández López ereslibre@ereslibre.es Enable `ExperimentalCriticalPodAnnotation` feature gate in the kubelet Fixes: bsc#1114812
Containers Team (containersteam)
committed
(revision 349)
new commit from concourse: Commit a42b893 by Rafael Fernández López ereslibre@ereslibre.es Use `jenkins-tox-container` image instead of `jenkins-tox3-container` image. Maintenance update 9039 on opensuse increased `pluggy` version to 0.6.0. This rendered `python3-tox` unusable with that pluggy version, as the current version in OBS requires `pluggy` (pluggy>=0.3.0,<0.4.0). Since this is making salt pipelines fail we are including the `python3` environment on the regular `jenkins-tox-container`. [1] https://build.suse.de/request/show/182868
Containers Team (containersteam)
committed
(revision 348)
new commit from concourse: Commit 0da4671 by Danny Sauer dsauer@suse.com Minor cleanup for flake8 Minor changes to fix flake8 warnings - use raw strings in regex methods - inline-suppress an incorrect unused variable warning - update to flake8 version 3.6.0 - switch flake8 config to use new extend-ignore option ("ignore" is an exclusive list, so overrides the default ignored list)
Containers Team (containersteam)
committed
(revision 347)
new commit from concourse: Commit 98c8b40 by Maximilian Meister mmeister@suse.de in python3 strings need to be decoded from binary objects Signed-off-by: Maximilian Meister <mmeister@suse.de>
buildservice-autocommit
accepted
request 653886
from
Containers Team (containersteam)
(revision 346)
baserev update by copy to link target
Containers Team (containersteam)
committed
(revision 345)
new commit from concourse: Commit 99a0d11 by Maximilian Meister mmeister@suse.de Added migration orchestration. This orchestration will run transactional-update salt migration to change the cluster to a new channel. bsc#1109785 Signed-off-by: Maximilian Meister <mmeister@suse.de>
Containers Team (containersteam)
committed
(revision 344)
new commit from concourse: Commit bf5feaa by Florian Bergmann fbergmann@suse.de Use the correct key to access the etcd_version from pillars Commit 962a830 by Florian Bergmann fbergmann@suse.de Only add a new etcd member if no alias is already a member When adding a new member to etcd, it might happen that it is already part of the cluster using one of the aliases - when migrating from v2 to v3 it seems common that the default nodename changes. If this is the case it should not be added again with the new nodename, as one node can not have 2 etcd members.
Containers Team (containersteam)
committed
(revision 343)
new commit from concourse: Commit 97f9dab by emilianolangella emiliano.langella@suse.com Fix bsc#1116005: Dex pods should run only on master nodes Dex pods should run only on master nodes due to firewall/security policies that could be applied to workers nodes.
Containers Team (containersteam)
committed
(revision 342)
new commit from concourse: Commit 11c82a5 by Maximilian Meister mmeister@suse.de don't run haproxy states when not really needed in case of a kubernetes update from 1.9 to 1.10 we can't afford to stop kubernetes through the haproxy states, because it will not be able to restart as the --config file flag has changed between those releases the update orchestration fails in the sanity check of the state all-workers-3.0-pre-clean-shutdown because the new kubelet configuration is already applied, but the old kubernetes version is still running before the reboot This is a corner case and our other states would have to be adapted as well to re-run configs when a node gets accidentally rebooted and the config hasn't been applied yet. Furthermore this is only an issue coming from v2 during migration to v3 - so the case that this happens is even rarer. Trying to run this state on each worker would require a check for /etc/caasp/haproxy/haproxy.cfg to safely determine if it needs to be run or not, but it is not possible to use salt runners with a target to determine if this file exists on all worker nodes. salt.runners.salt.cmd doesn't accept targets salt.runners.salt.execute only exists since salt2017.7.0 which might not be present yet for a user that hasn't installed the salt upgrade yet. bsc#1114645 Signed-off-by: Maximilian Meister <mmeister@suse.de>
Containers Team (containersteam)
committed
(revision 341)
new commit from concourse: Commit b4c0474 by Michal Jura mjura@suse.com Add log rotation options to docker daemon (bug#1114832)
Containers Team (containersteam)
committed
(revision 340)
new commit from concourse: Commit b4c0474 by Michal Jura mjura@suse.com Add log rotation options to docker daemon (bug#1114832)
Containers Team (containersteam)
committed
(revision 339)
new commit from concourse: Commit 9ef0f58 by David Helkowski dhelkowski@suse.com Add support for OIDC connectors to dex configmap
Containers Team (containersteam)
committed
(revision 338)
new commit from concourse: Commit 793d856 by Rafael Fernández López ereslibre@ereslibre.es Add a whitelist for returned events so we only save events that we care about Fixes: bsc#1112967
Displaying revisions 21 - 40 of 377