mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-25 04:28:15 +00:00
undrafting, adding weight
This commit is contained in:
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Adding a DNS Record
|
||||
weight:
|
||||
draft: true
|
||||
weight: 75
|
||||
---
|
||||
For every workload created, a complementing Service Discovery entry is created. This Service Discovery entry enables DNS resolution for the workload's pods using the following naming convention:
|
||||
`<workload>.<namespace>.svc.cluster.local`.
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Adding a Sidecar
|
||||
weight:
|
||||
draft: true
|
||||
---
|
||||
A _sidecar_ is a container that extends or enhances the main container in a pod. The main container and the sidecar share a pod, and therefore share the same network space and storage. You can add sidecars to existing workloads by using the **Add a Sidecar** option.
|
||||
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Adding Ingress
|
||||
weight:
|
||||
draft: true
|
||||
weight: 50
|
||||
---
|
||||
|
||||
Ingress can be added for workloads to provide load balancing, SSL termination and host/path based routing.
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Adding a Persistent Volume Claim
|
||||
weight:
|
||||
draft: true
|
||||
weight: 100
|
||||
---
|
||||
|
||||
_Persistent Volume Claims_ (or PVCs) are objects that request storage resources from your cluster. They're similar to a voucher that your deployment can redeem for storage access. When you create a deployment, you should usually attach a PVC so that your application can lay claim to persistent storage. This claim lets your deployment application store its data in an external location, so that if one of the application's containers fails, it can be replaced with a new container and continue accessing its data stored externally, as though an outage never occured.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Deploying Workloads
|
||||
weight:
|
||||
weight: 25
|
||||
---
|
||||
|
||||
Deploy a workload to run an application in one or more containers.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Rolling Back Workloads
|
||||
weight:
|
||||
weight: 150
|
||||
---
|
||||
|
||||
Sometimes there is a need to rollback to the previous version of the application, either for debugging purposes or because an upgrade did not go as planned.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Upgrading Workloads
|
||||
weight:
|
||||
weight: 125
|
||||
---
|
||||
When a new version of an application image is released on Docker Hub, you can upgrade any workloads running a previous version of the application to the new one.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user