fixing the headings I missed

This commit is contained in:
Mark Bishop
2018-05-14 13:10:48 -07:00
committed by Mark Bishop
parent 537f162b4a
commit 9e459d8a24
11 changed files with 4 additions and 25 deletions
@@ -2,8 +2,6 @@
title: Concepts title: Concepts
weight: 2000 weight: 2000
--- ---
# Concepts
This section describes the different features in Rancher, the ideas behind them, and how they work. This section describes the different features in Rancher, the ideas behind them, and how they work.
Choose a concept from the side-menu to start learning about Rancher! Choose a concept from the side-menu to start learning about Rancher!
@@ -1,4 +1,5 @@
--- ---
title: Alerts and Notifiers title: Alerts and Notifiers
weight: 2300 weight: 2300
draft: true
--- ---
@@ -2,9 +2,6 @@
title: Global Configuration title: Global Configuration
weight: 2075 weight: 2075
--- ---
# Global Configuration
After installing Rancher 2.0, you should configure it to support your users and environment. This section describes the global configurations you should make after installation. After installing Rancher 2.0, you should configure it to support your users and environment. This section describes the global configurations you should make after installation.
# Authentication # Authentication
@@ -3,6 +3,3 @@ title: Logging
weight: 2325 weight: 2325
draft: true draft: true
--- ---
# Logging
Coming Soon!
@@ -2,9 +2,6 @@
title: Projects title: Projects
weight: 2150 weight: 2150
--- ---
# Projects
## What's a Project? ## What's a Project?
Project is a new concept introduced by Rancher. It is not a native Kubernetes construct. A project captures a set of policies for a set of namespaces. A user can be assigned a specific role in a project. A role can be owner, member, read-only, or custom. Policies include Kubernetes Role-Based Access Control (RBAC) policies and pod security policies. Rancher 2.0 also implements a canned network policy that isolates containers in different projects. Future versions of Rancher will implement more flexible network policies. Project is a new concept introduced by Rancher. It is not a native Kubernetes construct. A project captures a set of policies for a set of namespaces. A user can be assigned a specific role in a project. A role can be owner, member, read-only, or custom. Policies include Kubernetes Role-Based Access Control (RBAC) policies and pod security policies. Rancher 2.0 also implements a canned network policy that isolates containers in different projects. Future versions of Rancher will implement more flexible network policies.
@@ -3,9 +3,6 @@ title: Resources
weight: 2275 weight: 2275
draft: true draft: true
--- ---
# Resources
Coming Soon Coming Soon
## Certificates ## Certificates
@@ -1,5 +1,5 @@
--- ---
title: Service Discovery title: Service Discovery
weight: 2200 weight: 2200
draft: true
--- ---
# Service Discovery
@@ -3,9 +3,6 @@ title: Storage
weight: 2125 weight: 2125
draft: true draft: true
--- ---
# Storage
Coming Soon Coming Soon
## Persistent Volumes ## Persistent Volumes
@@ -2,9 +2,6 @@
title: Users and Roles title: Users and Roles
weight: weight:
--- ---
# Users and Roles
Every user in {{< product >}} is assigned a _role_, which is a set of permissions that determine what Kubernetes API endpoints that the user can access. Let's use this metaphor: a user account is like getting access to an entire office building; however, the user's role determine what rooms the user can access within the building. Every user in {{< product >}} is assigned a _role_, which is a set of permissions that determine what Kubernetes API endpoints that the user can access. Let's use this metaphor: a user account is like getting access to an entire office building; however, the user's role determine what rooms the user can access within the building.
Within {{< product >}} there are two types of user roles: Within {{< product >}} there are two types of user roles:
@@ -3,9 +3,6 @@ title: Workloads
weight: 2175 weight: 2175
draft: true draft: true
--- ---
# Workloads
You can build any complex workload in Kubernetes using two basic constructs: pods and controllers. You can build any complex workload in Kubernetes using two basic constructs: pods and controllers.
## Workload Types ## Workload Types
@@ -1,5 +1,6 @@
--- ---
shortTitle: Creating an Azure Cluster title: Creating an Azure Cluster
shortTitle: Azure
weight: 3300 weight: 3300
--- ---