Hello community,
here is the log from the commit of package kubernetes-salt for openSUSE:Factory
checked in at 2018-12-04 20:58:36
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/kubernetes-salt (Old)
and /work/SRC/openSUSE:Factory/.kubernetes-salt.new.19453 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "kubernetes-salt"
Tue Dec 4 20:58:36 2018 rev:36 rq:653886 version:4.0.0+git_r961_7c23cdf
Changes:
--------
--- /work/SRC/openSUSE:Factory/kubernetes-salt/kubernetes-salt.changes
2018-10-29 14:58:23.921972167 +0100
+++
/work/SRC/openSUSE:Factory/.kubernetes-salt.new.19453/kubernetes-salt.changes
2018-12-04 20:58:42.160562233 +0100
@@ -1,0 +2,153 @@
+Tue Dec 4 10:09:07 UTC 2018 - Containers Team <containers-bugow...@suse.de>
+
+- Commit 99a0d11 by Maximilian Meister mmeis...@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 <mmeis...@suse.de>
+
+
+-------------------------------------------------------------------
+Mon Nov 19 08:55:20 UTC 2018 - containers-bugow...@suse.de
+
+- Commit bf5feaa by Florian Bergmann fbergm...@suse.de
+ Use the correct key to access the etcd_version from pillars
+
+ Commit 962a830 by Florian Bergmann fbergm...@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.
+
+
+-------------------------------------------------------------------
+Fri Nov 16 12:15:13 UTC 2018 - containers-bugow...@suse.de
+
+- Commit 97f9dab by emilianolangella emiliano.lange...@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.
+
+
+-------------------------------------------------------------------
+Thu Nov 15 17:46:08 UTC 2018 - containers-bugow...@suse.de
+
+- Commit 11c82a5 by Maximilian Meister mmeis...@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 <mmeis...@suse.de>
+
+
+-------------------------------------------------------------------
+Thu Nov 15 12:18:47 UTC 2018 - containers-bugow...@suse.de
+
+- Commit b4c0474 by Michal Jura mj...@suse.com
+ Add log rotation options to docker daemon (bug#1114832)
+
+
+-------------------------------------------------------------------
+Thu Nov 15 08:52:28 UTC 2018 - containers-bugow...@suse.de
+
+- Commit b4c0474 by Michal Jura mj...@suse.com
+ Add log rotation options to docker daemon (bug#1114832)
+
+
+-------------------------------------------------------------------
+Thu Nov 8 16:55:28 UTC 2018 - containers-bugow...@suse.de
+
+- Commit 9ef0f58 by David Helkowski dhelkow...@suse.com
+ Add support for OIDC connectors to dex configmap
+
+
+-------------------------------------------------------------------
+Tue Nov 6 13:59:59 UTC 2018 - containers-bugow...@suse.de
+
+- Commit 793d856 by Rafael Fernández López eresli...@ereslibre.es
+ Add a whitelist for returned events so we only save events that we care about
+
+ Fixes: bsc#1112967
+
+
+-------------------------------------------------------------------
+Tue Oct 30 10:39:24 UTC 2018 - containers-bugow...@suse.de
+
+- Commit e501ce9 by Rafael Fernández López eresli...@ereslibre.es
+ Fix tests
+
+ Commit 90423b6 by Rafael Fernández López eresli...@ereslibre.es
+ * Add more test cases for `caasp_etcd`
+ * Update to allow `etcdctl` API version 3
+
+ Fixes: bsc#1098433 Fixes: bsc#1098064 Fixes: bsc#1098161
+
+ Commit e5efa1c by Rafael Fernández López eresli...@ereslibre.es
+ Allow `etcd` to grow as required and shrink to optimal etcd cluster sizes on
+ corner cases.
+
+ Improve `etcd` configuration handling to allow it to grow as needed. This
+ change includes:
+
+ * Adding several masters at the same time
+ ** `etcd` will grow instance by instance still, as recommended by the
+ `etcd` administration best practices.
+
+ * Try to use the current endpoints reported by `etcd`. This makes much
+ easier to grow several instances one by one without having to relay
+ on internal hacks to properly set up `ETCD_INITIAL_CLUSTER` environment
+ variable.
+
+ * Add helper methods that allow us to list current members (active and
+ unstarted)
+
+ * Differentiate between the first bootstrap (`ETCD_INITIAL_CLUSTER_STATE`
+ defaults to `new`) and *any* other run, where `ETCD_INITIAL_CLUSTER_STATE`
+ will be `existing`, as the `etcd` cluster is already running.
+
+ When we grow, we take into account the golden ratio; however, when shrinking
+ the cluster we don't. It might happen that a cluster ends up with not
+ recommended etcd number of nodes (2, 4, 6...) depending on how it grew before
+ and how it shrank.
+
+ This logic makes sure that we are always on an etcd golden ratio, also on
+ corner cases when removing nodes.
+
+ Fixes: bsc#1098433 Fixes: bsc#1098064 Fixes: bsc#1098161
+
+
+-------------------------------------------------------------------
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ kubernetes-salt.spec ++++++
--- /var/tmp/diff_new_pack.q2l2L4/_old 2018-12-04 20:58:42.800561527 +0100
+++ /var/tmp/diff_new_pack.q2l2L4/_new 2018-12-04 20:58:42.800561527 +0100
@@ -12,7 +12,7 @@
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.
-# Please submit bugfixes or comments via http://bugs.opensuse.org/
+# Please submit bugfixes or comments via https://bugs.opensuse.org/
#
@@ -33,7 +33,7 @@
Name: kubernetes-salt
%define gitrepo salt
-Version: 4.0.0+git_r937_e9764fe
+Version: 4.0.0+git_r961_7c23cdf
Release: 0
BuildArch: noarch
Summary: Production-Grade Container Scheduling and Management
++++++ master.tar.gz ++++++
++++ 1927 lines of diff (skipped)
