openSUSE Build Service

Overview Repositories Revisions Requests Users Attributes Meta

Revisions of kubernetes-salt

Containers Team (containersteam) committed almost 6 years ago (revision 297)

new commit from concourse: Commit fd3507f by Kiall Mac Innes kiall@macinnes.ie
 Stop kubelet before any other services
 
 Explicitly stop kubelet before any other services. If cri.stop is ran in
 parallel to or before kubelet.stop, kubelet will be unable to successfully
 drain.
 
 bsc#1085980

buildservice-autocommit accepted request 618553 from

Containers Team (containersteam) almost 6 years ago (revision 296)

baserev update by copy to link target

Containers Team (containersteam) committed almost 6 years ago (revision 295)

new commit from concourse: Commit 8a746bc by Flavio Castelli fcastelli@suse.com
 Do not install recommends
 
 Instruct salt to not install recommended packages.
 
 feature#do-not-install-recommends
 
 Signed-off-by: Flavio Castelli <fcastelli@suse.com>

Containers Team (containersteam) committed almost 6 years ago (revision 294)

new commit from concourse: Commit 97d8178 by Rafael Fernández López ereslibre@ereslibre.es
 Call to `mine.update` after `saltutil.sync_pillar` has been called.
 
 During an upgrade we want to call to `mine.update` after
 `saltutil.sync_pillar` has been called, because the `mine_functions` reside
 on the pillar, we first want to make sure to sync that, and update the mine
 afterwards. Otherwise, we risk doing this in a race condition when the salt
 minion starts, and it could or could not lead to update orchestration
 failure.
 
 Fixes: bsc#1097478

buildservice-autocommit accepted request 617896 from

Containers Team (containersteam) almost 6 years ago (revision 293)

baserev update by copy to link target

Containers Team (containersteam) committed almost 6 years ago (revision 292)

new commit from concourse: Commit 45b8f7b by Maximilian Meister mmeister@suse.de
 explicitly pass unix_socket
 
 this affects only kubic for now where we use PyMySQL
 
 we cant use the MYSQL_UNIX_PORT workaround anymore as we could do with
 MySQLdb
 
 salt#mysql-unix-socket
 
 Signed-off-by: Maximilian Meister <mmeister@suse.de>

Containers Team (containersteam) committed almost 6 years ago (revision 291)

