mirror of https://github.com/k3s-io/k3s
![]() Automatic merge from submit-queue move '(master)' to end of message for uniformity **What this PR does / why we need it**: This is a small polish operation on the kubernetes charm wrt juju status output. **Release note**: <!-- Steps to write your release note: 1. Use the release-note-* labels to set the release note state (if you have access) 2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. --> ```release-note NONE ``` This changes the status output from: ``` kubernetes/0 active idle 3 172.27.24.54 8088/tcp Kubernetes running. kubernetes/1 active idle 4 172.27.24.55 6443/tcp (master) Kubernetes services started ``` to this: ``` kubernetes/0 active idle 3 172.27.24.54 8088/tcp Kubernetes running. kubernetes/1 active idle 4 172.27.24.55 6443/tcp Kubernetes services started (master) ``` |
||
---|---|---|
.. | ||
addons | ||
aws | ||
azure | ||
azure-legacy | ||
centos | ||
gce | ||
gke | ||
images | ||
juju | ||
kubemark | ||
lib | ||
libvirt-coreos | ||
local | ||
mesos/docker | ||
openstack-heat | ||
ovirt | ||
photon-controller | ||
rackspace | ||
saltbase | ||
skeleton | ||
ubuntu | ||
vagrant | ||
vsphere | ||
OWNERS | ||
README.md | ||
common.sh | ||
get-kube-local.sh | ||
get-kube.sh | ||
kube-down.sh | ||
kube-push.sh | ||
kube-up.sh | ||
kube-util.sh | ||
kubectl.sh | ||
log-dump.sh | ||
options.md | ||
test-e2e.sh | ||
test-network.sh | ||
test-smoke.sh | ||
update-storage-objects.sh | ||
validate-cluster.sh |
README.md
Cluster Configuration
Deprecation Notice: This directory has entered maintainence mode and will not be accepting new providers. Please submit new automation deployments to kube-deploy. Deployments in this directory will continue to be maintained and supported at their current level of support.
The scripts and data in this directory automate creation and configuration of a Kubernetes cluster, including networking, DNS, nodes, and master components.
See the getting-started guides for examples of how to use the scripts.
cloudprovider/config-default.sh
contains a set of tweakable definitions/parameters for the cluster.
The heavy lifting of configuring the VMs is done by SaltStack.