Skip to content

Commit

Permalink
Add more queryString support to Tabs
Browse files Browse the repository at this point in the history
Signed-off-by: Derek Nola <derek.nola@suse.com>
  • Loading branch information
dereknola committed Jul 11, 2024
1 parent d7c2198 commit f65671b
Show file tree
Hide file tree
Showing 6 changed files with 8 additions and 8 deletions.
2 changes: 1 addition & 1 deletion docs/cli/etcd-snapshot.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ When K3s is restored from backup, the old data directory will be moved to `${dat

To restore the cluster from backup:

<Tabs>
<Tabs queryString="etcdsnap">
<TabItem value="Single Server">

Run K3s with the `--cluster-reset` option, with the `--cluster-reset-restore-path` also given:
Expand Down
6 changes: 3 additions & 3 deletions docs/cli/secrets-encrypt.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ Available as of [v1.28.1+k3s1](https://github.com/k3s-io/k3s/releases/tag/v1.28.
For older releases, see [Encryption Key Rotation Classic](#encryption-key-rotation-classic)
:::

<Tabs groupId="se">
<Tabs groupId="se" queryString>
<TabItem value="Single-Server" default>
To rotate secrets encryption keys on a single-server cluster:

Expand Down Expand Up @@ -97,7 +97,7 @@ To rotate secrets encryption keys on HA setups:

### Encryption Key Rotation Classic

<Tabs groupId="se">
<Tabs groupId="se" queryString>
<TabItem value="Single-Server" default>

To rotate secrets encryption keys on a single-server cluster:
Expand Down Expand Up @@ -195,7 +195,7 @@ To rotate secrets encryption keys on HA setups:
</Tabs>

### Secrets Encryption Disable/Re-enable
<Tabs groupId="se">
<Tabs groupId="se" queryString>
<TabItem value="Single-Server" default>

After launching a server with `--secrets-encryption` flag, secrets encryption can be disabled.
Expand Down
2 changes: 1 addition & 1 deletion docs/datastore/cluster-loadbalancer.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ Three additional nodes exist with hostnames and IPs of:
* agent-3: `10.10.10.103`

## Setup Load Balancer
<Tabs>
<Tabs queryString="ext-load-balancer">
<TabItem value="HAProxy" default>

[HAProxy](http://www.haproxy.org/) is an open source option that provides a TCP load balancer. It also supports HA for the load balancer itself, ensuring redundancy at all levels. See [HAProxy Documentation](http://docs.haproxy.org/2.8/intro.html) for more info.
Expand Down
2 changes: 1 addition & 1 deletion docs/datastore/datastore.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ As a best practice we recommend setting these parameters as environment variable
### Datastore Endpoint Format and Functionality
As mentioned, the format of the value passed to the `datastore-endpoint` parameter is dependent upon the datastore backend. The following details this format and functionality for each supported external datastore.

<Tabs>
<Tabs queryString="ext-db">
<TabItem value="PostgreSQL">


Expand Down
2 changes: 1 addition & 1 deletion docs/installation/airgap.md
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ See the [SELinux](../advanced.md#selinux-support) section for more information.
You can install K3s on one or more servers as described below.
<Tabs>
<Tabs queryString="airgap-cluster">
<TabItem value="Single Server Configuration" default>
To install K3s on a single server, simply do the following on the server node:
Expand Down
2 changes: 1 addition & 1 deletion docs/networking/basic-network-options.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ We recommend that users migrate to the new backend as soon as possible. The migr

Start K3s with `--flannel-backend=none` and install your CNI of choice. Most CNI plugins come with their own network policy engine, so it is recommended to set `--disable-network-policy` as well to avoid conflicts. Some important information to take into consideration:

<Tabs>
<Tabs queryString="cni">
<TabItem value="Canal" default>

Visit the [Canal Docs](https://docs.tigera.io/calico/latest/getting-started/kubernetes/flannel/install-for-flannel#installing-calico-for-policy-and-flannel-aka-canal-for-networking) website. Follow the steps to install Canal. Modify the Canal YAML so that IP forwarding is allowed in the `container_settings` section, for example:
Expand Down

0 comments on commit f65671b

Please sign in to comment.