diff --git a/content/rancher/v2.x/en/kubernetes-in-rancher/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/_index.md index 812e75542b3..b701634ee32 100644 --- a/content/rancher/v2.x/en/kubernetes-in-rancher/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/_index.md @@ -9,14 +9,83 @@ aliases: After you provision a Kubernetes (K8s) cluster in Rancher, you can begin using powerful K8s features from the Rancher UI to manage the cluster, allowing you to deploy and scale your containerized applications in development, testing, or production environments. +Do Lorem ut et quis laboris dolore enim ad voluptate. Veniam reprehenderit mollit id anim in labore ipsum voluptate anim ut nostrud. Nulla laborum voluptate culpa veniam ullamco ad laboris enim. Sint qui proident laboris aliquip veniam in enim reprehenderit officia nostrud pariatur pariatur. + +Magna est sint irure adipisicing dolor. Pariatur duis sunt commodo esse ex do deserunt. Et adipisicing velit mollit nisi do commodo. Velit do anim aliqua consectetur. + +Occaecat esse amet nulla cupidatat Lorem velit. Quis eu ex dolor pariatur id sit aliqua. Ex enim elit voluptate sint deserunt proident veniam occaecat occaecat velit exercitation deserunt dolore. + ## Advanced Cluster Interaction +Although the primary method of interacting with your Kubernetes clusters created using Rancher is the Rancher UI, you have additional options for controlling your clusters: + +- **kubectl** + + You can use the Kubernetes command-line tool, [kubectl](https://kubernetes.io/docs/reference/kubectl/overview/), to control your clusters. You have two options for using kubectl: + + - **Rancher kubectl shell** + + You can interact with your clusters by launching the kubectl shell available in the Rancher UI. This option requires no configuration actions on your part. + + For more information, see [Accessing Clusters with kubectl Shell]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/kubectl/#accessing-clusters-with-kubectl-shell). + + - **Terminal remote connection**: + + You can also interact with your clusters by installing [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) and then copying your cluster's kubeconfig file from the Rancher UI to your local `~/.kube/config` directory. + + For more information, see [Accessing Clusters with kubectl and a kubeconfig File]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/kubectl/#accessing-clusters-with-kubectl-and-a-kubeconfig-file). + +- **Rancher CLI** + + You can interact with your clusters by downloading Rancher's own command-line interface, [Rancher CLI]({{< baseurl >}}/rancher/v2.x/en/cli/). + +- **Rancher API** + + Finally, you can interact with your clusters over the Rancher API. However, before you use the API, you must obtain an [API key]({{< baseurl >}}/rancher/v2.x/en/user-settings/api-keys/) using the Rancher UI. + ## Node Management +After you launch a Rancher cluster, you can edit many of the settings you configured during its initial launch, including: + +- The cluster's [members]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/cluster-project-roles/#membership-and-role-assignment) and [roles]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/cluster-project-roles/#project-roles). +- Its [Kubernetes options]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/), including: + + - The version of Kubernetes installed. + - Whether the cluster allows unsupported versions of Docker to run. + - Whether the cluster uses a cloud provider. + - Whether the cluster applies a pod security policy. + + >**Note:** You cannot edit the clusters Network Provider after its initial launch. + +- The [node pools]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/#node-pools) configured for the cluster. + +For instructions on how to edit a cluster's settings, see [Editing Clusters]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/editing-clusters). + +Additionally, you can also edit individual nodes using the **Nodes** tab, from which you can complete the following actions: + +- Enter custom names and descriptions for each node. +- Add [labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) to each node. +- Pause nodes using the **Cordon** button. +- **Delete** nodes. +- Scale the number of nodes in the cluster up or down. +- Download the access keys for each node. + ## Projects and Namespaces -Rancher extends the application of the Kubernetes namespace resources listed above to [projects]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/projects-namespaces/), which are Rancher-specific constructs. In the hierarchy of Rancher objects, projects contain namespaces. Therefore, any resources available within a project are available for all namespaces within that project. +In use cases where many users share use of a cluster, you can divide it into different [namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/) and [projects]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/projects-and-namespaces/) to prevent conflicts. +- [Namespaces]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/projects-and-namespaces/#namespaces) + + Namespaces are objects you can use to restrict cluster resources among groups of users and applications. Using namesspaces, you can limit the cluster objects that users can access, including: + + - **[Workloads](#workloads)**: standard workloads, load balancers, service discovery records, and storage. + - **[Resources](#kubernetes-resources)**: certificates, ConfigMaps, registries, and secrets. + +- [Projects]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/projects-and-namespaces/) + + Projects are a feature available in Rancher, but not the base version of Kubernetes. Projects allows you to group different namespaces a single object. You can then use your project to set user access and pod security policies using a single object (the project) rather than many (namespaces). + + You can also assign the workloads and resources mentioned above to a project. Therefore, any resources available within a project are available for all namespaces within that project. ## Workloads diff --git a/content/rancher/v2.x/en/kubernetes-in-rancher/projects-and-namespaces/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/projects-and-namespaces/_index.md index 316621fed6e..a04ea3c5612 100644 --- a/content/rancher/v2.x/en/kubernetes-in-rancher/projects-and-namespaces/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/projects-and-namespaces/_index.md @@ -7,6 +7,8 @@ aliases: - /rancher/v2.x/en/tasks/projects/create-project/ --- +## Projects + _Projects_ are a new concept introduced by Rancher. They are 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]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/default-custom-roles/). 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. ## Authorization