diff --git a/content/rancher/v2.x/en/v1.6-migration/discover-services/_index.md b/content/rancher/v2.x/en/v1.6-migration/discover-services/_index.md
index 038f90a65ba..90112383200 100644
--- a/content/rancher/v2.x/en/v1.6-migration/discover-services/_index.md
+++ b/content/rancher/v2.x/en/v1.6-migration/discover-services/_index.md
@@ -7,6 +7,10 @@ Service discovery is one of the core functionalities of any container-based envi
This document will also show you how to link the workloads and services that you migrated into Rancher v2.x. When you parsed your services from v1.6 using migration-tools CLI, it output two files for each service: one deployment manifest and one service manifest. You'll have to link these two files together before the deployment works correctly in v2.x.
+Resolve the output.txt Link Directive
+
+
+
## In This Document
@@ -58,6 +62,11 @@ When you migrate v1.6 services to v2.x, Rancher does not automatically create a
In the image below, the `web-deployment.yml` and `web-service.yml` files [created after parsing]({{< baseurl >}}/rancher/v2.x/en/v1.6-migration/run-migration-tool/#migration-example-file-output) our [migration example services]({{< baseurl >}}/rancher/v2.x/en/v1.6-migration/#migration-example-files) are linked together.
+Linked Workload and Kubernetes Service
+
+
+
+
### Service Name Alias Creation
Just as you can create an alias for Rancher v1.6 services, you can do the same for Rancher v2.x workloads. Similarly, you can also create DNS records pointing to services running externally, using either their hostname or IP address. These DNS records are Kubernetes service objects.
@@ -66,6 +75,9 @@ Using the v2.x UI, use the context menu to navigate to the `Project` view. Then
Click **Add Record** to create new DNS records. Then view the various options supported to link to external services or to create aliases for another workload, DNS record, or set of pods.
+Add Service Discovery Record
+
+
The following table indicates which alias options are implemented natively by Kubernetes and which options are implemented by Rancher leveraging Kubernetes.
Option | Kubernetes-implemented? | Rancher-implemented?
diff --git a/content/rancher/v2.x/en/v1.6-migration/get-started/_index.md b/content/rancher/v2.x/en/v1.6-migration/get-started/_index.md
index f5a1b6147d9..2f6a6237e85 100644
--- a/content/rancher/v2.x/en/v1.6-migration/get-started/_index.md
+++ b/content/rancher/v2.x/en/v1.6-migration/get-started/_index.md
@@ -40,6 +40,10 @@ After provisioning your node(s), install Rancher:
After your Rancher v2.x Server is installed, we recommend configuring external authentication (like Active Directory or GitHub) so that users can log into Rancher using their single sign-on. For a full list of supported authentication providers and instructions on how to configure them, see [Authentication]({{< baseurl >}}/rancher/v2.x/en/admin-settings/authentication).
+Rancher v2.x Authentication
+
+
+
### Local Users
Although we recommend using an external authentication provider, Rancher v1.6 and v2.x both offer support for users local to Rancher. However, these users cannot be migrated from Rancher v1.6 to v2.x. If you used local users in Rancher v1.6 and want to continue this practice in v2.x, you'll need to [manually recreate these user accounts]({{< baseurl >}}/rancher/v2.x/en/admin-settings/authentication/) and assign them access rights.
diff --git a/content/rancher/v2.x/en/v1.6-migration/load-balancing/_index.md b/content/rancher/v2.x/en/v1.6-migration/load-balancing/_index.md
index 645766f6a63..4a20100eb50 100644
--- a/content/rancher/v2.x/en/v1.6-migration/load-balancing/_index.md
+++ b/content/rancher/v2.x/en/v1.6-migration/load-balancing/_index.md
@@ -9,6 +9,10 @@ As outlined in [its documentation]({{< baseurl >}}/rancher/v1.6/en/cattle/adding
If you encounter the `output.txt` text below after parsing your v1.6 Compose files to Kubernetes manifests, you'll have to resolve it by manually creating a load balancer in v2.x.
+output.txt Load Balancer Directive
+
+
+
## In This Document
@@ -49,8 +53,16 @@ In Rancher v1.6 you could deploy a scalable load balancer service within your st
+Rancher v1.6 Load Balancing Architecture
+
+
+
The Rancher v2.x Ingress Controller is a DaemonSet, it is globally deployed on all schedulable nodes to serve your entire Kubernetes Cluster. Therefore, when you program the Ingress rules, you must use a unique hostname and path to point to your workloads, as the load balancer node IP addresses and ports 80 and 443 are common access points for all workloads.
+Rancher v2.x Load Balancing Architecture
+
+
+
## Ingress Caveats
Although Rancher v2.x supports HTTP and HTTPS hostname and path-based load balancing, you must use unique host names and paths when configuring your workloads. This limitation derives from:
@@ -67,8 +79,14 @@ You can launch a new load balancer to replace your load balancer from v1.6. Usin
>**Prerequisite:** Before deploying Ingress, you must have a workload deployed that's running a scale of two or more pods.
>
+
+
For balancing between these two pods, you must create a Kubernetes Ingress rule. To create this rule, navigate to your cluster and project, and click **Resources > Workloads > Load Balancing.** (In versions prior to v2.3.0, click **Workloads > Load Balancing.**) Then click **Add Ingress**. This GIF below depicts how to add Ingress to one of your projects.
+Browsing to Load Balancer Tab and Adding Ingress
+
+
+
Similar to a service/port rules in Rancher v1.6, here you can specify rules targeting your workload's container port. The sections below demonstrate how to create Ingress rules.
### Configuring Host- and Path-Based Routing
@@ -77,8 +95,16 @@ Using Rancher v2.x, you can add Ingress rules that are based on host names or a
For example, let's say you have multiple workloads deployed to a single namespace. You can add an Ingress to route traffic to these two workloads using the same hostname but different paths, as depicted in the image below. URL requests to `foo.com/name.html` will direct users to the `web` workload, and URL requests to `foo.com/login` will direct users to the `chat` workload.
+Ingress: Path-Based Routing Configuration
+
+
+
Rancher v2.x also places a convenient link to the workloads on the Ingress record. If you configure an external DNS to program the DNS records, this hostname can be mapped to the Kubernetes Ingress address.
+Workload Links
+
+
+
The Ingress address is the IP address in your cluster that the Ingress Controller allocates for your workload. You can reach your workload by browsing to this IP address. Use `kubectl` command below to see the Ingress address assigned by the controller:
```
@@ -92,6 +118,10 @@ Rancher v2.x Ingress functionality supports the HTTPS protocol, but if you want
- We recommend [uploading a certificate]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/certificates/) from a known certificate authority (you'll have to do this before configuring Ingress). Then, while configuring your load balancer, use the **Choose a certificate** option and select the uploaded certificate that you want to use.
- If you have configured [NGINX default certificate]({{< baseurl >}}/rke/latest/en/config-options/add-ons/ingress-controllers/#configuring-an-nginx-default-certificate), you can select **Use default ingress controller certificate**.
+Load Balancer Configuration: SSL/TLS Certificate Section
+
+
+
### TCP Load Balancing Options
#### Layer-4 Load Balancer
@@ -100,6 +130,10 @@ For the TCP protocol, Rancher v2.x supports configuring a Layer 4 load balancer
For example, if we create a deployment named `myapp` and specify a Layer 4 load balancer in the **Port Mapping** section, Rancher will automatically add an entry to the **Load Balancer** tab named `myapp-loadbalancer`.
+Workload Deployment: Layer 4 Load Balancer Creation
+
+
+
Once configuration of the load balancer succeeds, the Rancher UI provides a link to your workload's public endpoint.
#### NGINX Ingress Controller TCP Support by ConfigMaps
@@ -110,6 +144,8 @@ However, there is a workaround to use NGINX's TCP balancing by creating a Kubern
To configure NGINX to expose your services via TCP, you can add the ConfigMap `tcp-services` that should exist in the `ingress-nginx` namespace. This namespace also contains the NGINX Ingress Controller pods.
+
+
The key in the ConfigMap entry should be the TCP port that you want to expose for public access: `:`. As shown above, two workloads are listed in the `Default` namespace. For example, the first entry in the ConfigMap above instructs NGINX to expose the `myapp` workload (the one in the `default` namespace that's listening on private port 80) over external port `6790`. Adding these entries to the ConfigMap automatically updates the NGINX pods to configure these workloads for TCP balancing. The workloads exposed should be available at `:`. If they are not accessible, you might have to expose the TCP port explicitly using a NodePort service.
## Rancher v2.x Load Balancing Limitations
diff --git a/content/rancher/v2.x/en/v1.6-migration/monitor-apps/_index.md b/content/rancher/v2.x/en/v1.6-migration/monitor-apps/_index.md
index ad16e2cac2c..d018c49e4e4 100644
--- a/content/rancher/v2.x/en/v1.6-migration/monitor-apps/_index.md
+++ b/content/rancher/v2.x/en/v1.6-migration/monitor-apps/_index.md
@@ -11,6 +11,10 @@ Use this document to correct Rancher v2.x workloads and services that list `heal
For example, for the image below, we would configure liveness probes for the `web` and `weblb` workloads (i.e., the Kubernetes manifests output by migration-tools CLI).
+Resolve health_check for the web and webLB Workloads
+
+
+
## In This Document
@@ -37,6 +41,8 @@ The health check microservice features two types of health checks, which have a
The following diagram displays the health check microservice evaluating a container running Nginx. Notice that the microservice is making its check across nodes.
+
+
## Rancher v2.x Health Checks
In Rancher v2.x, the health check microservice is replaced with Kubernete's native health check mechanisms, called _probes_. These probes, similar to the Rancher v1.6 health check microservice, monitor the health of pods over TCP and HTTP.
@@ -63,6 +69,8 @@ Kubernetes includes two different _types_ of probes: liveness checks and readine
The following diagram displays kubelets running probes on containers they are monitoring ([kubelets](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/) are the primary "agent" running on each node). The node on the left is running a liveness probe, while the one of the right is running a readiness check. Notice that the kubelet is scanning containers on its host node rather than across nodes, as in Rancher v1.6.
+
+
## Configuring Probes in Rancher v2.x
The [migration-tool CLI]({{< baseurl >}}/rancher/v2.x/en/v1.6-migration/run-migration-tool/) cannot parse health checks from Compose files to Kubernetes manifest. Therefore, if want you to add health checks to your Rancher v2.x workloads, you'll have to add them manually.
@@ -73,6 +81,10 @@ If the probe fails, the container is restarted per the restartPolicy defined in
Configure probes by using the **Health Check** section while editing deployments called out in `output.txt`.
+Edit Deployment: Health Check Section
+
+
+
### Configuring Checks
While you create a workload using Rancher v2.x, we recommend configuring a check that monitors the health of the deployment's pods.
@@ -85,6 +97,8 @@ TCP checks monitor your deployment's health by attempting to open a connection t
You can configure the probe along with values for specifying its behavior by selecting the **TCP connection opens successfully** option in the **Health Check** section. For more information, see [Deploying Workloads]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/workloads/deploy-workloads/). For help setting probe timeout and threshold values, see [Health Check Parameter Mappings](#health-check-parameter-mappings).
+
+
When you configure a readiness check using Rancher v2.x, the `readinessProbe` directive and the values you've set are added to the deployment's Kubernetes manifest. Configuring a readiness check also automatically adds a liveness check (`livenessProbe`) to the deployment.
+Rancher v2.x: Workload Deployment
+
+
+
Rancher schedules pods to the node you select if 1) there are compute resource available for the node and 2) you've configured port mapping to use the HostPort option, that there are no port conflicts.
If you expose the workload using a NodePort that conflicts with another workload, the deployment gets created successfully, but no NodePort service is created. Therefore, the workload isn't exposed outside of the cluster.
After the workload is created, you can confirm that the pods are scheduled to your chosen node. From the project view, click **Resources > Workloads.** (In versions prior to v2.3.0, click the **Workloads** tab.) Click the **Group by Node** icon to sort your workloads by node. Note that both Nginx pods are scheduled to the same node.
+
+
). A _DaemonSet_ functions exactly like a Rancher v1.6 global service. The Kubernetes scheduler deploys a pod on each node of the cluster, and as new nodes are added, the scheduler will start new pods on them provided they match the scheduling requirements of the workload. Additionally, in v2.x, you can also limit a DaemonSet to be deployed to nodes that have a specific label.
To create a daemonset while configuring a workload, choose **Run one pod on each node** from the **Workload Type** options.
+Workload Configuration: Choose run one pod on each node to configure daemonset
+
+
+
### Scheduling Pods Using Resource Constraints
While creating a service in the Rancher v1.6 UI, you could schedule its containers to hosts based on hardware requirements that you choose. The containers are then scheduled to hosts based on which ones have bandwidth, memory, and CPU capacity.
@@ -204,6 +238,10 @@ To declare resource constraints, edit your migrated workloads, editing the **Sec
- Memory Limit
- CPU Limit
+Scheduling: Resource Constraint Settings
+
+
+
You can find more detail about these specs and how to use them in the [Kubernetes Documentation](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#resource-requests-and-limits-of-pod-and-container).
### [Next: Service Discovery]({{< baseurl >}}/rancher/v2.x/en/v1.6-migration/discover-services/)
diff --git a/static/img/rancher/add-custom-metrics.gif b/static/img/rancher/add-custom-metrics.gif
new file mode 100644
index 00000000000..9c6405a3433
Binary files /dev/null and b/static/img/rancher/add-custom-metrics.gif differ
diff --git a/static/img/rancher/add-ingress-form.png b/static/img/rancher/add-ingress-form.png
new file mode 100644
index 00000000000..405ff3abf1e
Binary files /dev/null and b/static/img/rancher/add-ingress-form.png differ
diff --git a/static/img/rancher/add-ingress.gif b/static/img/rancher/add-ingress.gif
new file mode 100644
index 00000000000..b9a3f449d5b
Binary files /dev/null and b/static/img/rancher/add-ingress.gif differ
diff --git a/static/img/rancher/add-node-label.gif b/static/img/rancher/add-node-label.gif
new file mode 100644
index 00000000000..9c41e774064
Binary files /dev/null and b/static/img/rancher/add-node-label.gif differ
diff --git a/static/img/rancher/add-pod-label.gif b/static/img/rancher/add-pod-label.gif
new file mode 100644
index 00000000000..b78da3ce7cb
Binary files /dev/null and b/static/img/rancher/add-pod-label.gif differ
diff --git a/static/img/rancher/add-record.png b/static/img/rancher/add-record.png
new file mode 100644
index 00000000000..8838a5ea6ff
Binary files /dev/null and b/static/img/rancher/add-record.png differ
diff --git a/static/img/rancher/auth-providers.svg b/static/img/rancher/auth-providers.svg
new file mode 100644
index 00000000000..8b53323d25a
--- /dev/null
+++ b/static/img/rancher/auth-providers.svg
@@ -0,0 +1,2 @@
+
+
\ No newline at end of file
diff --git a/static/img/rancher/cattle-load-balancer.svg b/static/img/rancher/cattle-load-balancer.svg
new file mode 100644
index 00000000000..70db25baa0b
--- /dev/null
+++ b/static/img/rancher/cattle-load-balancer.svg
@@ -0,0 +1,2 @@
+
+
\ No newline at end of file
diff --git a/static/img/rancher/deploy-service.gif b/static/img/rancher/deploy-service.gif
new file mode 100644
index 00000000000..bf97d1690e7
Binary files /dev/null and b/static/img/rancher/deploy-service.gif differ
diff --git a/static/img/rancher/deploy-workload-hostport.png b/static/img/rancher/deploy-workload-hostport.png
new file mode 100644
index 00000000000..ec6193df3c4
Binary files /dev/null and b/static/img/rancher/deploy-workload-hostport.png differ
diff --git a/static/img/rancher/deploy-workload-load-balancer.png b/static/img/rancher/deploy-workload-load-balancer.png
new file mode 100644
index 00000000000..4751b599a28
Binary files /dev/null and b/static/img/rancher/deploy-workload-load-balancer.png differ
diff --git a/static/img/rancher/deploy-workload-nodeport.png b/static/img/rancher/deploy-workload-nodeport.png
new file mode 100644
index 00000000000..d1cfa67e35b
Binary files /dev/null and b/static/img/rancher/deploy-workload-nodeport.png differ
diff --git a/static/img/rancher/edit-migration-workload.gif b/static/img/rancher/edit-migration-workload.gif
new file mode 100644
index 00000000000..f9510b8ff9f
Binary files /dev/null and b/static/img/rancher/edit-migration-workload.gif differ
diff --git a/static/img/rancher/enable-cluster-monitoring.gif b/static/img/rancher/enable-cluster-monitoring.gif
new file mode 100644
index 00000000000..baef3cc2487
Binary files /dev/null and b/static/img/rancher/enable-cluster-monitoring.gif differ
diff --git a/static/img/rancher/enable-project-monitoring.gif b/static/img/rancher/enable-project-monitoring.gif
new file mode 100644
index 00000000000..f44c67eb8f7
Binary files /dev/null and b/static/img/rancher/enable-project-monitoring.gif differ
diff --git a/static/img/rancher/health-check-section.png b/static/img/rancher/health-check-section.png
new file mode 100644
index 00000000000..4a4bfafe128
Binary files /dev/null and b/static/img/rancher/health-check-section.png differ
diff --git a/static/img/rancher/healthcheck-cmd-exec.png b/static/img/rancher/healthcheck-cmd-exec.png
new file mode 100644
index 00000000000..06b6b22ab6c
Binary files /dev/null and b/static/img/rancher/healthcheck-cmd-exec.png differ
diff --git a/static/img/rancher/healthcheck.svg b/static/img/rancher/healthcheck.svg
new file mode 100644
index 00000000000..55b573e578f
--- /dev/null
+++ b/static/img/rancher/healthcheck.svg
@@ -0,0 +1,2 @@
+
+
\ No newline at end of file
diff --git a/static/img/rancher/import-yaml-error.png b/static/img/rancher/import-yaml-error.png
new file mode 100644
index 00000000000..8af7a0878ce
Binary files /dev/null and b/static/img/rancher/import-yaml-error.png differ
diff --git a/static/img/rancher/imported-workloads.png b/static/img/rancher/imported-workloads.png
new file mode 100644
index 00000000000..75142fd0510
Binary files /dev/null and b/static/img/rancher/imported-workloads.png differ
diff --git a/static/img/rancher/kubernetes-load-balancer.svg b/static/img/rancher/kubernetes-load-balancer.svg
new file mode 100644
index 00000000000..bf9de1a3986
--- /dev/null
+++ b/static/img/rancher/kubernetes-load-balancer.svg
@@ -0,0 +1,2 @@
+
+
\ No newline at end of file
diff --git a/static/img/rancher/layer-4-lb-config-map.png b/static/img/rancher/layer-4-lb-config-map.png
new file mode 100644
index 00000000000..cf5c9dc168d
Binary files /dev/null and b/static/img/rancher/layer-4-lb-config-map.png differ
diff --git a/static/img/rancher/linked-service-workload.png b/static/img/rancher/linked-service-workload.png
new file mode 100644
index 00000000000..e0a1da0981f
Binary files /dev/null and b/static/img/rancher/linked-service-workload.png differ
diff --git a/static/img/rancher/liveness-check.png b/static/img/rancher/liveness-check.png
new file mode 100644
index 00000000000..e88cb297aae
Binary files /dev/null and b/static/img/rancher/liveness-check.png differ
diff --git a/static/img/rancher/load-balancer-links.png b/static/img/rancher/load-balancer-links.png
new file mode 100644
index 00000000000..5121abd0795
Binary files /dev/null and b/static/img/rancher/load-balancer-links.png differ
diff --git a/static/img/rancher/load-balancer-ssl-certs.png b/static/img/rancher/load-balancer-ssl-certs.png
new file mode 100644
index 00000000000..246ffd618f8
Binary files /dev/null and b/static/img/rancher/load-balancer-ssl-certs.png differ
diff --git a/static/img/rancher/migrate-schedule-workloads.png b/static/img/rancher/migrate-schedule-workloads.png
new file mode 100644
index 00000000000..c6ab638ac94
Binary files /dev/null and b/static/img/rancher/migrate-schedule-workloads.png differ
diff --git a/static/img/rancher/node-schedule-advanced-options.png b/static/img/rancher/node-schedule-advanced-options.png
new file mode 100644
index 00000000000..1d83edc767e
Binary files /dev/null and b/static/img/rancher/node-schedule-advanced-options.png differ
diff --git a/static/img/rancher/node-schedule-antiaffinity.png b/static/img/rancher/node-schedule-antiaffinity.png
new file mode 100644
index 00000000000..74bd0455b50
Binary files /dev/null and b/static/img/rancher/node-schedule-antiaffinity.png differ
diff --git a/static/img/rancher/node-scheduling-affinity.png b/static/img/rancher/node-scheduling-affinity.png
new file mode 100644
index 00000000000..28d44908232
Binary files /dev/null and b/static/img/rancher/node-scheduling-affinity.png differ
diff --git a/static/img/rancher/node-scheduling-labels.png b/static/img/rancher/node-scheduling-labels.png
new file mode 100644
index 00000000000..4e1a634e74b
Binary files /dev/null and b/static/img/rancher/node-scheduling-labels.png differ
diff --git a/static/img/rancher/node-scheduling.png b/static/img/rancher/node-scheduling.png
new file mode 100644
index 00000000000..953208144c7
Binary files /dev/null and b/static/img/rancher/node-scheduling.png differ
diff --git a/static/img/rancher/one-six-schedule.png b/static/img/rancher/one-six-schedule.png
new file mode 100644
index 00000000000..5bc05d915f8
Binary files /dev/null and b/static/img/rancher/one-six-schedule.png differ
diff --git a/static/img/rancher/output-dot-text.png b/static/img/rancher/output-dot-text.png
new file mode 100644
index 00000000000..ca39b2867b3
Binary files /dev/null and b/static/img/rancher/output-dot-text.png differ
diff --git a/static/img/rancher/probes.svg b/static/img/rancher/probes.svg
new file mode 100644
index 00000000000..007abfda6c1
--- /dev/null
+++ b/static/img/rancher/probes.svg
@@ -0,0 +1,2 @@
+
+
\ No newline at end of file
diff --git a/static/img/rancher/readiness-check-http.png b/static/img/rancher/readiness-check-http.png
new file mode 100644
index 00000000000..1b2b19c2a75
Binary files /dev/null and b/static/img/rancher/readiness-check-http.png differ
diff --git a/static/img/rancher/readiness-check-tcp.png b/static/img/rancher/readiness-check-tcp.png
new file mode 100644
index 00000000000..0ba9869eb7c
Binary files /dev/null and b/static/img/rancher/readiness-check-tcp.png differ
diff --git a/static/img/rancher/readiness-check.png b/static/img/rancher/readiness-check.png
new file mode 100644
index 00000000000..f978079aff7
Binary files /dev/null and b/static/img/rancher/readiness-check.png differ
diff --git a/static/img/rancher/resolve-affinity.png b/static/img/rancher/resolve-affinity.png
new file mode 100644
index 00000000000..d705a2c4fd8
Binary files /dev/null and b/static/img/rancher/resolve-affinity.png differ
diff --git a/static/img/rancher/resolve-global.png b/static/img/rancher/resolve-global.png
new file mode 100644
index 00000000000..583c500b8f6
Binary files /dev/null and b/static/img/rancher/resolve-global.png differ
diff --git a/static/img/rancher/resolve-health-checks.png b/static/img/rancher/resolve-health-checks.png
new file mode 100644
index 00000000000..3b7bfe282d1
Binary files /dev/null and b/static/img/rancher/resolve-health-checks.png differ
diff --git a/static/img/rancher/resolve-links.png b/static/img/rancher/resolve-links.png
new file mode 100644
index 00000000000..1f0544268f2
Binary files /dev/null and b/static/img/rancher/resolve-links.png differ
diff --git a/static/img/rancher/resolve-load-balancer.png b/static/img/rancher/resolve-load-balancer.png
new file mode 100644
index 00000000000..a03951098cf
Binary files /dev/null and b/static/img/rancher/resolve-load-balancer.png differ
diff --git a/static/img/rancher/resolve-pull-image.png b/static/img/rancher/resolve-pull-image.png
new file mode 100644
index 00000000000..a822469d795
Binary files /dev/null and b/static/img/rancher/resolve-pull-image.png differ
diff --git a/static/img/rancher/resolve-scale.png b/static/img/rancher/resolve-scale.png
new file mode 100644
index 00000000000..5d36dec666a
Binary files /dev/null and b/static/img/rancher/resolve-scale.png differ
diff --git a/static/img/rancher/resource-constraint-settings.png b/static/img/rancher/resource-constraint-settings.png
new file mode 100644
index 00000000000..68bf73cfc5d
Binary files /dev/null and b/static/img/rancher/resource-constraint-settings.png differ
diff --git a/static/img/rancher/schedule-specific-node.png b/static/img/rancher/schedule-specific-node.png
new file mode 100644
index 00000000000..211bd90a190
Binary files /dev/null and b/static/img/rancher/schedule-specific-node.png differ
diff --git a/static/img/rancher/scheduled-nodes.png b/static/img/rancher/scheduled-nodes.png
new file mode 100644
index 00000000000..14807de68f8
Binary files /dev/null and b/static/img/rancher/scheduled-nodes.png differ
diff --git a/static/img/rancher/separate-check.png b/static/img/rancher/separate-check.png
new file mode 100644
index 00000000000..d094073c02e
Binary files /dev/null and b/static/img/rancher/separate-check.png differ
diff --git a/static/img/rancher/view-edit-yaml.png b/static/img/rancher/view-edit-yaml.png
new file mode 100644
index 00000000000..36574ffa618
Binary files /dev/null and b/static/img/rancher/view-edit-yaml.png differ
diff --git a/static/img/rancher/workload-scale.png b/static/img/rancher/workload-scale.png
new file mode 100644
index 00000000000..f8aa87a6d5c
Binary files /dev/null and b/static/img/rancher/workload-scale.png differ
diff --git a/static/img/rancher/workload-type-option.png b/static/img/rancher/workload-type-option.png
new file mode 100644
index 00000000000..02c74e29a6e
Binary files /dev/null and b/static/img/rancher/workload-type-option.png differ
diff --git a/static/img/rancher/workload-type.png b/static/img/rancher/workload-type.png
new file mode 100644
index 00000000000..cfa3493381d
Binary files /dev/null and b/static/img/rancher/workload-type.png differ