Add admonition type to shortcode (#9482)
* Change existing admon blocks * Fix includes issue
This commit is contained in:
committed by
k8s-ci-robot
parent
e839031292
commit
d65e1790ff
@@ -22,9 +22,9 @@ with upgrading your clusters, for example. We encourage you to try either approa
|
||||
and provide feedback.
|
||||
|
||||
{{< caution >}}
|
||||
**Caution**: This page does not address running your cluster on a cloud provider.
|
||||
In a cloud environment, neither approach documented here works with Service objects
|
||||
of type LoadBalancer, or with dynamic PersistentVolumes.
|
||||
This page does not address running your cluster on a cloud provider. In a cloud
|
||||
environment, neither approach documented here works with Service objects of type
|
||||
LoadBalancer, or with dynamic PersistentVolumes.
|
||||
{{< /caution >}}
|
||||
|
||||
{{% /capture %}}
|
||||
@@ -49,9 +49,8 @@ For the external etcd cluster only, you also need:
|
||||
- Three additional machines for etcd members
|
||||
|
||||
{{< note >}}
|
||||
**Note**: The following examples run Calico as the Pod networking provider. If
|
||||
you run another networking provider, make sure to replace any default values as
|
||||
needed.
|
||||
The following examples run Calico as the Pod networking provider. If you run another
|
||||
networking provider, make sure to replace any default values as needed.
|
||||
{{< /note >}}
|
||||
|
||||
{{% /capture %}}
|
||||
@@ -61,8 +60,7 @@ needed.
|
||||
## First steps for both methods
|
||||
|
||||
{{< note >}}
|
||||
**Note**: All commands in this guide on any control plane or etcd node should be
|
||||
run as root.
|
||||
All commands in this guide on any control plane or etcd node should be run as root.
|
||||
{{< /note >}}
|
||||
|
||||
- Find your pod CIDR. For details, see [the CNI network
|
||||
@@ -102,9 +100,8 @@ run as root.
|
||||
### Create load balancer for kube-apiserver
|
||||
|
||||
{{< note >}}
|
||||
**Note**: There are many configurations for load balancers. The following
|
||||
example is only one option. Your cluster requirements may need a
|
||||
different configuration.
|
||||
There are many configurations for load balancers. The following example is only one
|
||||
option. Your cluster requirements may need a different configuration.
|
||||
{{< /note >}}
|
||||
|
||||
1. Create a kube-apiserver load balancer with a name that resolves to DNS.
|
||||
@@ -140,7 +137,7 @@ different configuration.
|
||||
### Bootstrap the first stacked control plane node
|
||||
|
||||
{{< note >}}
|
||||
**Note**: Optionally replace `stable` with a different version of Kubernetes, for example `v1.12.0`.
|
||||
Optionally replace `stable` with a different version of Kubernetes, for example `v1.12.0`.
|
||||
{{< /note >}}
|
||||
|
||||
1. Create a `kubeadm-config.yaml` template file:
|
||||
@@ -217,7 +214,7 @@ done
|
||||
```
|
||||
|
||||
{{< note >}}
|
||||
**Note**: Remember that your config may differ from this example.
|
||||
Remember that your config may differ from this example.
|
||||
{{< /note >}}
|
||||
|
||||
### Add the second stacked control plane node
|
||||
@@ -439,7 +436,7 @@ done
|
||||
1. Create a `kubeadm-config.yaml`:
|
||||
|
||||
{{< note >}}
|
||||
**Note**: Optionally replace `stable` with a different version of Kubernetes, for example `v1.11.3`.
|
||||
Optionally replace `stable` with a different version of Kubernetes, for example `v1.11.3`.
|
||||
{{< /note >}}
|
||||
|
||||
apiVersion: kubeadm.k8s.io/v1alpha3
|
||||
|
||||
Reference in New Issue
Block a user