mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-26 13:08:11 +00:00
Fix K8s resources and pipelines links
This commit is contained in:
Catherine Luse
@@ -13,7 +13,7 @@ Restoring a snapshot of the Rancher Server cluster will revert Rancher to the ve
|
||||
|
||||
>**Note:** Managed clusters are authoritative for their state. This means restoring the rancher server will not revert workload deployments or changes made on managed clusters after the snapshot was taken.
|
||||
|
||||
- [Rolling back Rancher installed with Docker]({{<baseurl>}}/rancher/v2.x/en/upgrades/rollbacks/single-node-rollbacks/)
|
||||
- [Rolling back Rancher installed with Docker]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/single-node-docker/single-node-rollbacks)
|
||||
- [Rolling back Rancher installed on a Kubernetes cluster]({{<baseurl>}}/rancher/v2.x/en/upgrades/rollbacks/ha-server-rollbacks/)
|
||||
|
||||
### Special Scenarios regarding Rollbacks
|
||||
|
||||
+2
-2
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Legacy
|
||||
title: Kubernetes Resources
|
||||
weight: 19
|
||||
aliases:
|
||||
- /rancher/v2.x/en/concepts/
|
||||
@@ -7,7 +7,7 @@ aliases:
|
||||
- /rancher/v2.x/en/concepts/resources/
|
||||
---
|
||||
|
||||
When your project is set up, [project members]({{<baseurl>}}/rancher/v2.x/en/admin-settings/rbac/cluster-project-roles/#project-roles) can start managing their applications and all the components that comprise it.
|
||||
> The **Cluster Explorer** is a new feature in Rancher v2.5 that allows you to view and manipulate all of the custom resources and CRDs in a Kubernetes cluster from the Rancher UI. This section will be updated to reflect the way that Kubernetes resources are handled in Rancher v2.5.
|
||||
|
||||
## Workloads
|
||||
|
||||
-1
@@ -6,7 +6,6 @@ aliases:
|
||||
- /rancher/v2.x/en/k8s-in-rancher/configmaps
|
||||
---
|
||||
|
||||
|
||||
While most types of Kubernetes secrets store sensitive information, [ConfigMaps](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/) store general configuration information, such as a group of config files. Because ConfigMaps don't store sensitive information, they can be updated automatically, and therefore don't require their containers to be restarted following update (unlike most secret types, which require manual updates and a container restart to take effect).
|
||||
|
||||
ConfigMaps accept key value pairs in common string formats, like config files or JSON blobs. After you upload a config map, any workload can reference it as either an environment variable or a volume mount.
|
||||
@@ -1,13 +0,0 @@
|
||||
---
|
||||
title: Kubernetes Resources
|
||||
weight: 10
|
||||
aliases:
|
||||
- /rancher/v2.x/en/k8s-in-rancher
|
||||
---
|
||||
|
||||
|
||||
### About the Cluster Explorer
|
||||
|
||||
_Available as of v2.5_
|
||||
|
||||
The cluster explorer is a new feature in Rancher v2.5 that allows you to view and manipulate all of the custom resources and CRDs in a Kubernetes cluster from the Rancher UI.
|
||||
+2
-2
@@ -2,8 +2,8 @@
|
||||
title: Cluster Metrics
|
||||
weight: 3
|
||||
aliases:
|
||||
- rancher/v2.x/en/project-admin/tools/monitoring/cluster-metrics
|
||||
- rancher/v2.x/en/cluster-admin/tools/monitoring/cluster-metrics
|
||||
- /rancher/v2.x/en/project-admin/tools/monitoring/cluster-metrics
|
||||
- /rancher/v2.x/en/cluster-admin/tools/monitoring/cluster-metrics
|
||||
---
|
||||
|
||||
_Available as of v2.2.0_
|
||||
|
||||
-2
@@ -3,8 +3,6 @@ title: Prometheus Custom Metrics Adapter
|
||||
weight: 5
|
||||
aliases:
|
||||
- rancher/v2.x/en/project-admin/tools/monitoring/custom-metrics
|
||||
- rancher/v2.x/en/cluster-admin/tools/monitoring/cluster-metrics
|
||||
- /rancher/v2.x/en/cluster-admin/tools/monitoring/custom-metrics
|
||||
---
|
||||
|
||||
After you've enabled [cluster level monitoring]({{< baseurl >}}/rancher/v2.x/en/monitoring-alerting/legacy/monitoring/cluster-monitoring/#enabling-cluster-monitoring), You can view the metrics data from Rancher. You can also deploy the Prometheus custom metrics adapter then you can use the HPA with metrics stored in cluster monitoring.
|
||||
|
||||
@@ -606,7 +606,7 @@ To configure compute resources for pipeline-step containers:
|
||||
|
||||
You can configure compute resources for pipeline-step containers in the `.rancher-pipeline.yml` file.
|
||||
|
||||
In a [step type]({{<baseurl>}}/rancher/v2.x/en/k8s-in-rancher/pipelines/#step-types), you will provide the following information:
|
||||
In a step, you will provide the following information:
|
||||
|
||||
* **CPU Reservation (`CpuRequest`)**: CPU request for the container of a pipeline step.
|
||||
* **CPU Limit (`CpuLimit`)**: CPU limit for the container of a pipeline step.
|
||||
|
||||
@@ -74,4 +74,4 @@ After enabling an example repository, run the pipeline to see how it works.
|
||||
|
||||
### What's Next?
|
||||
|
||||
For detailed information about setting up your own pipeline for your repository, [configure a version control provider]({{<baseurl>}}/rancher/v2.x/en/project-admin/pipelines), [enable a repository](#configure-repositories) and finally [configure your pipeline]({{<baseurl>}}/rancher/v2.x/en/k8s-in-rancher/pipelines/#pipeline-configuration).
|
||||
For detailed information about setting up your own pipeline for your repository, [configure a version control provider]({{<baseurl>}}/rancher/v2.x/en/project-admin/pipelines), [enable a repository](#configure-repositories) and finally [configure your pipeline]({{<baseurl>}}/rancher/v2.x/en/k8s-in-rancher/pipelines/#pipeline-configuration-reference).
|
||||
|
||||
Reference in New Issue
Block a user