github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/cluster/saltbase
History
Kubernetes Submit Queue 6ed3bce7f4 Merge pull request #43546 from calebamiles/wip-bump-cni-ref 
Automatic merge from submit-queue

Bump CNI consumers to v0.5.1

**What this PR does / why we need it**:
- vendored CNI plugins properly handle `DEL` on missing resources
- update CNI version refs

**Which issue this PR fixes**

fixes #43488

**Release note**:

`bumps CNI to version v0.5.1 where plugins properly handle DEL on non existent resources`
 		2017-03-23 14:13:05 -07:00
..
pillar update oscodenames supporting systemd 2016-10-18 09:37:40 -04:00
reactor Remove kube-up for vsphere 2016-12-22 20:15:37 +00:00
salt Merge pull request #43546 from calebamiles/wip-bump-cni-ref 2017-03-23 14:13:05 -07:00
BUILD Build release tarballs in bazel and add `make bazel-release` rule 2017-01-13 16:17:44 -08:00
README.md Implement Azure cloud provider scripts 2016-06-17 23:46:03 -07:00
install.sh Remove "All rights reserved" from all the headers. 2016-06-29 17:47:36 -07:00

README.md

SaltStack configuration

This is the root of the SaltStack configuration for Kubernetes. A high level overview for the Kubernetes SaltStack configuration can be found in the docs tree.

This SaltStack configuration currently applies to default configurations for Debian-on-GCE, Fedora-on-Vagrant, Ubuntu-on-AWS and Ubuntu-on-Azure. (That doesn't mean it can't be made to apply to an arbitrary configuration, but those are only the in-tree OS/IaaS combinations supported today.) As you peruse the configuration, these are shorthanded as gce, vagrant, aws, azure-legacy in grains.cloud; the documentation in this tree uses this same shorthand for convenience.

See more:

Analytics