fix nine 404 page in doc
I wrote a crawl to fetch all invalid herf in website: https://kubernetes.io/docs/ Fix nine of them first. I will fix others if there are.
This commit is contained in:
@@ -1014,8 +1014,7 @@ Pod.
|
||||
|
||||
Download the example above, and save it to a file named `webp.yaml`
|
||||
|
||||
This manifest is identical to the one you
|
||||
[downloaded above](creating-a-statefulset) except that the `.spec.podManagementPolicy`
|
||||
This manifest is identical to the one you downloaded above except that the `.spec.podManagementPolicy`
|
||||
of the `web` StatefulSet is set to `Parallel`.
|
||||
|
||||
In one terminal, watch the Pods in the StatefulSet.
|
||||
|
||||
@@ -48,7 +48,7 @@ computer.
|
||||
|
||||
## Cassandra Docker
|
||||
|
||||
The pods use the [```gcr.io/google-samples/cassandra:v12```](image/Dockerfile)
|
||||
The pods use the [```gcr.io/google-samples/cassandra:v12```](https://github.com/kubernetes/examples/blob/master/cassandra/image/Dockerfile)
|
||||
image from Google's [container registry](https://cloud.google.com/container-registry/docs/).
|
||||
The docker is based on `debian:jessie` and includes OpenJDK 8. This image
|
||||
includes a standard Cassandra installation from the Apache Debian repo. Through the use of environment variables you are able to change values that are inserted into the `cassandra.yaml`.
|
||||
@@ -835,7 +835,7 @@ via a replication control or a daemonset, you will need to use the custom seed p
|
||||
In Cassandra, a `SeedProvider` bootstraps the gossip protocol that Cassandra uses to find other
|
||||
Cassandra nodes. Seed addresses are hosts deemed as contact points. Cassandra
|
||||
instances use the seed list to find each other and learn the topology of the
|
||||
ring. The [`KubernetesSeedProvider`](java/src/main/java/io/k8s/cassandra/KubernetesSeedProvider.java)
|
||||
ring. The [`KubernetesSeedProvider`](https://github.com/kubernetes/kubernetes/blob/master/examples/storage/cassandra/java/src/main/java/io/k8s/cassandra/KubernetesSeedProvider.java)
|
||||
discovers Cassandra seeds IP addresses via the Kubernetes API, those Cassandra
|
||||
instances are defined within the Cassandra Service.
|
||||
|
||||
@@ -843,7 +843,7 @@ Refer to the custom seed provider [README](https://git.k8s.io/examples/cassandra
|
||||
`KubernetesSeedProvider` configurations. For this example you should not need
|
||||
to customize the Seed Provider configurations.
|
||||
|
||||
See the [image](image/) directory of this example for specifics on
|
||||
See the [image](https://github.com/kubernetes/examples/tree/master/cassandra/image) directory of this example for specifics on
|
||||
how the container docker image was built and what it contains.
|
||||
|
||||
You may also note that we are setting some Cassandra parameters (`MAX_HEAP_SIZE`
|
||||
|
||||
@@ -726,7 +726,7 @@ container to rotate and ship your logs.
|
||||
The best practices with respect to allowing an application to run as a privileged
|
||||
user inside of a container are a matter of debate. If your organization requires
|
||||
that applications be run as a non-privileged user you can use a
|
||||
[SecurityContext](/docs/concepts/policy/security-context/) to control the user that
|
||||
[SecurityContext](/docs/tasks/configure-pod-container/security-context/) to control the user that
|
||||
the entry point runs as.
|
||||
|
||||
The `zk` StatefulSet's Pod `template` contains a SecurityContext.
|
||||
|
||||
Reference in New Issue
Block a user