updating relative links with absolute links

2026-09-25 04:28:15 +00:00 · 2018-07-12 13:00:54 -07:00
parent 3f140c72e4
commit 5c7366cb7c
14 changed files with 109 additions and 13 deletions
@@ -156,3 +156,13 @@ Last thing you will need to do, is assign the appropriate permissions to your Ap
 Custom Azure Network Security Group needed to allow Azure Load Balancers to work. If you provision hosts using Rancher Machine Azure driver, you will need to edit them manually to assign them to this Network Security Group. You should already assign custom hosts to this Network Security Group during provisioning.

 Only hosts expected to be Load Balancer backends need to be in this group.
+
+## Related Links
+
+### External Links
+
+- [Cloud Providers](https://kubernetes.io/docs/concepts/cluster-administration/cloud-providers/)
+
+### Tutorials
+
+- [Creating a Cluster]({{< baseurl >}}/rancher/v2.x/en/tasks/clusters/creating-a-cluster/)
@@ -22,13 +22,7 @@ However, Rancher also provides local authentication.

 In most cases, you should use an external authentication service over local, as external authentication allows user management from a central location. However, you may want a few local authentication users for managing Rancher under rare circumstances, such as if Active Directory is down.

-<<<<<<< HEAD
-For more information on how to configure external authentication or local authentication, see [Authentication](../../../tasks/global-configuration/authentication/). 
-
-### External Authentication Configuration and Principal Users
-=======
 ## External Authentication Configuration and Principal Users
->>>>>>> adding links

 Configuration of external authentication requires:

@@ -59,10 +53,7 @@ Configuration of external authentication affects how principal users are managed

 6. The external principal and the local principal share the same access rights.

-<<<<<<< HEAD
-=======

 ## Related Links

 - [Configuring Authentication]({{< baseurl >}}/rancher/v2.x/en/tasks/global-configuration/authentication)
->>>>>>> adding links
@@ -8,3 +8,6 @@ Out-of-the-box, Rancher provides support for creating clusters using many popula
 For more information on creating node drivers, see [https://github.com/rancher/ui-driver-skel](https://github.com/rancher/ui-driver-skel).


+## Related Links
+
+- [Configuring Node Drivers]({{< baseurl >}}/rancher/v2.x/en/tasks/global-configuration/node-drivers)
@@ -7,3 +7,6 @@ You can create new clusters within Rancher using _node templates_. A node templa

 After you add a node template to Rancher, its stored by the system so that you can use it when creating another cluster later. Node templates are bound to your login. After you add a template, you can remove them from your user profile.

+## Related Links
+
+- [Creating a Cluster]({{< baseurl >}}/rancher/v2.x/en/tasks/clusters/creating-a-cluster)
@@ -17,3 +17,13 @@ Read more about Pod Security Policies in the [Kubernetes Documentation](https://

 >**Best Practice:**
 >Set Pod Security at the cluster level.
+
+## Related Links
+
+### External Links
+
+- [Pod Security Policies](https://kubernetes.io/docs/concepts/policy/pod-security-policy/)
+
+### Tutorials
+
+- [Creating Pod Security Policies]({{< baseurl >}}/rancher/v2.x/en/tasks/clusters/adding-a-pod-security-policy)
@@ -195,3 +195,8 @@ Roles can be locked by the following users:
 - Any user assigned the `Administrator` global permission.
 - Any user assigned the `Custom Users` permission, along with the `Manage Roles` role.

+## Related Links
+
+- [Adding Project Members]({{< baseurl >}}/rancher/v2.x/en/tasks/projects/add-project-members)
+- [Adding Project Members]({{< baseurl >}}/rancher/v2.x/en/tasks/clusters/adding-managing-cluster-members)
+- [Roles]({{< baseurl >}}/rancher/v2.x/en/tasks/global-configuration/roles)
@@ -50,3 +50,22 @@ Other layer-7 load balancers, such as the Google Load Balancer or Nginx Ingress
 2.	Ask Rancher to generate an xip.io host name for your ingress rule. Rancher will take one of your exposed IPs, say a.b.c.d, and generate a host name <ingressname>.<namespace>.a.b.c.d.xip.io.

 The benefit of using xip.io is that you obtain a working entrypoint URL immediately after you create the ingress rule. Setting up your own domain name, on the other hand, requires you to configure DNS servers and wait for DNS to propagate.
+
+## Related Links
+
+### External Load Balancers
+
+#### External Links
+
+- [Create an External Load Balancer](https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/)
+
+#### Tutorials
+
+- [High Availability Installation with External Load Balancer (HTTPS/Layer 7)]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install-external-lb)
+- [High Availability Installation with External Load Balancer (TCP/Layer 4)]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install)
+- [Single Node Installation with External Load Balancer]({{< baseurl >}}/rancher/v2.x/en/installation/single-node-install-external-lb)
+
+### Ingress Controller
+
+- [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/#what-is-ingress)
+<!--  [Adding Ingress]({{< baseurl >}}/rancher/v2.x/en/tasks/workloads/add-ingress) -->
@@ -3,3 +3,8 @@ title: Logging
 weight: 2325
 draft: true
 ---
+
+
+## Related Links
+
+[Configuring Logging]({{< baseurl >}}/rancher/v2.x/en/tasks/logging/)
@@ -21,3 +21,7 @@ Rancher extends Kubernetes to allow the application of [Pod Security Policies](h
 Kubernetes resources belong to specific namespaces. Rancher 2.0 relies on namespaces to isolate resources among users and apps. When the user deploys an app from the catalog, for example, he can choose to deploy that app into its own namespace, so that resource names in one app will not conflict with resource names in another. Namespaces must be globally unique. It is often difficult for users to pick unique namespace names. Rancher therefore encourages the pattern where users work with projects, and the system generates unique namespace names automatically.

 For more information, see the [Kubernetes Namespaces Documentation](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/).
+
+## Related Links
+
+- [Project Tutorials]({{< baseurl >}}/rancher/v2.x/en/tasks/projects)
@@ -10,7 +10,7 @@ Within the context of a Rancher project or namespace, _resources_ are files and
 - [Secrets](#secrets)
 - [Registries](#registries)

-Rancher extends the application of the Kubernetes namespace resources listed above to [projects](../projects), which are Rancher-specific constructs. In the hierarchy of Rancher objects, projects contain namespaces. Therefore, any resources available within a project are available for all namespaces within that project.
+Rancher extends the application of the Kubernetes namespace resources listed above to [projects]({{< baseurl >}}/rancher/v2.x/en/projects), which are Rancher-specific constructs. In the hierarchy of Rancher objects, projects contain namespaces. Therefore, any resources available within a project are available for all namespaces within that project.

 Within Kubernetes, certificates, registries, and secrets are all considered [secrets](https://kubernetes.io/docs/concepts/configuration/secret/). Therefore, within a single project or namespace, these resources must have unique names to avoid conflicts. Although secrets are primarily used to carry sensitive information, they have other uses as well. Read on below.

@@ -37,4 +37,11 @@ When configuring a workload, you'll be able to choose which secrets to include.

 Registries are secrets containing credentials used to authenticate with [private registries](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/). Deployments use these secrets to authenticate with a private registry and then pull a Docker image hosted on it.

->**Note:** Currently, credentials are pulled automatically only if the workload is created in the Rancher UI and not kubectl.
+>**Note:** Currently, credentials are pulled automatically only if the workload is created in the Rancher UI and not kubectl.
+
+## Related Links
+
+- [Adding SSL Certificates]({{< baseurl >}}/rancher/v2.x/en/tasks/projects/add-ssl-certificates)
+- [Adding ConfigMaps]({{< baseurl >}}/rancher/v2.x/en/tasks/projects/add-configmaps)
+- [Adding Secrets]({{< baseurl >}}/rancher/v2.x/en/tasks/projects/add-a-secret)
+- [Adding Registries]({{< baseurl >}}/rancher/v2.x/en/tasks/projects/add-registries)
@@ -3,3 +3,14 @@ title: Service Discovery
 weight: 2200
 draft: true
 ---
+
+## Related Links
+
+### Tutorials
+
+- [Adding a DNS Record]({{< baseurl >}}/rancher/v2.x/en/tasks/workloads/add-a-dns-record)
+
+### External Links
+
+- [Services](https://kubernetes.io/docs/concepts/services-networking/service/)
+- [Adding entries to Pod /etc/hosts with HostAliases](https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/)
@@ -45,4 +45,15 @@ In addition to customizing each provisioner's options for the storage class, you

 Finally, you can define custom `MountOptions` for the persistent volume created.

-`parameters` are specific to each cloud storage provisioner. For full information about the storage classes provisioner parameters, refer to the official [Kubernetes documentation](https://kubernetes.io/docs/concepts/storage/storage-classes/#parameters).
+`parameters` are specific to each cloud storage provisioner. For full information about the storage classes provisioner parameters, refer to the official [Kubernetes documentation](https://kubernetes.io/docs/concepts/storage/storage-classes/#parameters).
+
+## Related Links
+
+### External Docs
+
+- [Storage](https://kubernetes.io/docs/concepts/storage/)
+
+### Tutorials
+
+- [Adding Storage]({{< baseurl >}}/rancher/v2.x/en/tasks/clusters/adding-storage/provisioning-storage)
+- [Adding Persistent Volume Claims]({{< baseurl >}}/rancher/v2.x/en/tasks/workloads/add-persistent-volume-claim)
@@ -61,3 +61,13 @@ There are several types of services available in Rancher. The descriptions below
 - **LoadBalancer**

    >Exposes the service externally using a cloud provider’s load balancer. `NodePort` and `ClusterIP` services, to which the external load balancer will route, are automatically created.
+
+## Related Links
+
+### External Links
+
+- [Services](https://kubernetes.io/docs/concepts/services-networking/service/)
+
+### Tutorials
+
+- [Workloads]({{< baseurl >}}/rancher/v2.x/en/tasks/workloads/)
@@ -42,4 +42,11 @@ However, you also have the option of creating additional Service Discovery recor
 **Result:** A new DNS record is created.

 - You can view the record by from the project's **Service Discovery** tab.
- When you visit the new DNS name for the new record that you created (`<recordname>.<namespace>.svc.cluster.local`), it resolves the chosen namespace.
+- When you visit the new DNS name for the new record that you created (`<recordname>.<namespace>.svc.cluster.local`), it resolves the chosen namespace.
+### Tutorials
+
+- [Service Discovery]({{< baseurl >}}/rancher/v2.x/en/concepts/service-discovery)
+
+### External Links
+
+- [Adding entries to Pod /etc/hosts with HostAliases](https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/)