From 670054d514add698231f6400e082eb3a8fc3a119 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Mon, 7 May 2018 10:51:30 -0700 Subject: [PATCH] fixed broken images and removed duplicate content --- .../v2.x/en/concepts/overview/_index.md | 23 ------------------- .../v2.x/en/quick-start-guide/_index.md | 6 ++--- 2 files changed, 3 insertions(+), 26 deletions(-) delete mode 100644 content/rancher/v2.x/en/concepts/overview/_index.md diff --git a/content/rancher/v2.x/en/concepts/overview/_index.md b/content/rancher/v2.x/en/concepts/overview/_index.md deleted file mode 100644 index 8c08ef7e23f..00000000000 --- a/content/rancher/v2.x/en/concepts/overview/_index.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -title: Overview -weight: 2025 ---- - -# Rancher 2.0 Overview - -## What's Rancher? - -Rancher is a container management platform built for organizations that deploy containers in production. Rancher makes it easy to run Kubernetes everywhere, meet IT requirements, and empower DevOps teams. - -Run Kubernetes Everywhere. Kubernetes is not only the de-facto container orchestration standard, it is rapidly becoming a form of standard infrastructure available from all cloud and virtualization vendors. Rancher users have the choice of creating Kubernetes clusters with Rancher Kubernetes Engine (RKE), cloud Kubernetes services like GKE, AKS, and EKS. Rancher users can also import and manage their existing Kubernetes clusters created using any Kubernetes distributions or installers. - -Meet IT Requirements. Rancher supports centralized authentication for all Kubernetes clusters under management. An employee of a large enterprise, for example, can use his corporate Active Directory credential to gain access to Kubernetes clusters in GKE. IT administrators can setup and enforce access control and security policies across all users, groups, projects, clusters, and clouds. IT administrators have a single-pane-of-glass view of the health and capacity of all their Kubernetes clusters. - -Empower DevOps Teams. Rancher provides an intuitive user interface for DevOps engineers to manage their application workload. The user does not need to have in-depth knowledge of Kubernetes concepts to start using Rancher. Rancher catalog contains a set of useful DevOps tools. Rancher is certified with a wide selection of cloud native ecosystem products, including, for example, security tools, monitoring systems, container registries, and storage and networking drivers. -The following figure illustrates the role Rancher plays in IT and DevOps organizations. Each team deploys their applications on the public or private clouds they choose. IT administrators gain visibility and enforce policies across all users, clusters, and clouds. - -{{< figure src="assets/platform.png" title="Rancher Platform">}} - -## What's New? - -The previous version, Rancher 1.6, was a container management platform built on docker. Rancher 2.0 build on the success and experience of Rancher 1.6 but bulk of the system has been rearchitected to work on Kubernetes. Rancher 2.0 retains the ease-of-use of Rancher 1.6 UI and catalog. Rancher 2.0 includes many new features such as the built-in CI pipeline, alerts and log aggregation, multi-cluster management, RKE, and integration with cloud Kubernetes services such as GKE, EKS, and AKS. diff --git a/content/rancher/v2.x/en/quick-start-guide/_index.md b/content/rancher/v2.x/en/quick-start-guide/_index.md index cbb0f137fab..7cfb04e6f01 100644 --- a/content/rancher/v2.x/en/quick-start-guide/_index.md +++ b/content/rancher/v2.x/en/quick-start-guide/_index.md @@ -151,13 +151,13 @@ For this workload, you'll be deploying the application Nginx. 7. From **Port Mapping**, click **Add Port**. 8. From the **As a** drop-down, make sure that **NodePort (On every node)** is selected. -![As a dropdown, NodePort (On every node selected)]({{< baseurl >}}/src/img/nodeport-dropdown.png) +![As a dropdown, NodePort (On every node selected)]({{< baseurl >}}/img/rancher/nodeport-dropdown.png) 9. From the **On Listening Port** field, leave the **Random** value in place. -![On Listening Port, Random selected](images/on_listening_port_random.png) +![On Listening Port, Random selected]({{< baseurl >}}/img/rancher/listening-port-field.png) 10. From the **Publish the container port** field, enter port `80`. -![Publish the container port, 80 entered](images/publish_the_container_port_80.png) +![Publish the container port, 80 entered]({{< baseurl >}}/img/rancher/container-port-field.png) 11. Leave the remaining options on their default setting. We'll tell you about them later.