rancher
/
rke1-docs
mirror of https://github.com/rancher/rke1-docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix broken links

This commit is contained in:
Billy Tat 2023-03-22 10:15:26 -07:00
parent a6dfbf3ce0
commit 3cf97079fa
3 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/config-options/cloud-providers/cloud-providers.md
View File

@ -5,9 +5,9 @@ title: Cloud Providers
RKE supports the ability to set your specific cloud provider for your Kubernetes cluster. There are specific cloud configurations for these cloud providers. RKE supports the ability to set your specific cloud provider for your Kubernetes cluster. There are specific cloud configurations for these cloud providers.
To enable a cloud provider its name as well as any required configuration options must be provided under the `cloud_provider` directive in the cluster YML. To enable a cloud provider its name as well as any required configuration options must be provided under the `cloud_provider` directive in the cluster YML.
* [AWS](config-options/cloud-providers/aws) * [AWS](./aws/aws.md)
* [Azure](config-options/cloud-providers/azure) * [Azure](./azure/azure.md)
* [OpenStack](config-options/cloud-providers/openstack) * [OpenStack](./openstack/openstack.md)
* [vSphere](config-options/cloud-providers/vsphere) * [vSphere](./vsphere/vsphere.md)
Outside of this list, RKE also supports the ability to handle any [custom cloud provider](config-options/cloud-providers/custom). Outside of this list, RKE also supports the ability to handle any [custom cloud provider](./custom/custom.md).

4
docs/installation/certs/certs.md
View File

@ -6,7 +6,7 @@ _Available as of v0.2.0_
By default, Kubernetes clusters require certificates and RKE auto-generates the certificates for all the Kubernetes services. RKE can also use custom certificates for these Kubernetes services. By default, Kubernetes clusters require certificates and RKE auto-generates the certificates for all the Kubernetes services. RKE can also use custom certificates for these Kubernetes services.
When [deploying Kubernetes with RKE](/installation/#deploying-kubernetes-with-rke), there are two additional options that can be used with `rke up` so that RKE uses custom certificates. When [deploying Kubernetes with RKE](../installation.md#deploying-kubernetes-with-rke), there are two additional options that can be used with `rke up` so that RKE uses custom certificates.
| Option | Description | | Option | Description |
| --- | --- | | --- | --- |
@ -47,7 +47,7 @@ The following certificates must exist in the certificate directory.
If you want to create and sign the certificates by a real Certificate Authority (CA), you can use RKE to generate a set of Certificate Signing Requests (CSRs) and keys. Using the `rke cert generate-csr` command, you can generate the CSRs and keys. If you want to create and sign the certificates by a real Certificate Authority (CA), you can use RKE to generate a set of Certificate Signing Requests (CSRs) and keys. Using the `rke cert generate-csr` command, you can generate the CSRs and keys.
1. Set up your `cluster.yml` with the [node information](/config-options/nodes). 1. Set up your `cluster.yml` with the [node information](../../config-options/nodes/nodes.md).
2. Run `rke cert generate-csr` to generate certificates for the node(s) in the `cluster.yml`. By default, the CSRs and keys will be saved in `./cluster_certs`. To have them saved in a different directory, use `--cert-dir` to define what directory to have them saved in. 2. Run `rke cert generate-csr` to generate certificates for the node(s) in the `cluster.yml`. By default, the CSRs and keys will be saved in `./cluster_certs`. To have them saved in a different directory, use `--cert-dir` to define what directory to have them saved in.

16
docs/installation/installation.md
View File

@ -92,20 +92,20 @@ For information on which Docker versions were tested with your version of RKE, r
::: :::
Review the [OS requirements](/os) and configure each node appropriately. Review the [OS requirements](../os/os.md) and configure each node appropriately.
## Creating the Cluster Configuration File ## Creating the Cluster Configuration File
RKE uses a cluster configuration file, referred to as `cluster.yml` to determine what nodes will be in the cluster and how to deploy Kubernetes. There are [many configuration options](/config-options) that can be set in the `cluster.yml`. In our example, we will be assuming the minimum of one [node](/config-options/nodes) for your Kubernetes cluster. RKE uses a cluster configuration file, referred to as `cluster.yml` to determine what nodes will be in the cluster and how to deploy Kubernetes. There are [many configuration options](../config-options/config-options.md) that can be set in the `cluster.yml`. In our example, we will be assuming the minimum of one [node](../config-options/nodes/nodes.md) for your Kubernetes cluster.
There are two easy ways to create a `cluster.yml`: There are two easy ways to create a `cluster.yml`:
- Using our [minimal `cluster.yml`](/example-yamls/#minimal-cluster-yml-example) and updating it based on the node that you will be using. - Using our [minimal `cluster.yml`](../example-yamls/example-yamls.md#minimal-cluster-yml-example) and updating it based on the node that you will be using.
- Using `rke config` to query for all the information needed. - Using `rke config` to query for all the information needed.
### Using `rke config` ### Using `rke config`
Run `rke config` to create a new `cluster.yml` in the current directory. This command will prompt you for all the information needed to build a cluster. See [cluster configuration options](/config-options) for details on the various options. Run `rke config` to create a new `cluster.yml` in the current directory. This command will prompt you for all the information needed to build a cluster. See [cluster configuration options](../config-options/config-options.md) for details on the various options.
``` ```
rke config --name cluster.yml rke config --name cluster.yml
@ -135,7 +135,7 @@ To create an HA cluster, specify more than one host with role `controlplane`.
_Available as of v0.2.0_ _Available as of v0.2.0_
By default, Kubernetes clusters require certificates and RKE auto-generates the certificates for all cluster components. You can also use [custom certificates](installation/certs). After the Kubernetes cluster is deployed, you can [manage these auto-generated certificates](/cert-mgmt#certificate-rotation). By default, Kubernetes clusters require certificates and RKE auto-generates the certificates for all cluster components. You can also use [custom certificates](installation/certs). After the Kubernetes cluster is deployed, you can [manage these auto-generated certificates](../cert-mgmt/cert-mgmt.md#certificate-rotation).
## Deploying Kubernetes with RKE ## Deploying Kubernetes with RKE
@ -190,9 +190,9 @@ Before v0.2.0, RKE saved the Kubernetes cluster state as a secret. When updating
## Interacting with your Kubernetes cluster ## Interacting with your Kubernetes cluster
After your cluster is up and running, you can start using the [generated kubeconfig file](/kubeconfig) to start interacting with your Kubernetes cluster using `kubectl`. After your cluster is up and running, you can start using the [generated kubeconfig file](../kubeconfig/kubeconfig.md) to start interacting with your Kubernetes cluster using `kubectl`.
After installation, there are several maintenance items that might arise: After installation, there are several maintenance items that might arise:
* [Certificate Management](/cert-mgmt) * [Certificate Management](../cert-mgmt/cert-mgmt.md)
* [Adding and Removing Nodes in the cluster](/managing-clusters) * [Adding and Removing Nodes in the cluster](../managing-clusters/managing-clusters.md)