Merge branch 'master' into master

This commit is contained in:
Ankur Shukla
2016-09-23 12:51:06 -07:00
committed by GitHub
8 changed files with 47 additions and 9 deletions
+22
View File
@@ -0,0 +1,22 @@
<!-- Thanks for filing an issue! Before submitting, please fill in the following information. -->
<!--Required Information-->
**This is a...**
<!-- choose one by changing [ ] to [x] -->
- [ ] Feature Request
- [ ] Bug Report
**Problem:**
**Proposed Solution:**
**Page to Update:**
http://kubernetes.io/...
<!--Optional Information (remove the comment tags around information you would like to include)-->
<!--Kubernetes Version:-->
<!--Additional Information:-->
+3 -3
View File
@@ -11,7 +11,7 @@ change the name of the fork to be:
YOUR_GITHUB_USERNAME.github.io YOUR_GITHUB_USERNAME.github.io
Then make your changes. Then make your changes.
When you visit [http://YOUR_GITHUB_USERNAME.github.io](http://YOUR_GITHUB_USERNAME.github.io) you should see a special-to-you version of the site that contains the changes you just made. When you visit [http://YOUR_GITHUB_USERNAME.github.io](http://YOUR_GITHUB_USERNAME.github.io) you should see a special-to-you version of the site that contains the changes you just made.
@@ -21,11 +21,11 @@ Don't like installing stuff? Download and run a local staging server with a sing
git clone https://github.com/kubernetes/kubernetes.github.io.git git clone https://github.com/kubernetes/kubernetes.github.io.git
cd kubernetes.github.io cd kubernetes.github.io
docker run -ti --rm -v "$PWD":/k8sdocs -p 4000:4000 johndmulhausen/k8sdocs docker run -ti --rm -v "$PWD":/k8sdocs -p 4000:4000 gcr.io/google-samples/k8sdocs:1.0
Then visit [http://localhost:4000](http://localhost:4000) to see our site. Any changes you make on your local machine will be automatically staged. Then visit [http://localhost:4000](http://localhost:4000) to see our site. Any changes you make on your local machine will be automatically staged.
If you're interested you can view [the Dockerfile for this image](https://gist.github.com/johndmulhausen/f8f0ab8d82d2c755af3a4709729e1859). If you're interested you can view [the Dockerfile for this image](https://github.com/kubernetes/kubernetes.github.io/blob/master/staging-container/Dockerfile).
## Staging the site locally (from scratch setup) ## Staging the site locally (from scratch setup)
+1 -1
View File
@@ -41,7 +41,7 @@ Kubernetes installations. This required some minor
(backward-compatible) changes to the way (backward-compatible) changes to the way
the Kubernetes cluster DNS server processes DNS queries, to facilitate the Kubernetes cluster DNS server processes DNS queries, to facilitate
the lookup of federated services (which span multiple Kubernetes clusters). the lookup of federated services (which span multiple Kubernetes clusters).
See the [Cluster Federation Administrators' Guide](/docs/admin/federation/index.md) for more See the [Cluster Federation Administrators' Guide](/docs/admin/federation) for more
details on Cluster Federation and multi-site support. details on Cluster Federation and multi-site support.
## References ## References
+3
View File
@@ -0,0 +1,3 @@
# *Stop. This guide has been superseded by [Minikube](../minikube/). The link below is present only for historical purposes*
The document has been moved to [here](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/local-cluster/docker.md)
+3 -3
View File
@@ -37,14 +37,14 @@ git fetch upstream
git reset --hard upstream/docsv2 git reset --hard upstream/docsv2
``` ```
### Step 3: Make sure you can serve rendered docs ### Step 3: Make sure you can serve rendered docs
One option is to simply rename your fork's repo on GitHub.com to `yourusername.github.io`, which will auto-stage your commits at that URL. One option is to simply rename your fork's repo on GitHub.com to `yourusername.github.io`, which will auto-stage your commits at that URL.
Or, just use Docker! Run this from within your local `kubernetes.github.io` directory and you should be good: Or, just use Docker! Run this from within your local `kubernetes.github.io` directory and you should be good:
```shell ```shell
docker run -ti --rm -v "$PWD":/k8sdocs -p 4000:4000 johndmulhausen/k8sdocs docker run -ti --rm -v "$PWD":/k8sdocs -p 4000:4000 gcr.io/google-samples/k8sdocs:1.0
``` ```
The site will then be viewable at [http://localhost:4000/](http://localhost:4000/). The site will then be viewable at [http://localhost:4000/](http://localhost:4000/).
@@ -246,4 +246,4 @@ You probably shouldn't be using this, but we also have templates which consume Y
### Adding page to navigation ### Adding page to navigation
Once your page is saved, somewhere in the `/docs/` directory, add a reference to the `reference.yml` file under `/_data/` so that it will appear in the left-hand navigation of the site. This is also where you add a title to the page. Once your page is saved, somewhere in the `/docs/` directory, add a reference to the `reference.yml` file under `/_data/` so that it will appear in the left-hand navigation of the site. This is also where you add a title to the page.
+1 -1
View File
@@ -50,7 +50,7 @@ kubectl version
### SEE ALSO ### SEE ALSO
* [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager * [kubectl](../kubectl.md) - kubectl controls the Kubernetes cluster manager
###### Auto generated by spf13/cobra on 12-Aug-2016 ###### Auto generated by spf13/cobra on 12-Aug-2016
+1 -1
View File
@@ -398,7 +398,7 @@ start until all the pod's volumes are mounted.
Create a secret containing some ssh keys: Create a secret containing some ssh keys:
```shell ```shell
$ kubectl create secret generic my-secret --from-file=ssh-privatekey=/path/to/.ssh/id_rsa --from-file=ssh-publickey=/path/to/.ssh/id_rsa.pub $ kubectl create secret generic ssh-key-secret --from-file=ssh-privatekey=/path/to/.ssh/id_rsa --from-file=ssh-publickey=/path/to/.ssh/id_rsa.pub
``` ```
**Security Note:** think carefully before sending your own ssh keys: other users of the cluster may have access to the secret. Use a service account which you want to have accessible to all the users with whom you share the kubernetes cluster, and can revoke if they are compromised. **Security Note:** think carefully before sending your own ssh keys: other users of the cluster may have access to the secret. Use a service account which you want to have accessible to all the users with whom you share the kubernetes cluster, and can revoke if they are compromised.
+13
View File
@@ -0,0 +1,13 @@
FROM starefossen/ruby-node:2-4
RUN gem install github-pages
VOLUME /k8sdocs
EXPOSE 4000
WORKDIR /k8sdocs
CMD bundle && jekyll clean && jekyll serve -H 0.0.0.0 -P 4000
# For instructions, see http://kubernetes.io/editdocs/