mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-25 04:28:15 +00:00
fixed images and air gap website
This commit is contained in:
Mark Bishop
@@ -28,7 +28,7 @@ Rancher provides an intuitive user interface for DevOps engineers to manage thei
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## What's New?
|
||||
@@ -73,7 +73,7 @@ Majority of Rancher 2.0 software runs on the Rancher server. Rancher server inc
|
||||
|
||||
The figure below illustrates the high-level architecture of Rancher 2.0. The figure depicts a Rancher server installation that manages two Kubernetes clusters: one Kubernetes cluster created by RKE and another Kubernetes cluster created by GKE.
|
||||
|
||||
|
||||
|
||||
|
||||
In this section we describe the functionalities of each Rancher server components.
|
||||
|
||||
|
||||
+1
-1
@@ -10,7 +10,7 @@ If you have a private registry, you can move Rancher into that registry and inst
|
||||
>**Prerequisite:** It is assumed you either have your own private registry or other means of distributing docker images to your machine. If you need help with creating a private registry, please refer to the [Docker documentation for private registries](https://docs.docker.com/registry/).
|
||||
|
||||
|
||||
1. Browse to https://github.com/rancher/rancher/releases/tag/v2.0.0-beta4-rc2 and download all files in the release.
|
||||
1. Browse to https://github.com/rancher/rancher/releases/tag/v2.0.0 and download all files in the release.
|
||||
|
||||
2. Run rancher-save-images.sh in an environment that has access to dockerhub. This script will download all images into a file rancher-images.tar.gz.
|
||||
|
||||
|
||||
@@ -3,25 +3,44 @@ title: Overview
|
||||
shortTitle: Rancher 2.0
|
||||
weight: 1
|
||||
---
|
||||
|
||||
# Rancher 2.0 Documentation
|
||||
|
||||
## Rancher Overview
|
||||
|
||||
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.
|
||||
### Run Kubernetes Everywhere
|
||||
|
||||
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.
|
||||
Kubernetes has become the container orchestration standard. Most cloud and virtualization vendors now offer it as standard infrastructure. Rancher users have the choice of creating Kubernetes clusters with Rancher Kubernetes Engine (RKE) or cloud Kubernetes services, such as GKE, AKS, and EKS. Rancher users can also import and manage their existing Kubernetes clusters created using any Kubernetes distribution or installer.
|
||||
|
||||
### Meet IT requirements
|
||||
|
||||
Rancher supports centralized authentication for all Kubernetes clusters under its control. For example, you can:
|
||||
|
||||
- Use your Active Directory credentials to access Kubernetes clusters hosted by cloud vendors, such as GKE.
|
||||
- Setup and enforce access control and security policies across all users, groups, projects, clusters, and clouds.
|
||||
- View the health and capacity of your Kubernetes clusters from a single-pane-of-glass.
|
||||
|
||||
### 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.
|
||||
|
||||
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.
|
||||
The previous version of Rancher, version 1.6, was a container management platform built on Docker. Rancher 2.0 builds on the success and experience of Rancher 1.6.
|
||||
|
||||
However, for version 2.0, most of Rancher has been redesigned to work on Kubernetes. Rancher 2.0 retains the user-friendly features of version 1.6, such as the UI and catalog. However, 2.0 now includes many new features such as:
|
||||
|
||||
- Built-in CI pipeline
|
||||
- Alerts and log aggregation
|
||||
- Multi-cluster management
|
||||
- Rancher Kubernetes Engine (RKE)
|
||||
- Integration with cloud Kubernetes services, such as GKE, EKS, and AKS.
|
||||
|
||||
# Rancher Architecture
|
||||
|
||||
@@ -51,9 +70,9 @@ We now cover high-level Rancher architecture.
|
||||
|
||||
Majority of Rancher 2.0 software runs on the Rancher server. Rancher server includes all the software components used to manage the entire Rancher deployment.
|
||||
|
||||
Figure 2 illustrates the high-level architecture of Rancher 2.0. The figure depicts a Rancher server installation that manages two Kubernetes clusters: one Kubernetes cluster created by RKE and another Kubernetes cluster created by GKE.
|
||||
The figure below illustrates the high-level architecture of Rancher 2.0. The figure depicts a Rancher server installation that manages two Kubernetes clusters: one Kubernetes cluster created by RKE and another Kubernetes cluster created by GKE.
|
||||
|
||||
{{< figure src="assets/rancher-architecture.png" title="Rancher Architecture">}}
|
||||
|
||||
|
||||
In this section we describe the functionalities of each Rancher server components.
|
||||
|
||||
@@ -75,17 +94,17 @@ The cluster controller and cluster agents implement the business logic required
|
||||
|
||||
Cluster agents perform the following activities:
|
||||
|
||||
1. Manage workload. This includes, for example, creating pods and deployments in each cluster.
|
||||
- Manage workload. This includes, for example, creating pods and deployments in each cluster.
|
||||
|
||||
2. Applying roles and bindings that are defined in global policies into every cluster.
|
||||
- Applying roles and bindings that are defined in global policies into every cluster.
|
||||
|
||||
3. Propagate information from cluster to rancher server: events, stats, node info, and health.
|
||||
- Propagate information from cluster to rancher server: events, stats, node info, and health.
|
||||
|
||||
The cluster controller performs the following activities:
|
||||
|
||||
1. Configures access control policies to clusters and projects.
|
||||
- Configures access control policies to clusters and projects.
|
||||
|
||||
2. Provisions clusters by invoking the necessary Docker machine drivers and invoking Kubernetes engines like RKE and GKE.
|
||||
- Provisions clusters by invoking the necessary Docker machine drivers and invoking Kubernetes engines like RKE and GKE.
|
||||
|
||||
#### Authentication Proxy
|
||||
|
||||
|
||||
Reference in New Issue
Block a user