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
@@ -117,6 +117,7 @@ juju run-action new-etcd/0 restore
|
||||
{{% /capture %}}
|
||||
|
||||
{{% capture discussion %}}
|
||||
|
||||
## Known Limitations
|
||||
|
||||
#### Loss of PKI warning
|
||||
@@ -126,10 +127,9 @@ all TLS pki will be lost. No PKI migration occurs outside
|
||||
of the units requesting and registering the certificates.
|
||||
|
||||
{{< caution >}}
|
||||
**Caution:** Mismanaging this configuration will result in locking yourself
|
||||
out of the cluster, and can potentially break existing deployments in very
|
||||
strange ways relating to x509 validation of certificates, which affects both
|
||||
servers and clients.
|
||||
Mismanaging this configuration will result in locking yourself out of the cluster,
|
||||
and can potentially break existing deployments in very strange ways relating to x509
|
||||
validation of certificates, which affects both servers and clients.
|
||||
{{< /caution >}}
|
||||
|
||||
#### Restoring from snapshot on a scaled cluster
|
||||
|
||||
@@ -12,7 +12,7 @@ This page shows you how to properly decommission a cluster.
|
||||
This page assumes you have a working Juju deployed cluster.
|
||||
|
||||
{{< warning >}}
|
||||
**Warning:** By the time you've reached this step you should have backed up your workloads and pertinent data; this section is for the complete destruction of a cluster.
|
||||
By the time you've reached this step you should have backed up your workloads and pertinent data; this section is for the complete destruction of a cluster.
|
||||
{{< /warning >}}
|
||||
|
||||
{{% /capture %}}
|
||||
|
||||
@@ -14,7 +14,7 @@ This page shows how the various network portions of a cluster work and how to co
|
||||
This page assumes you have a working Juju deployed cluster.
|
||||
|
||||
{{< note >}}
|
||||
**Note:** Note that if you deploy a cluster via conjure-up or the CDK bundles, manually deploying CNI plugins is unnecessary.
|
||||
Note that if you deploy a cluster via conjure-up or the CDK bundles, manually deploying CNI plugins is unnecessary.
|
||||
{{< /note >}}
|
||||
{{% /capture %}}
|
||||
|
||||
|
||||
@@ -43,8 +43,11 @@ loop loop
|
||||
rootfs rootfs
|
||||
tmpfs tmpfs
|
||||
```
|
||||
> **Note**: This listing is for the Amazon Web Services public cloud.
|
||||
> Different clouds may have different pool names.
|
||||
|
||||
{{< note >}}
|
||||
This listing is for the Amazon Web Services public cloud. Different clouds may have
|
||||
different pool names.
|
||||
{{< /note >}}
|
||||
|
||||
Add a storage pool to the ceph-osd charm by NAME,SIZE,COUNT:
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ This page will outline how to manage and execute a Kubernetes upgrade.
|
||||
This page assumes you have a working deployed cluster.
|
||||
|
||||
{{< warning >}}
|
||||
**Warning:** You should always back up all your data before attempting an upgrade.
|
||||
You should always back up all your data before attempting an upgrade.
|
||||
Don't forget to include the workload inside your cluster!
|
||||
Refer to the [backup documentation](/docs/getting-started-guides/ubuntu/backups).
|
||||
{{< /warning >}}
|
||||
@@ -83,7 +83,7 @@ First you need to upgrade the masters:
|
||||
juju upgrade-charm kubernetes-master
|
||||
|
||||
{{< note >}}
|
||||
**Note:** Always upgrade the masters before the workers.
|
||||
Always upgrade the masters before the workers.
|
||||
{{< /note >}}
|
||||
|
||||
Once the latest charm is deployed, the channel for Kubernetes can be selected by issuing the following:
|
||||
|
||||
@@ -90,7 +90,7 @@ a deployed cluster. The following example will skip the `Flaky`, `Slow`, and
|
||||
juju run-action kubernetes-e2e/0 test skip='\[(Flaky|Slow|Feature:.*)\]'
|
||||
|
||||
{{< note >}}
|
||||
**Note:** The escaping of the regex due to how bash handles brackets.
|
||||
The escaping of the regex due to how bash handles brackets.
|
||||
{{< /note >}}
|
||||
|
||||
To see the different types of tests the Kubernetes end-to-end charm has access
|
||||
@@ -112,7 +112,7 @@ command, as well as a flat file on disk on the `kubernetes-e2e` unit that
|
||||
executed the test.
|
||||
|
||||
{{< note >}}
|
||||
**Note:** The results will only be available once the action has
|
||||
The results will only be available once the action has
|
||||
completed the test run. End-to-end testing can be quite time consuming, often
|
||||
taking more than 1 hour, depending on configuration.
|
||||
{{< /note >}}
|
||||
|
||||
Reference in New Issue
Block a user