Merge pull request #337 from deniseschannon/release-rke

Release rke
2026-09-27 21:50:21 +00:00 · 2018-06-22 21:26:38 -07:00
parent fd94104862 58e6c73a58
commit 9f5e6293a3
27 changed files with 31 additions and 47 deletions
@@ -1,35 +1,45 @@
 ---
 title: "Documentation | Rancher Labs"
-pageHeader: "Docs"
+pageHeader: "Rancher Docs"
 subTitle: "sub"
 description: ""
 ---
 <section class="p-v-lg">
  <div class="wrapper">
-    <div class="row center-xs">
+    <div class="row middle-xs">
-      <div class="col-md-8">
+      <div class="col-md-3">
        <p>Rancher is open source software that combines everything an organization needs to adopt and run containers in production. Built on Kubernetes, Rancher makes it easy for DevOps teams to test, deploy and manage their applications. Operations teams use Rancher to deploy, manage and secure every Kubernetes deployment regardless of where it is running.</p>
      </div>
-    </div>
+      <div class="col-md-9 row">
-    <div class="row middle-xs center-xs">
+        <div class="col-md-6 p-a-xs">
      <div class="col-md">
        <h3 class="bg-default m-a-0 p-a-sm">Rancher 2.x</h3>
          <div class="box p-a-sm">
-            <a href="{{< baseurl >}}/rancher/v2.x/en/" class="btn bg-link">Read the Docs</a>
+          <h3 class="m-t-0">Rancher 2.x</h3>
-          </div>
+          <p>The most of Rancher is redesigned to work on Kubernetes. Rancher 2.0 retains the user-friendly features of version 1.6, such as the UI and catalog.</p>
-      </div>
+          <a href="{{< baseurl >}}/rancher/v2.x/en/" class="btn bg-link">Read the Docs</a>
-      <div class="col-md">
+        </div>
-        <h3 class="bg-default m-a-0 p-a-sm">Rancher 1.6</h3>
+        </div>
        <div class="col-md-6 p-a-xs">
          <div class="box p-a-sm">
-            <a href="https://rancher.com/docs/rancher/v1.6/en/" target="_blank" class="btn bg-link">Read the Docs</a>
+          <h3 class="m-t-0">Rancher 1.6</h3>
-          </div>
+          <p>Rancher enables organizations to run and manage Docker and Kubernetes in production without having to build a container services platform from scratch.</p>
-      </div>
+          <a href="https://rancher.com/docs/rancher/v1.6/en/" target="_blank" class="btn bg-link">Read the Docs</a>
-      <div class="col-md">
+        </div>
-        <h3 class="bg-default m-a-0 p-a-sm">RancherOS</h3>
+        </div>
        <div class="col-md-6 p-a-xs">
          <div class="box p-a-sm">
-            <a href="{{< baseurl >}}/os/v1.x/en/" class="btn bg-link">Read the Docs</a>
+          <h3 class="m-t-0">RancherOS</h3>
-          </div>
+          <p>RancherOS is the smallest, easiest way to run Docker in production. Everything in RancherOS is a container managed by Docker.</p>
          <a href="{{< baseurl >}}/os/v1.x/en/" class="btn bg-link">Read the Docs</a>
        </div>
        </div>
        <div class="col-md-6 p-a-xs">
          <div class="box p-a-sm">
          <h3 class="m-t-0">RKE</h3>
          <p>Rancher Kubernetes Engine (RKE) is an extremely simple, lightning fast Kubernetes installer that works everywhere.</p>
          <a href="{{< baseurl >}}/rke/v0.1.x/en" class="btn bg-link">Read the Docs</a>
        </div>
        </div>
      </div>
    </div>
  </div>
@@ -2,5 +2,4 @@
 title: RKE
 weight: 1
 showBreadcrumb: false
 draft: true
 ---
@@ -1,5 +1,4 @@
 ---
 title: v0.1.x
 showBreadcrumb: false
 draft: true
 ---
@@ -2,7 +2,6 @@
 title: Overview of RKE
 shortTitle: RKE
 weight: 1
 draft: true
 ---
 Rancher Kubernetes Engine (RKE) is a light-weight Kubernetes installer that supports installation on bare-metal and virtualized servers. RKE solves a common issue in the Kubernettes community: installation complexity. With RKE, Kubernetes installation is simplified, regardless of what operating systems and platforms you're running.
@@ -1,7 +1,6 @@
 ---
 title: Config Options
 weight: 200
 draft: true
 ---
 When setting up your `cluster.yml` for RKE, there are a lot of different options that can be configured to control the behavior of how RKE launches Kubernetes.
@@ -1,7 +1,6 @@
 ---
 title: Add-Ons
 weight: 250
 draft: true
 ---
 RKE supports pluggable add-ons. Add-ons are used to deploy several cluster components including:
@@ -1,7 +1,6 @@
 ---
 title: Ingress Controllers
 weight: 252
 draft: true
 ---
 By default, RKE deploys the nginx ingress controller on all schedulable nodes.
@@ -1,7 +1,6 @@
 ---
 title: Network Plug-ins
 weight: 251
 draft: true
 ---
 RKE supports the following network plug-ins that are deployed as add-ons:
