From 7cdb4a764776c16bf047f3f82ff020f24d48378d Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Tue, 10 Jul 2018 10:41:00 -0700 Subject: [PATCH] addressed Jason and Sebs comments --- .../rancher/v2.x/en/tasks/workloads/add-a-sidecar/_index.md | 6 +++++- .../rancher/v2.x/en/tasks/workloads/add-ingress/_index.md | 2 ++ 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/tasks/workloads/add-a-sidecar/_index.md b/content/rancher/v2.x/en/tasks/workloads/add-a-sidecar/_index.md index c64c38d622d..a044732e71f 100644 --- a/content/rancher/v2.x/en/tasks/workloads/add-a-sidecar/_index.md +++ b/content/rancher/v2.x/en/tasks/workloads/add-a-sidecar/_index.md @@ -1,6 +1,6 @@ --- title: Adding a Sidecar -weight: +weight: 200 --- 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. @@ -29,3 +29,7 @@ A _sidecar_ is a container that extends or enhances the main container in a pod. 1. Click **Launch**. **Result:** The sidecar is deployed according to your parameters. Following its deployment, you can view the sidecar by selecting **Ellipsis icon (...) > Edit** for the main deployment. + +## Related Links + +- [The Distributed System ToolKit: Patterns for Composite Containers](https://kubernetes.io/blog/2015/06/the-distributed-system-toolkit-patterns/) diff --git a/content/rancher/v2.x/en/tasks/workloads/add-ingress/_index.md b/content/rancher/v2.x/en/tasks/workloads/add-ingress/_index.md index 110f63b54b0..e8c9435a6b9 100644 --- a/content/rancher/v2.x/en/tasks/workloads/add-ingress/_index.md +++ b/content/rancher/v2.x/en/tasks/workloads/add-ingress/_index.md @@ -51,6 +51,8 @@ Ingress can be added for workloads to provide load balancing, SSL termination an - **Use as the default backend** Use this option to set an ingress rule for handling requests that don't match any other ingress rules. For example, use this option to route requests that can't be found to a `404` page. + + >**Note:** If you deployed Rancher using RKE, a default backend is already configured. However, you can use this option to customize your backend. 1. Add a **Target Backend**. Click either **Service** or **Workload** to add the target.