mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-09-06 11:42:14 +00:00
Merge pull request #8296 from jlowdermilk/gen-analytics
Add ga-beacon analytics to gendocs scripts
This commit is contained in:
Victor Marmol
@@ -57,3 +57,6 @@ Definition of columns:
|
||||
- **Community**: Actively supported by community contributions. May not work with more recent releases of kubernetes.
|
||||
- **Inactive**: No active maintainer. Not recommended for first-time K8s users, and may be deleted soon.
|
||||
- **Notes** is relevant information such as version k8s used.
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -212,3 +212,6 @@ Visit the public IP address in your browser to view the running pod.
|
||||
```bash
|
||||
kubectl delete pods hello
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -79,3 +79,6 @@ cluster/kube-down.sh
|
||||
## Further reading
|
||||
Please see the [Kubernetes docs](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/docs) for more details on administering
|
||||
and using a Kubernetes cluster.
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -19,3 +19,6 @@ mv kubectl /usr/local/bin/
|
||||
```bash
|
||||
ssh -f -nNT -L 8080:127.0.0.1:8080 core@<master-public-ip>
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -126,3 +126,6 @@ Look in `api/examples/` for more examples
|
||||
```
|
||||
cluster/kube-down.sh
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -21,3 +21,6 @@ make release
|
||||
```
|
||||
|
||||
For more details on the release process see the [`build/` directory](../../build)
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -162,3 +162,6 @@ centos-minion <none> Ready
|
||||
**The cluster should be running! Launch a test pod.**
|
||||
|
||||
You should have a functional cluster, check out [101](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/examples/walkthrough/README.md)!
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -88,3 +88,6 @@ SSH to it using the key that was created and using the _core_ user and you can l
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -10,3 +10,6 @@ There are multiple guides on running Kubernetes with [CoreOS](http://coreos.com)
|
||||
* [Yet another multi-node cluster using cloud-config and Vagrant](https://github.com/AntonioMeireles/kubernetes-vagrant-coreos-cluster/blob/master/README.md) (similar to the one above but with an increased, more *aggressive* focus on features and flexibility)
|
||||
* [Multi-node cluster with Vagrant and fleet units using a small OS X App](https://github.com/rimusz/coreos-osx-gui-kubernetes-cluster/blob/master/README.md)
|
||||
* [Resizable multi-node cluster on Azure with Weave](coreos/azure/README.md)
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -185,3 +185,6 @@ If you don't wish care about the Azure bill, you can tear down the cluster. It's
|
||||
> Note: make sure to use the _latest state file_, as after resizing there is a new one.
|
||||
|
||||
By the way, with the scripts shown, you can deploy multiple clusters, if you like :)
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -674,3 +674,6 @@ List Kubernetes
|
||||
Kill all pods:
|
||||
|
||||
for i in `kubectl get pods | awk '{print $1}'`; do kubectl stop pod $i; done
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -132,3 +132,6 @@ hdiutil makehybrid -iso -joliet -joliet-volume-name "config-2" -joliet -o node.i
|
||||
#### Provision worker nodes
|
||||
|
||||
Boot one or more the [vmware image](https://coreos.com/docs/running-coreos/platforms/vmware) using `node.iso` as a config drive.
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -56,3 +56,6 @@ hdiutil makehybrid -iso -joliet -joliet-volume-name "config-2" -joliet -o standa
|
||||
```
|
||||
|
||||
Boot the [vmware image](https://coreos.com/docs/running-coreos/platforms/vmware) using the `standalone.iso` as a config drive.
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -43,3 +43,6 @@ See [here](docker-multinode/worker.md) for detailed instructions.
|
||||
Once your cluster has been created you can [test it out](docker-multinode/testing.md)
|
||||
|
||||
For more complete applications, please look in the [examples directory](../../examples)
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -141,3 +141,6 @@ If all else fails, ask questions on IRC at #google-containers.
|
||||
|
||||
### Next steps
|
||||
Move on to [adding one or more workers](worker.md)
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -55,4 +55,6 @@ And list the pods
|
||||
kubectl get pods
|
||||
```
|
||||
|
||||
You should see pods landing on the newly added machine.
|
||||
You should see pods landing on the newly added machine.
|
||||
|
||||
[]()
|
||||
|
||||
@@ -130,3 +130,6 @@ Make the API call to add the node, you should do this on the master node that yo
|
||||
### Next steps
|
||||
|
||||
Move on to [testing your cluster](testing.md) or [add another node](#adding-a-kubernetes-worker-node-via-docker)
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -79,3 +79,6 @@ Many of these containers run under the management of the ```kubelet``` binary, w
|
||||
the cluster, you need to first kill the kubelet container, and then any other containers.
|
||||
|
||||
You may use ```docker ps -a | awk '{print $1}' | xargs docker kill```, note this removes _all_ containers running under Docker, so use with caution.
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -229,3 +229,6 @@ curl http://localhost
|
||||
```
|
||||
|
||||
That's it !
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -189,3 +189,6 @@ $ kubectl delete -f node.json
|
||||
**The cluster should be running! Launch a test pod.**
|
||||
|
||||
You should have a functional cluster, check out [101](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/examples/walkthrough/README.md)!
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -157,3 +157,6 @@ PING 18.16.90.4 (18.16.90.4) 56(84) bytes of data.
|
||||
```
|
||||
|
||||
* Now kubernetes multi-node cluster is set up with overlay networking set up by flannel.
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -104,3 +104,6 @@ field values:
|
||||
|
||||
* Source Ranges: `10.0.0.0/8`
|
||||
* Allowed Protocols and Port: `tcp:1-65535;udp:1-65535;icmp`
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -208,3 +208,6 @@ Azure | TBD
|
||||
Digital Ocean | TBD
|
||||
MAAS (bare metal) | TBD
|
||||
GCE | TBD
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -252,3 +252,6 @@ usermod -a -G libvirtd $USER
|
||||
#### error: Out of memory initializing network (virsh net-create...)
|
||||
|
||||
Ensure libvirtd has been restarted since ebtables was installed.
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -110,3 +110,6 @@ One or more of the kubernetes daemons might've crashed. Tail the logs of each in
|
||||
|
||||
#### The pods fail to connect to the services by host names
|
||||
The local-up-cluster.sh script doesn't start a DNS service. Similar situation can be found [here](https://github.com/GoogleCloudPlatform/kubernetes/issues/6667). You can start a manually. Related documents can be found [here](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/cluster/addons/dns#how-do-i-configure-it)
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -26,3 +26,6 @@ Elasticsearch service (more information to follow shortly in the contrib directo
|
||||
To enable logging of Docker contains in a cluster using Google Compute
|
||||
Platform set the config flags ``ENABLE_NODE_LOGGING`` to ``true`` and
|
||||
``LOGGING_DESTINATION`` to ``gcp``.
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -302,3 +302,6 @@ Now, you can visit the guestbook in your browser!
|
||||
[10]: mesos/k8s-guestbook.png
|
||||
[11]: http://mesos.apache.org/
|
||||
[12]: https://google.mesosphere.com/clusters
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -42,3 +42,6 @@ The `ovirt-cloud.conf` file then must be specified in kube-controller-manager:
|
||||
This short screencast demonstrates how the oVirt Cloud Provider can be used to dynamically add VMs to your kubernetes cluster.
|
||||
|
||||
[](http://www.youtube.com/watch?v=JyyST4ZKne8)
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -45,3 +45,6 @@ The current cluster design is inspired by:
|
||||
- eth0 - Public Interface used for servers/containers to reach the internet
|
||||
- eth1 - ServiceNet - Intra-cluster communication (k8s, etcd, etc) communicate via this interface. The `cloud-config` files use the special CoreOS identifier `$private_ipv4` to configure the services.
|
||||
- eth2 - Cloud Network - Used for k8s pods to communicate with one another. The proxy service will pass traffic via this interface.
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -170,3 +170,6 @@ Please try:
|
||||
`$ KUBERNETES_PROVIDER=ubuntu ./kube-up.sh` again to start again.
|
||||
|
||||
4. You can also customize your own settings in `/etc/default/{component_name}` after configured success.
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -300,3 +300,6 @@ export KUBERNETES_MINION_MEMORY=2048
|
||||
|
||||
#### I ran vagrant suspend and nothing works!
|
||||
```vagrant suspend``` seems to mess up the network. It's not supported at this time.
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
@@ -78,3 +78,6 @@ The output of `kube-up.sh` displays the IP addresses of the VMs it deploys. You
|
||||
can log into any VM as the `kube` user to poke around and figure out what is
|
||||
going on (find yourself authorized with your SSH key, or use the password
|
||||
`kube` otherwise).
|
||||
|
||||
|
||||
[]()
|
||||
|
||||
Reference in New Issue
Block a user