@@ -1,7 +1,6 @@
 ---
 title: User-Defined Add-Ons
 weight: 253
 draft: true
 ---
 Besides the [network plug-in]({{< baseurl >}}/rke/v0.1.x/en/config-options/network-plugins/) and [ingress controllers]({{< baseurl >}}/rke/v0.1.x/en/config-options/ingress-controllers/), you can define any add-on that you want deployed after the Kubernetes cluster is deployed.
@@ -1,7 +1,6 @@
 ---
 title: Authentication
 weight: 235
 draft: true
 ---
 RKE supports x509 authentication strategy. You can additionally define a list of SANs (Subject Alternative Names) to add to the Kubernetes API Server PKI certificates. As an example, this allows you to connect to your Kubernetes cluster API Server through a load balancer instead of a single node.
@@ -1,7 +1,6 @@
 ---
 title: Authorization
 weight: 240
 draft: true
 ---
 Kubernetes supports multiple [Authorization Modules](https://kubernetes.io/docs/reference/access-authn-authz/authorization/#authorization-modules). Currently, RKE only supports the [RBAC module](https://kubernetes.io/docs/reference/access-authn-authz/rbac/).
@@ -1,7 +1,6 @@
 ---
 title: Bastion/Jump Host Configuration
 weight: 220
 draft: true
 ---
 Since RKE uses `ssh` to connect to [nodes]({{< baseurl >}}/rke/v0.1.x/en/config-options/nodes/), you can configure to use a bastion host.
@@ -1,7 +1,6 @@
 ---
 title: Cloud Providers
 weight: 245
 draft: true
 ---
 RKE supports the ability to set your specific [cloud provider](https://kubernetes.io/docs/concepts/cluster-administration/cloud-providers/) for your Kubernetes cluster. There are specific cloud configurations  for these cloud providers:
@@ -1,7 +1,6 @@
 ---
 title: Example Cluster.ymls
 weight: 205
 draft: true
 ---
 There are lots of different config options that can be set in the cluster configuration file for RKE. Here are some examples of files:
@@ -1,7 +1,6 @@
 ---
 title: Nodes
 weight: 210
 draft: true
 ---
 The `nodes` directive is the only required section in the `cluster.yml` file. It's used by RKE to specify cluster node(s), ssh credentials used to access the node(s) and which roles these nodes will be in the Kubernetes cluster.
@@ -1,7 +1,6 @@
 ---
 title: Private Registries
 weight: 215
 draft: true
 ---
 RKE supports the ability to configure multiple private Docker registries. By passing in your registry and credentials, it allows the nodes to pull images from these private registries.  
@@ -1,7 +1,6 @@
 ---
 title: Kubernetes Default Services
 weight: 230
 draft: true
 ---
 To deploy Kubernetes, RKE deploys several core components or services in Docker containers on the nodes. Based on the roles of the node, the containers deployed may be different.
@@ -1,7 +1,6 @@
 ---
 title: External etcd
 weight: 232
 draft: true
 ---
 By default, RKE will launch etcd servers, but RKE also supports being able to use an external etcd. RKE only supports connecting to a TLS enabled etcd setup.
@@ -1,7 +1,6 @@
 ---
 title: Extra Args, Extra Binds, and Extra Environment Variables
 weight: 231
 draft: true
 ---
 RKE supports additional service arguments, volume binds and environment variables.
@@ -1,7 +1,6 @@
 ---
 title: System Images
 weight: 225
 draft: true
 ---
 When RKE is deploying Kubernetes, there are several images that are pulled. These images are used as Kubernetes system components as well as helping to deploy these system components.  
@@ -1,7 +1,6 @@
 ---
 title: Installation
 weight: 50
 draft: true
 ---
 RKE is a fast, versatile Kubernetes installer that you can use to install Kubernetes on your Linux hosts. You can get started in a couple of quick and easy steps:
@@ -1,7 +1,6 @@
 ---
 title: Backups and Disaster Recovery
 weight: 65
 draft: true
 ---
 As of v0.1.7, you can configure a RKE cluster to automatically take snapshots of etcd. In a disaster scenario, you can restore these snapshots, which are stored on other nodes in the cluster.
@@ -1,7 +1,6 @@
 ---
 title: Managing RKE Clusters
 weight: 60
 draft: true
 ---
 ### Adding/Removing Nodes
@@ -1,7 +1,6 @@
 ---
 title: Operating System Requirements
 weight: 55
 draft: true
 ---
 RKE runs on almost any Linux OS with Docker installed. Most of the development and testing of RKE occurred on Ubuntu 16.04. However, some OS's have restrictions and specific requirements.
@@ -13,8 +13,8 @@
 {{ end }}
 {{ define "main" }}
 {{ partial "docs-nav.html" . }}
  <div class="wrapper">
    {{ partial "docs-nav.html" . }}
    {{ $secondLevel := ($.Scratch.Get "secondLevel") }}
    {{ $.Scratch.Set "showSidebar" false }}
    {{ with $secondLevel }}
@@ -13,8 +13,8 @@
 {{ end }}
 {{ define "main" }}
 {{ partial "docs-nav.html" . }}
  <div class="wrapper">
    {{ partial "docs-nav.html" . }}
    {{ $secondLevel := ($.Scratch.Get "secondLevel") }}
    {{ $.Scratch.Set "showSidebar" false }}
    {{ with $secondLevel }}
@@ -51,5 +51,3 @@
  </div>
 {{ end }}
@@ -68,4 +68,3 @@
  </nav>
 </div>
 </nav>