Add ga-beacon analytics to gendocs scripts
hack/run-gendocs.sh puts ga-beacon analytics link into all md files, hack/verify-gendocs.sh verifies presence of link.
This commit is contained in:
Jeff Lowdermilk
parent
293afd4a4f
commit
29edafa519
|
|
@ -360,3 +360,6 @@ public class KubernetesSeedProvider implements SeedProvider {
|
|||
}
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -232,3 +232,6 @@ rabbitmq-controller-pjzb3 10.246.2.16 rabbitmq library/rabb
|
|||
|
||||
Now you know on which host Flower is running (in this case, 10.245.1.4), you can open your browser and enter the address (e.g. `http://10.245.1.4:5555`. If you click on the tab called "Tasks", you should see an ever-growing list of tasks called "celery_conf.add" which the run\_tasks.py script is dispatching.
|
||||
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -135,3 +135,6 @@ $ cluster/kubectl.sh log dns-frontend
|
|||
#### Note about default namespace
|
||||
|
||||
If you prefer not using namespace, then all your services can be addressed using `default` namespace, e.g. `http://dns-backend.default.kubernetes.local:8000`, or shorthand version `http://dns-backend:8000`
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -31,3 +31,6 @@ $ kubectl log dapi-test-pod | grep POD_
|
|||
2015-04-30T20:22:18.568024817Z POD_NAME=dapi-test-pod
|
||||
2015-04-30T20:22:18.568087688Z POD_NAMESPACE=default
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -316,4 +316,6 @@ $ curl 104.197.12.157:9200/_nodes?pretty=true | grep name
|
|||
"vm_name" : "OpenJDK 64-Bit Server VM",
|
||||
"name" : "eth0",
|
||||
|
||||
```
|
||||
```
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -126,3 +126,6 @@ Error: <*>lookup elasticsearch-logging: no such host
|
|||
|
||||
</body></html>
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -80,3 +80,6 @@ $ mount | grep kube_vol
|
|||
```
|
||||
|
||||
You may also run `docker ps` on the host to see the actual container.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -209,3 +209,6 @@ To turn down a Kubernetes cluster:
|
|||
```shell
|
||||
$ cluster/kube-down.sh
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -32,3 +32,6 @@ Accepts an optional tag (defaults to "latest")
|
|||
###### Clean up
|
||||
|
||||
./script/clean.sh
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -550,3 +550,6 @@ $> docker logs 26af6bd5ac12
|
|||
==> default: <b>Fatal error</b>: Uncaught exception 'Predis\ServerException' with message 'MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk. Commands that may modify the data set are disabled. Please check Redis logs for details about the error.' in /vendor/predis/predis/lib/Predis/Client.php:282"
|
||||
```
|
||||
The fix is to setup SE Linux properly (don't just turn it off). Remember that you can also rebuild this entire app from scratch, using the dockerfiles, and modify while redeploying. Reach out on the mailing list if you need help doing so!
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -329,3 +329,6 @@ public class HazelcastDiscoveryController implements CommandLineRunner {
|
|||
}
|
||||
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -55,3 +55,6 @@ Run *docker inspect* and I found the Containers mounted the host directory into
|
|||
# docker inspect --format '{{index .Volumes "/mnt/iscsipd"}}' cc051196e7af
|
||||
/var/lib/kubelet/pods/75e0af2b-f8e8-11e4-9ae7-42010af01964/volumes/kubernetes.io~iscsi/iscsipd-rw
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -109,3 +109,6 @@ Thus we plan to add another tier of queueing, which empties the REDIS transactio
|
|||
For questions on running this app, you can ask on the google containers group (freenode ~ google-containers@googlegroups.com or #google-containers on IRC)
|
||||
|
||||
For questions about bigpetstore, and how the data is generated, ask on the apache bigtop mailing list.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -13,3 +13,6 @@ and checkout the last exact version (will be updated periodically).
|
|||
then, cd to bigtop-bigpetstore/bigpetstore-transaction-queue, and run the docker file, i.e.
|
||||
|
||||
`Docker build -t -i jayunit100/bps-transaction-queue`.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -247,3 +247,6 @@ At this point, it should be clear that the resources users create in one namespa
|
|||
|
||||
As the policy support in Kubernetes evolves, we will extend this scenario to show how you can provide different
|
||||
authorization rules for each namespace.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -74,3 +74,6 @@ You would also see the killing and creating events at the bottom of the *kubectl
|
|||
Thu, 14 May 2015 15:23:25 -0700 Thu, 14 May 2015 15:23:25 -0700 1 {kubelet kubernetes-minion-0uzf} spec.containers{liveness} started Started with docker id b254a9810073f9ee9075bb38ac29a4b063647176ad9eabd9184078ca98a60062
|
||||
...
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -241,3 +241,6 @@ Access the Elasticsearch service at URL `https://130.211.122.180/api/v1beta3/pro
|
|||
}
|
||||
```
|
||||
Visiting the URL `https://130.211.122.180/api/v1beta3/proxy/namespaces/default/services/kibana-logging` should show the Kibana viewer for the logging information stored in the Elasticsearch service.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -163,3 +163,6 @@ container section:
|
|||
}
|
||||
],
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -7,3 +7,6 @@ To build and push the base meteor-kubernetes image:
|
|||
|
||||
docker build -t chees/meteor-kubernetes .
|
||||
docker push chees/meteor-kubernetes
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -307,3 +307,6 @@ $ <kubernetes>/cluster/kube-down.sh
|
|||
|
||||
|
||||
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -35,3 +35,6 @@ Now the pod serves `index.html` from the NFS server:
|
|||
|
||||
$ curl http://<the container IP address>/
|
||||
Hello World!
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -8,3 +8,6 @@ Serves NFS4 exports, defined on command line. At least one export must be define
|
|||
Usage::
|
||||
|
||||
docker run -d --name nfs --privileged jsafrane/nfsexporter /path/to/share /path/to/share2 ...
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -4,4 +4,6 @@ This container exports /mnt/data with index.html in it via NFSv4. Based on
|
|||
../exporter.
|
||||
|
||||
Available in dockerhub as
|
||||
[jsafrane/nfs-data](https://registry.hub.docker.com/u/jsafrane/nfs-data/).
|
||||
[jsafrane/nfs-data](https://registry.hub.docker.com/u/jsafrane/nfs-data/).
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -58,3 +58,6 @@ When you then run `kubectl create -f pod.yaml`, the pod will get scheduled on th
|
|||
### Conclusion
|
||||
|
||||
While this example only covered one node, you can attach labels to as many nodes as you want. Then when you schedule a pod with a nodeSelector, it can be scheduled on any of the nodes that satisfy that nodeSelector. Be careful that it will match at least one node, however, because if it doesn't the pod won't be scheduled at all.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -153,3 +153,6 @@ $ docker run --privileged --entrypoint="/usr/bin/bash" -it -e="OPENSHIFTCONFIG=/
|
|||
$ osc config use-context public-default
|
||||
$ osc --help
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -110,3 +110,6 @@ Hopefully this simple guide is enough to get you started with PersistentVolumes.
|
|||
```#google-containers``` on IRC and ask!
|
||||
|
||||
Enjoy!
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -216,3 +216,6 @@ To turn down a Kubernetes cluster:
|
|||
```shell
|
||||
$ cluster/kube-down.sh
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -113,3 +113,6 @@ kubectl delete pods redis-master
|
|||
```
|
||||
|
||||
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -130,3 +130,6 @@ since the ui is not stateless when playing with Web Admin UI will cause `Connect
|
|||
the generated pods which is using `nodeSelector` to force k8s to schedule containers to my designate nodes, for I need to access persistent data on my host dirs. Note that one needs to label the node before 'nodeSelector' can work, see this [tutorial](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/examples/node-selection)
|
||||
|
||||
* see [antmanler/rethinkdb-k8s](https://github.com/antmanler/rethinkdb-k8s) for detail
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -44,3 +44,6 @@ volume:
|
|||
$ kubectl log secret-test-pod
|
||||
2015-04-29T21:17:24.712206409Z content of file "/etc/secret-volume/data-1": value-1
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -43,3 +43,6 @@ This should print the service that has been created, and map an external IP addr
|
|||
### Next: Configuration files
|
||||
Most people will eventually want to use declarative configuration files for creating/modifying their applications. A [simplified introduction](simple-yaml.md)
|
||||
is given in a different document.
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -87,3 +87,6 @@ To delete the replication controller (and the pods it created):
|
|||
```bash
|
||||
kubectl delete rc nginx
|
||||
```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -171,3 +171,6 @@ SparkContext available as sc.
|
|||
Make sure the Master Pod is running (use: ```kubectl get pods```).
|
||||
|
||||
```kubectl create -f spark-worker-controller.json```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -168,3 +168,6 @@ Make sure the ZooKeeper Pod is running (use: ```kubectl get pods```).
|
|||
Make sure the Nimbus Pod is running.
|
||||
|
||||
```kubectl create -f storm-worker-controller.json```
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -114,3 +114,6 @@ Note that the images included here are public domain.
|
|||
|
||||
* [kitten](http://commons.wikimedia.org/wiki/File:Kitten-stare.jpg)
|
||||
* [nautilus](http://commons.wikimedia.org/wiki/File:Nautilus_pompilius.jpg)
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -110,3 +110,6 @@ Finally, we have also introduced an environment variable to the ```git-monitor``
|
|||
### What's next?
|
||||
Continue on to [Kubernetes 201](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/examples/walkthrough/k8s201.md) or
|
||||
for a complete application see the [guestbook example](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/examples/guestbook/README.md)
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
|
|
@ -149,3 +149,6 @@ spec:
|
|||
|
||||
### What's next?
|
||||
For a complete application see the [guestbook example](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/examples/guestbook).
|
||||
|
||||
|
||||
[]()
|
||||
|
|
|
|||
Loading…
Reference in New Issue