new commit from concourse: Commit de8bd66 by Maximilian Meister mmeister@suse.de
 override volume plugin dir (bsc#1084766)
 
 kubernetes 1.10 uses /usr/libexec by default which doesnt exist, and we want
 to stick with /usr/lib
 
 Signed-off-by: Maximilian Meister <mmeister@suse.de>

Containers Team (containersteam) committed almost 6 years ago (revision 290)

new commit from concourse: Commit 5804349 by Alvaro Saurin alvaro.saurin@gmail.com
 Move the early services setup even before updating the masters (we can do
 this by removing some unnecessary dependencies).
 
 bsc#1096992

Containers Team (containersteam) committed almost 6 years ago (revision 289)

new commit from concourse: Commit ba20582 by Alvaro Saurin alvaro.saurin@gmail.com
 Try to load the manifests once we have at least one updated master.
 
 bsc#1096992

Containers Team (containersteam) committed almost 6 years ago (revision 288)

new commit from concourse: Commit 180e545 by Alvaro Saurin alvaro.saurin@gmail.com
 Early setup some services on updates Removed "allowedFlexVolumes" in PSP (as
 it doesn't pass the API verification in 2.1)
 
 bsc#1096992

buildservice-autocommit accepted request 616508 from

Containers Team (containersteam) almost 6 years ago (revision 287)

baserev update by copy to link target

Containers Team (containersteam) committed almost 6 years ago (revision 286)

new commit from concourse: Commit a4480ed by Alvaro Saurin alvaro.saurin@gmail.com
 Do not set the `bootstrap_complete` flag in all the nodes: do it only in the
 nodes that had some role assigned. Remove the `bootstrap_in_progress` even if
 the orchestration fails. Fixed typo in target.
 
 bsc#1094078

Containers Team (containersteam) committed almost 6 years ago (revision 285)

new commit from concourse: Commit cf5b83b by Rafael Fernández López ereslibre@ereslibre.es
 Remove mine information when removing a node
 
 This will avoid to render stale information about critical components, like
 `etcd` endpoints in the `etcd` configuration.
 
 `etcd` is very sensitive to this kind of misleading (stale) information, if
 more endpoints are provided in `ETCD_INITIAL_CLUSTER` than the ones that
 actually exist in the cluster, a new instance of etcd will refuse to start.
 
 Fixes: bsc#1097001 Fixes: bsc#1097147

Containers Team (containersteam) committed almost 6 years ago (revision 284)

new commit from concourse: Commit 23ce1f2 by Rafael Fernández López ereslibre@ereslibre.es
 Force `etc-hosts` sls to be run before `etcd`
 
 Before the real update orchestration happens we are updating etcd
 certificates, so this machine isn't left isolated. However, in this process,
 the configuration for etcd might refer to the new machine names if this
 happens during the upgrade of 2.0 to 3.0. This might leave the etcd instances
 in a state in which they cannot resolve other etcd peer names (because their
 `/etc/hosts` file is outdated).
 
 In order to prevent this, force the `etc-hosts` sls to be run before we
 execute the `etcd` sls, so we are sure that `/etc/hosts` will contain both
 the old and the new names during the upgrade, and etcd will be able to refer
 to other peers using the new hostnames.
 
 Fixes: bsc#1096750

Containers Team (containersteam) committed almost 6 years ago (revision 283)

new commit from concourse: Commit ec6238c by Rafael Fernández López ereslibre@ereslibre.es
 Also stop `kubelet` on masters when performing an upgrade
 
 If some important change lands between Kubernetes updates, it might happen
 that since we don't disable the `kubelet` service on the master nodes, when
 the machine gets rebooted, `systemd` will try to start the
 `kubelet` service, failing in a burst mode.
 
 This will prevent our salt states from trying to start it again, because the
 service will be in a failed state. Stop the service and disable it on the
 masters too when we are performing an upgrade, this way we are sure that
 we'll try to start and enable it when we have performed the required changes
 for it to succeed.
 
 Fixes: bsc#1096768

buildservice-autocommit accepted request 614578 from

Containers Team (containersteam) almost 6 years ago (revision 282)

baserev update by copy to link target

Containers Team (containersteam) committed almost 6 years ago (revision 281)

new commit from concourse: Commit c77b0ee by Alvaro Saurin alvaro.saurin@gmail.com
 Use the cache whenever something bad happens when refreshing the Pillar from
 Velum.
 
 bsc#1093123

Containers Team (containersteam) committed almost 6 years ago (revision 280)

new commit from concourse: Commit 450cfdb by Alvaro Saurin alvaro.saurin@gmail.com
 Perform some checks before starting the node removal.
 
 feature#node_removal

buildservice-autocommit accepted request 614020 from

Containers Team (containersteam) almost 6 years ago (revision 279)

baserev update by copy to link target

Containers Team (containersteam) committed almost 6 years ago (revision 278)

new commit from concourse: Commit 33b39b3 by Alvaro Saurin alvaro.saurin@gmail.com
 Skip nodes that are being removed in the list of servers in haproxy.
 
 bsc#1095330
 
 Commit 8484c28 by Alvaro Saurin alvaro.saurin@gmail.com
 Fix the "targets" priorities for getting nodes for replacements. Minor: use
 the same pattern for targeting nodes in removals.sls
 as in kubernetes.sls. Do not use "unassigned" nodes when looking for
 replacements. Minor improvements
 
 bsc#1095336 bsc#1094078
 
 Commit b80c8f1 by Alvaro Saurin alvaro.saurin@gmail.com
 Minor cleanups and "beautifications"
 
 feature#cleanups

Displaying revisions 81 - 100 of 377

Places

Revisions of kubernetes-salt

Places