diff --git a/content/rancher/v2.x/en/admin-settings/pod-security-policies/_index.md b/content/rancher/v2.x/en/admin-settings/pod-security-policies/_index.md index 9857571848c..b2aa12204c4 100644 --- a/content/rancher/v2.x/en/admin-settings/pod-security-policies/_index.md +++ b/content/rancher/v2.x/en/admin-settings/pod-security-policies/_index.md @@ -51,7 +51,15 @@ Using Rancher, you can create a Pod Security Policy using our GUI rather than cr ### What's Next? -Now that you've created a Pod Security Policy, you can apply it to clusters and projects. For more information, see [Adding a Pod Security Policy to a Cluster]({{< baseurl >}}/rancher/v2.x/en/tasks/clusters/adding-a-pod-security-policy). +You can add a Pod Security Policy (PSPs hereafter) in the following contexts: + +- [When creating a cluster]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/editing-clusters/#adding-a-default-pod-security-policy) +- [When editing an existing cluster]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/editing-clusters/#adding-a-pod-security-policy) +- [When creating a project]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/projects-namespaces/creating-and-managing-projects/) +- [When editing an existing project]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/projects-namespaces/creating-and-managing-projects/#editing-the-pod-security-policy) + +> **Note:** We recommend adding PSPs during cluster and project creation instead of adding it to an existing one. + diff --git a/content/rancher/v2.x/en/catalog-and-charts/launching-catalog-apps/_index.md b/content/rancher/v2.x/en/catalog-and-charts/launching-catalog-apps/_index.md index 6d1645d43e7..4e90666473c 100644 --- a/content/rancher/v2.x/en/catalog-and-charts/launching-catalog-apps/_index.md +++ b/content/rancher/v2.x/en/catalog-and-charts/launching-catalog-apps/_index.md @@ -2,3 +2,32 @@ title: Launching Catalog Applications weight: 4010 --- + +After you've enabled default catalogs or setup a custom catalog, you can launch apps using a catalog instead of a standard deployment. + +>**Prerequisite:** Enable a catalog. For more information, see [Catalogs and Charts]({{< baseurl >}}/rancher/v2.x/en/concepts/catalogs). + +1. From the **Global** view, open the project that you want to deploy to. + +2. From the main menu, choose **Catalog Apps**. Then click **Launch**. + +3. Find the app that you want to launch, and then click **View Now**. + +4. Under **Configuration Options** enter a **Name**. By default, this name is also used to create a Kubernetes namespace for the application. + + * If you would like to change the **Namespace**, click **Customize** and enter a new name. + * If you want to use a different namespace that already exists, click **Customize**, and then click **Use an existing namespace**. Choose a namespace from the list. + +5. Select a **Template Version**. + +6. Complete the rest of the **Configuration Options**. + + * For native Helm charts (i.e., charts from the **Helm Stable** or **Helm Incubator** catalogs), answers are provided as key value pairs in the **Answers** section. + * Keys and values are available within **Detailed Descriptions**. + +7. Review the files in **Preview**. When you're satisfied, click **Launch**. + +**Result**: Your application is deployed to your chosen namespace. You can view the application status from the project's: + +- **Workloads** view +- **Catalog Apps** view diff --git a/content/rancher/v2.x/en/clusters/members/_index.md b/content/rancher/v2.x/en/clusters/cluster-members/_index.md similarity index 100% rename from content/rancher/v2.x/en/clusters/members/_index.md rename to content/rancher/v2.x/en/clusters/cluster-members/_index.md diff --git a/content/rancher/v2.x/en/clusters/rke-clusters/options/pod-security-policies/_index.md b/content/rancher/v2.x/en/clusters/rke-clusters/options/pod-security-policies/_index.md index 7919b19cce0..82e3da30dae 100644 --- a/content/rancher/v2.x/en/clusters/rke-clusters/options/pod-security-policies/_index.md +++ b/content/rancher/v2.x/en/clusters/rke-clusters/options/pod-security-policies/_index.md @@ -2,3 +2,97 @@ title: Pod Security Policies weight: 2260 --- + + +_Pod Security Policies_ are objects that control security-sensitive aspects of pod specification (like root privileges). + +You can add a Pod Security Policy (PSPs hereafter) in the following contexts: + +- [When creating a cluster](#cluster-creation--adding-a-default-pod-security-policy) +- [When editing an existing cluster]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/editing-clusters/#adding-a-pod-security-policy) +- [When creating a project](#project-creation--adding-a-pod-security-policy) +- [When editing an existing project](#existing-project--adding-a-pod-security-policy) + +> **Note:** We recommend adding PSPs during cluster and project creation instead of adding it to an existing one. + +For more information about PSPs, refer to [Pod Security Policy]({{< baseurl >}}/rancher/v2.x/en/admin-settings/pod-security-policies). + +## Cluster Creation: Adding a Default Pod Security Policy + +When you create a new cluster, you can configure it to apply a PSP immediately. As you create the cluster, use the **Cluster Options** to enable a PSP. The PSP assigned to the cluster will be the default PSP for projects within the cluster. + +>**Prerequisite:** +>Create a Pod Security Policy within Rancher. Before you can assign a default PSP to a new cluster, you must have a PSP available for assignment. For instruction, see [Creating Pod Security Policies]({{< baseurl >}}/rancher/v2.x/en/admin-settings/pod-security-policies/). +>**Note:** +>For security purposes, we recommend assigning a PSP as you create your clusters. + +To enable a default Pod Security Policy, set the **Pod Security Policy Support** option to **Enabled**, and then make a selection from the **Default Pod Security Policy** drop-down. + +When the cluster finishes provisioning, the PSP you selected is applied to all projects within the cluster. + +For detailed instruction about assigning a PSP to a new cluster, see [Creating a Cluster]({{< baseurl >}}/rancher/v2.x/en/tasks/clusters/creating-a-cluster/). + +## Existing Cluster: Adding a Pod Security Policy + +If you don't apply a PSP as you create your cluster, you can always add one later. + +>**Prerequisite:** +>Create a Pod Security Policy within Rancher. Before you can assign a default PSP to an existing cluster, you must have a PSP available for assignment. For instruction, see [Creating Pod Security Policies]({{< baseurl >}}/rancher/v2.x/en/admin-settings/pod-security-policies/). + +1. From the **Global** view, find the cluster that you want to apply your PSP to. Select **Vertical Ellipsis (...) > Edit** for the cluster you want to enable PSPs for. + +2. Expand the **Cluster Options** accordion. + +3. From **Pod Security Policy Support**, select **Enabled**. + + >**Note:** Not all cluster providers support PSPs, so this option may not be available. + + **Step Result:** The **Default Pod Security Policy** drop-down activates. + +4. From **Default Pod Security Policy**, select the PSP you want to apply to the cluster. + +5. Click **Save**. + +**Result:** The PSP is applied to the cluster and any projects within the cluster. + +>**Note:** Any workloads that are already running in a cluster or project before a PSP is assigned will not be checked if it complies with the PSP. Workloads would need to be cloned or upgraded to see if they pass the PSP. + +## Project Creation: Adding a Pod Security Policy + +When you create a new project, you can assign a PSP directly to the project. Assigning a PSP to a project will: + +- Override the cluster's default PSP. +- Apply the PSP to the project. +- Apply the PSP to any namespaces you add to the project later. + +>**Prerequisites:** +> +> - Create a Pod Security Policy within Rancher. Before you can assign a default PSP to a new project, you must have a PSP available for assignment. For instruction, see [Creating Pod Security Policies]({{< baseurl >}}/rancher/v2.x/en/admin-settings/pod-security-policies/). +> - Assign a default Pod Security Policy to the project's cluster. You can't assign a PSP to a project until one is already applied to the cluster. For more information, see [Existing Cluster: Adding a Pod Security Policy](#existing-cluster--adding-a-pod-security-policy). + +As you create the project, make a selection from the **Pod Security Policy** drop-down to assign a PSP. + + + +## Existing Project: Adding a Pod Security Policy + +You can always assign a PSP to an existing project if you didn't assign one during creation. + +>**Prerequisites:** +> +> - Create a Pod Security Policy within Rancher. Before you can assign a default PSP to an existing project, you must have a PSP available for assignment. For instruction, see [Creating Pod Security Policies]({{< baseurl >}}/rancher/v2.x/en/admin-settings/pod-security-policies/). +> - Assign a default Pod Security Policy to the project's cluster. You can't assign a PSP to a project until one is already applied to the cluster. For more information, see [Existing Cluster: Adding a Pod Security Policy](#existing-cluster--adding-a-pod-security-policy). + +1. From the **Global** view, find the cluster containing the project you want to apply a PSP to. + +1. From the main menu, select **Projects/Namespaces**. + +3. Find the project that you want to add a PSP to. From that project, select **Vertical Ellipsis (...) > Edit**. + +4. From the **Pod Security Policy** drop-down, select the PSP you want to apply to the project. + +5. Click **Save**. + +**Result:** The PSP is applied to the project and any namespaces added to the project. + +>**Note:** Any workloads that are already running in a cluster or project before a PSP is assigned will not be checked if it complies with the PSP. Workloads would need to be cloned or upgraded to see if they pass the PSP. diff --git a/content/rancher/v2.x/en/concepts/_index.md b/content/rancher/v2.x/en/concepts/_index.md deleted file mode 100644 index 1242f168e07..00000000000 --- a/content/rancher/v2.x/en/concepts/_index.md +++ /dev/null @@ -1,7 +0,0 @@ ---- - title: Concepts - weight: 2000 ---- -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! diff --git a/content/rancher/v2.x/en/concepts/resources/_index.md b/content/rancher/v2.x/en/concepts/resources/_index.md deleted file mode 100644 index 70411d7e264..00000000000 --- a/content/rancher/v2.x/en/concepts/resources/_index.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Resources -weight: 2275 ---- - -Within the context of a Rancher project or namespace, _resources_ are files and data that support operation of your pods. Within this scope, resources include: - -- [Certificates](#certificates) -- [ConfigMaps](#configmaps) -- [Secrets](#secrets) -- [Registries](#registries) - -Rancher extends the application of the Kubernetes namespace resources listed above to [projects]({{< baseurl >}}/rancher/v2.x/en/concepts/projects/), 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. - -Within Kubernetes, certificates, registries, and secrets are all considered [secrets](https://kubernetes.io/docs/concepts/configuration/secret/). Therefore, within a single project or namespace, these resources must have unique names to avoid conflicts. Although secrets are primarily used to carry sensitive information, they have other uses as well. Read on below. - -## Certificates - -When you create an ingress within Rancher/Kubernetes, you must provide it with a secret that includes a TLS private key and certificate, which are used to encrypt and decrypt communications that come through the ingress. You can make certificates available for ingress use by navigating to its project or namespace, and then uploading the certificate. You can then add the certificate to the ingress deployment. - -## ConfigMaps - -While most types of Kubernetes secrets store sensitive information, [ConfigMaps](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/) store general configuration information, such as a group of config files. Because ConfigMaps don't store sensitive information, they can be updated automatically, and therefore don't require their containers to be restarted following update (unlike most secret types, which require manual updates and a container restart to take effect). - -ConfigMaps accept key value pairs in common string formats, like config files or JSON blobs. After you upload a config map, any workload can reference it as either an environment variable or a volume mount. - ->**Note:** ConfigMaps are only available within namespaces and not projects. - -## Secrets - -[Secrets](https://kubernetes.io/docs/concepts/configuration/secret/#overview-of-secrets) store sensitive data like passwords, tokens, or keys. They may contain one or more key value pairs. -When configuring a workload, you'll be able to choose which secrets to include. Like config maps, secrets can be referenced by workloads as either an environment variable or a volume mount. - ->**Note:** Any update to secrets won't reflect automatically inside pods, until the pods are restarted. - -## Registries - -Registries are secrets containing credentials used to authenticate with [private registries](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/). Deployments use these secrets to authenticate with a private registry and then pull a Docker image hosted on it. - ->**Note:** Currently, credentials are pulled automatically only if the workload is created in the Rancher UI and not kubectl. - -## Related Links - -- [Adding SSL Certificates]({{< baseurl >}}/rancher/v2.x/en/tasks/projects/add-ssl-certificates) -- [Adding ConfigMaps]({{< baseurl >}}/rancher/v2.x/en/tasks/projects/add-configmaps) -- [Adding Secrets]({{< baseurl >}}/rancher/v2.x/en/tasks/projects/add-a-secret) -- [Adding Registries]({{< baseurl >}}/rancher/v2.x/en/tasks/projects/add-registries) diff --git a/content/rancher/v2.x/en/concepts/service-discovery/_index.md b/content/rancher/v2.x/en/concepts/service-discovery/_index.md deleted file mode 100644 index b3dff86b4b8..00000000000 --- a/content/rancher/v2.x/en/concepts/service-discovery/_index.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -title: Service Discovery -weight: 2200 -draft: true ---- - -## Related Links - -### Tutorials - -- [Adding a DNS Record]({{< baseurl >}}/rancher/v2.x/en/tasks/workloads/add-a-dns-record) - -### External Links - -- [Services](https://kubernetes.io/docs/concepts/services-networking/service/) -- [Adding entries to Pod /etc/hosts with HostAliases](https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/) diff --git a/content/rancher/v2.x/en/faq/technical/_index.md b/content/rancher/v2.x/en/faq/technical/_index.md index 3df6cd1abfc..75066217459 100644 --- a/content/rancher/v2.x/en/faq/technical/_index.md +++ b/content/rancher/v2.x/en/faq/technical/_index.md @@ -64,7 +64,7 @@ Node Templates can be accessed by opening your account menu (top right) and sele ### Why is my Layer-4 Load Balancer in `Pending` state? -The Layer-4 Load Balancer is created as `type: LoadBalancer`. In Kubernetes, this needs a cloud provider or controller that can satisfy these requests, otherwise these will be in `Pending` state forever. More information can be found on [Cloud Providers]({{< baseurl >}}/rancher/v2.x/en/concepts/clusters/cloud-providers/) or [Create External Load Balancer](https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/) +The Layer-4 Load Balancer is created as `type: LoadBalancer`. In Kubernetes, this needs a cloud provider or controller that can satisfy these requests, otherwise these will be in `Pending` state forever. More information can be found on [Cloud Providers]({{< baseurl >}}/rancher/v2.x/en/clusters/rke-clusters/options/cloud-providers/) or [Create External Load Balancer](https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/) ### Where is the state of Rancher stored? diff --git a/content/rancher/v2.x/en/kubernetes-in-rancher/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/_index.md new file mode 100644 index 00000000000..5ffa334dd0d --- /dev/null +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/_index.md @@ -0,0 +1,21 @@ +--- +title: Kubernetes in Rancher +weight: 3000 +aliases: + - /rancher/v2.x/en/concepts/ + - /rancher/v2.x/en/tasks/ + - /rancher/v2.x/en/concepts/resources/ +--- + + + +Within the context of a Rancher project or namespace, _resources_ are files and data that support operation of your pods. Within this scope, resources include: + +- [Certificates](#certificates) +- [ConfigMaps](#configmaps) +- [Secrets](#secrets) +- [Registries](#registries) + +Rancher extends the application of the Kubernetes namespace resources listed above to [projects]({{< baseurl >}}/rancher/v2.x/en/concepts/projects/), 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. + +Within Kubernetes, certificates, registries, and secrets are all considered [secrets](https://kubernetes.io/docs/concepts/configuration/secret/). Therefore, within a single project or namespace, these resources must have unique names to avoid conflicts. Although secrets are primarily used to carry sensitive information, they have other uses as well. diff --git a/content/rancher/v2.x/en/tasks/projects/add-ssl-certificates/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/certificates/_index.md similarity index 85% rename from content/rancher/v2.x/en/tasks/projects/add-ssl-certificates/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/certificates/_index.md index a9dfeaac88d..993e56f5799 100644 --- a/content/rancher/v2.x/en/tasks/projects/add-ssl-certificates/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/certificates/_index.md @@ -1,8 +1,11 @@ --- -title: Adding SSL Certificates -weight: +title: SSL Certificates +weight: 3060 +aliases: + - /rancher/v2.x/en/tasks/projects/add-ssl-certificate/ --- -When you create an ingress within Rancher/Kubernetes, you must provide it with a TLS private key and certificate, which are used to encrypt and decrypt communications that come through the ingress. You can make certificates available for ingress use by navigating to its project or namespace, and then uploading the certificate. + +When you create an ingress within Rancher/Kubernetes, you must provide it with a secret that includes a TLS private key and certificate, which are used to encrypt and decrypt communications that come through the ingress. You can make certificates available for ingress use by navigating to its project or namespace, and then uploading the certificate. You can then add the certificate to the ingress deployment. Add SSL certificates to either projects, namespaces, or both. A project scoped certificate will be available in all its namespaces. diff --git a/content/rancher/v2.x/en/tasks/projects/add-configmaps/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/configmaps/_index.md similarity index 72% rename from content/rancher/v2.x/en/tasks/projects/add-configmaps/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/configmaps/_index.md index 87476fd20c7..ba7049d6da7 100644 --- a/content/rancher/v2.x/en/tasks/projects/add-configmaps/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/configmaps/_index.md @@ -1,8 +1,17 @@ --- -title: Adding ConfigMaps -weight: +title: ConfigMaps +weight: 3061 +aliases: + - /rancher/v2.x/en/tasks/projects/add-configmaps --- + +While most types of Kubernetes secrets store sensitive information, [ConfigMaps](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/) store general configuration information, such as a group of config files. Because ConfigMaps don't store sensitive information, they can be updated automatically, and therefore don't require their containers to be restarted following update (unlike most secret types, which require manual updates and a container restart to take effect). + +ConfigMaps accept key value pairs in common string formats, like config files or JSON blobs. After you upload a config map, any workload can reference it as either an environment variable or a volume mount. + +>**Note:** ConfigMaps are only available within namespaces and not projects. + ConfigMaps store general configuration information for an application, such as configuration files, command-line arguments, environment variables, etc. ConfigMaps accept key value pairs in common string formats, like config files or JSON blobs. Add ConfigMaps to your Rancher workspaces so that you can add them to your workloads later. For more information on ConfigMaps, see the official [Kubernetes Documentation: Using ConfigMap](https://kubernetes-v1-4.github.io/docs/user-guide/configmap/). >**Note:** ConfigMaps can only be applied to namespaces and not projects. @@ -36,4 +45,4 @@ Now that you have a ConfigMap added to a namespace, you can add it to a workload - Application environment variables. - Specifying parameters for a Volume mounted to the workload. -For more information on adding ConfigMaps to a workload, see [Deploying Workloads]({{< baseurl >}}/rancher/v2.x/en/tasks/workloads/deploy-workloads/). \ No newline at end of file +For more information on adding ConfigMaps to a workload, see [Deploying Workloads]({{< baseurl >}}/rancher/v2.x/en/tasks/workloads/deploy-workloads/). diff --git a/content/rancher/v2.x/en/kubernetes-in-rancher/editing-clusters/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/editing-clusters/_index.md new file mode 100644 index 00000000000..743aa72305f --- /dev/null +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/editing-clusters/_index.md @@ -0,0 +1,33 @@ +--- +title: Editing Clusters +weight: 3015 +draft: true +--- + +## Increasing Number of nodes + + +## Adding a Pod Security Policy + +If you don't apply a PSP as you create your cluster, you can always add one later. + +>**Prerequisite:** +>Create a Pod Security Policy within Rancher. Before you can assign a default PSP to an existing cluster, you must have a PSP available for assignment. For instruction, see [Creating Pod Security Policies]({{< baseurl >}}/rancher/v2.x/en/admin-settings/pod-security-policies/). + +1. From the **Global** view, find the cluster that you want to apply your PSP to. Select **Vertical Ellipsis (...) > Edit** for the cluster you want to enable PSPs for. + +2. Expand the **Cluster Options** accordion. + +3. From **Pod Security Policy Support**, select **Enabled**. + + >**Note:** Not all cluster providers support PSPs, so this option may not be available. + + **Step Result:** The **Default Pod Security Policy** drop-down activates. + +4. From **Default Pod Security Policy**, select the PSP you want to apply to the cluster. + +5. Click **Save**. + +**Result:** The PSP is applied to the cluster and any projects within the cluster. + +>**Note:** Any workloads that are already running in a cluster or project before a PSP is assigned will not be checked if it complies with the PSP. Workloads would need to be cloned or upgraded to see if they pass the PSP. diff --git a/content/rancher/v2.x/en/concepts/clusters/kubeconfig-files/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/kubeconfig/_index.md similarity index 87% rename from content/rancher/v2.x/en/concepts/clusters/kubeconfig-files/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/kubeconfig/_index.md index c13ebb3e2e6..d66f8f8b174 100644 --- a/content/rancher/v2.x/en/concepts/clusters/kubeconfig-files/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/kubeconfig/_index.md @@ -1,6 +1,8 @@ --- title: Kubeconfig Files -weight: 2100 +weight: 3010 +aliases: + - /rancher/v2.x/en/concepts/clusters/kubeconfig-files/ --- A _kubeconfig file_ is a file used to configure access to Kubernetes when used in conjunction with the kubectl commandline tool (or other clients). @@ -11,11 +13,9 @@ When you create a cluster using the Rancher GUI, Rancher automatically creates a This kubeconfig file and its contents are specific to the cluster you are viewing. You will need a separate kubeconfig file for each cluster that you have access to in Rancher. -For more information, see [Using kubectl to Access a Cluster]({{< baseurl >}}/rancher/v2.x/en/tasks/clusters/using-kubectl-to-access-a-cluster). +For more information, see [Using kubectl to Access a Cluster]({{< baseurl >}}/rancher/v2.x/en//kubernetes-in-rancher/kubectl). >**Note:** By default, kubectl checks `~/.kube/config` for kubeconfig files, but you can use any directory you want using the `--kubeconfig` flag. For example: >``` kubectl --kubeconfig /custom/path/kube.config get pods ``` - - diff --git a/content/rancher/v2.x/en/tasks/clusters/using-kubectl-to-access-a-cluster/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/kubectl/_index.md similarity index 92% rename from content/rancher/v2.x/en/tasks/clusters/using-kubectl-to-access-a-cluster/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/kubectl/_index.md index cb9930f726e..93b13e310d4 100644 --- a/content/rancher/v2.x/en/tasks/clusters/using-kubectl-to-access-a-cluster/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/kubectl/_index.md @@ -1,6 +1,8 @@ --- title: Using kubectl to Access a Cluster -weight: 3450 +weight: 3005 +aliases: + - /rancher/v2.x/en/tasks/clusters/using-kubectl-to-access-a-cluster/ --- You can access and manage your Kubernetes clusters using kubectl in two ways: @@ -12,7 +14,7 @@ You can access and manage your Kubernetes clusters using kubectl in two ways: You can access and manage your clusters by logging into Rancher and opening the kubectl shell. No further configuration necessary. 1. From the **Global** view, open the cluster that you want to access with kubectl. - + 2. Click **Launch kubectl**. Use the window that opens to interact with your Kubernetes cluster. For more information on using kubectl, see [Kubernetes Documentation: Overview of kubectl](https://kubernetes.io/docs/reference/kubectl/overview/). @@ -26,7 +28,7 @@ Alternatively, you can access your clusters by installing kubectl on your workst 2. Log into Rancher. From the **Global** view, open the cluster that you want to access with kubectl. -3. Copy the cluster's kubeconfig file to your workstation. +3. Copy the cluster's kubeconfig file to your workstation. 1. Click **Kubeconfig File**. @@ -41,4 +43,4 @@ Alternatively, you can access your clusters by installing kubectl on your workst ``` 4. From your workstation, launch kubectl. Use it to interact with your kubernetes cluster. - For more information on using kubectl, see [Kubernetes Documentation: Overview of kubectl](https://kubernetes.io/docs/reference/kubectl/overview/). \ No newline at end of file + For more information on using kubectl, see [Kubernetes Documentation: Overview of kubectl](https://kubernetes.io/docs/reference/kubectl/overview/). diff --git a/content/rancher/v2.x/en/kubernetes-in-rancher/load-balancing-and-ingress/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/load-balancing-and-ingress/_index.md new file mode 100644 index 00000000000..bfc50aec574 --- /dev/null +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/load-balancing-and-ingress/_index.md @@ -0,0 +1,4 @@ +--- +title: Load Balancing and Ingresses +weight: 3040 +--- diff --git a/content/rancher/v2.x/en/tasks/workloads/add-ingress/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/load-balancing-and-ingress/ingress/_index.md similarity index 97% rename from content/rancher/v2.x/en/tasks/workloads/add-ingress/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/load-balancing-and-ingress/ingress/_index.md index a527ae01887..61e7ebda9dc 100644 --- a/content/rancher/v2.x/en/tasks/workloads/add-ingress/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/load-balancing-and-ingress/ingress/_index.md @@ -1,6 +1,6 @@ --- -title: Adding Ingress -weight: 50 +title: Ingress +weight: 3042 --- Ingress can be added for workloads to provide load balancing, SSL termination and host/path based routing. @@ -16,13 +16,13 @@ Ingress can be added for workloads to provide load balancing, SSL termination an 1. Create ingress forwarding **Rules**. - **Automatically generate a xip.io hostname** - + If you choose this option, ingress routes requests to hostname to a DNS name that's automatically generated. Rancher uses [xip.io](http://xip.io/) to automatically generates the DNS name. This option is best used for testing, _not_ production environments. >**Note:** To use this option, you must be able to resolve to `xip.io` addresses. - + 1. Add a **Target Backend**. By default, a workload is added to the ingress, but you can add more targets by clicking either **Service** or **Workload**. - + 1. **Optional:** If you want specify a workload or service when a request is sent to a particular hostname path, add a **Path** for the target. For example, if you want requests for `www.mysite.com/contact-us` to be sent to a different service than `www.mysite.com`, enter `/contact-us` in the **Path** field. Typically, the first rule that you create does not include a path. @@ -32,13 +32,13 @@ Ingress can be added for workloads to provide load balancing, SSL termination an 1. Enter the **Port** number that each target operates on. - **Specify a hostname to use** - + If you use this option, ingress routes requests for a hostname to the service or workload that you specify. 1. Enter the hostname that your ingress will handle request forwarding for. For example, `www.mysite.com`. - + 1. Add a **Target Backend**. By default, a workload is added to the ingress, but you can add more targets by clicking either **Service** or **Workload**. - + 1. **Optional:** If you want specify a workload or service when a request is sent to a particular hostname path, add a **Path** for the target. For example, if you want requests for `www.mysite.com/contact-us` to be sent to a different service than `www.mysite.com`, enter `/contact-us` in the **Path** field. Typically, the first rule that you create does not include a path. @@ -46,16 +46,16 @@ Ingress can be added for workloads to provide load balancing, SSL termination an 1. Select a workload or service from the **Target** drop-down list for each target you've added. 1. Enter the **Port** number that each target operates on. - + - **Use as the default backend** - + Use this option to set an ingress rule for handling requests that don't match any other ingress rules. For example, use this option to route requests that can't be found to a `404` page. >**Note:** If you deployed Rancher using RKE, a default backend for 404s and 202s is already configured. - + 1. Add a **Target Backend**. Click either **Service** or **Workload** to add the target. - + 1. Select a service or workload from the **Target** drop-down list. 1. **Optional:** click **Add Rule** to create additional ingress rules. For example, after you create ingress rules to direct requests for your hostname, you'll likely want to create a default backend to handle 404s. diff --git a/content/rancher/v2.x/en/concepts/load-balancing/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/load-balancing-and-ingress/load-balancing/_index.md similarity index 97% rename from content/rancher/v2.x/en/concepts/load-balancing/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/load-balancing-and-ingress/load-balancing/_index.md index f78cdbb88b0..d994204605e 100644 --- a/content/rancher/v2.x/en/concepts/load-balancing/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/load-balancing-and-ingress/load-balancing/_index.md @@ -1,6 +1,8 @@ --- -title: Load Balancing -weight: 2175 +title: Load Balancing and Ingresses +weight: 3041 +aliases: + - /rancher/v2.x/en/concepts/load-balancing/ --- Kubernetes supports load balancing in two ways: Layer-4 Load Balancing and Layer-7 Load Balancing. diff --git a/content/rancher/v2.x/en/concepts/projects/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/projects-namespaces/_index.md similarity index 86% rename from content/rancher/v2.x/en/concepts/projects/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/projects-namespaces/_index.md index d4704f3bfb0..27daae932fd 100644 --- a/content/rancher/v2.x/en/concepts/projects/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/projects-namespaces/_index.md @@ -1,8 +1,13 @@ --- -title: Projects -weight: 2150 +title: Projects and Namespaces +weight: 3020 +aliases: + - /rancher/v2.x/en/concepts/projects/ --- +_Projects_ are a new feature in Rancher that allows you to group namespaces. Users can be added as members to the project, and the project owner can assign roles to each member to control their project access. + + _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/creating-roles/#adding-a-custom-role). 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 @@ -21,7 +26,3 @@ Rancher extends Kubernetes to allow the application of [Pod Security Policies](h Kubernetes resources belong to specific namespaces. Rancher 2.0 relies on namespaces to isolate resources among users and apps. When the user deploys an app from the catalog, for example, he can choose to deploy that app into its own namespace, so that resource names in one app will not conflict with resource names in another. Namespaces must be globally unique. It is often difficult for users to pick unique namespace names. Rancher therefore encourages the pattern where users work with projects, and the system generates unique namespace names automatically. For more information, see the [Kubernetes Namespaces Documentation](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/). - -## Related Links - -- [Project Tutorials]({{< baseurl >}}/rancher/v2.x/en/tasks/projects) diff --git a/content/rancher/v2.x/en/kubernetes-in-rancher/projects-namespaces/creating-and-managing-projects/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/projects-namespaces/creating-and-managing-projects/_index.md new file mode 100644 index 00000000000..22a7531e685 --- /dev/null +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/projects-namespaces/creating-and-managing-projects/_index.md @@ -0,0 +1,89 @@ +--- +title: Creating and Managing Projects +weight: 3021 +aliases: + - /rancher/v2.x/en/tasks/projects/create-project/ +--- + + +1. From the **Global** view, choose **Clusters** from the main menu. From the **Clusters** page, open the cluster from which you want to create a project. + +1. From the main menu, choose **Projects/Namespaces**. Then click **Add Project**. + +1. Enter a **Project Name**. + +1. **Optional:** Select a **Pod Security Policy**. + + [What are Pod Security Policies?]({{< baseurl >}}/rancher/v2.x/en/admin-settings/pod-security-policies) + + >**Note:** This option is only available if you've already created a Pod Security Policy. For instruction, see [Creating Pod Security Policies]({{< baseurl >}}/rancher/v2.x/en/admin-settings/pod-security-policies/#creating-pod-security-policies). + +1. **Recommended:** Add project members. + + Use the **Members** accordion to provide other users with project access and roles. + + By default, your user is added as the project `Owner`. + + 1. Click **Add Member**. + + 1. From the **Name** combo box, search for a user or group that you want to assign project access. + + >**Note:** You can only search for groups if external authentication is enabled. + + 1. From the **Role** drop-down, choose a role. + + [What are Roles?]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/#cluster-and-project-roles) + + >**Tip:** Choose Custom to create a custom role on the fly: [Custom Project Roles]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/#custom-project-roles). + + 1. To add more members, repeat substeps a—c. + + +1. Click **Create**. + +**Result:** Your project is created. You can view it from the cluster's **Projects/Namespaces** view. + +## Switching projects + +To switch between clusters, use the **Global** drop-down available in the main menu. + +![Global Menu]({{< baseurl >}}/img/rancher/global-menu.png) + +Alternatively, you can switch between projects and clusters using the main menu. + +- To switch between clusters, open the **Global** view and select **Clusters** from the main menu. Then open a cluster. +- To switch between projects, open a cluster, and then select **Projects/Namespaces** from the main menu. Select the link for the project that you want to open. + + +## Editing the Pod Security Policy + +You can always assign a PSP to an existing project if you didn't assign one during creation. + +>**Prerequisites:** +> +> - Create a Pod Security Policy within Rancher. Before you can assign a default PSP to an existing project, you must have a PSP available for assignment. For instruction, see [Creating Pod Security Policies]({{< baseurl >}}/rancher/v2.x/en/admin-settings/pod-security-policies/). +> - Assign a default Pod Security Policy to the project's cluster. You can't assign a PSP to a project until one is already applied to the cluster. For more information, see [Existing Cluster: Adding a Pod Security Policy](#existing-cluster--adding-a-pod-security-policy). + +1. From the **Global** view, find the cluster containing the project you want to apply a PSP to. + +1. From the main menu, select **Projects/Namespaces**. + +3. Find the project that you want to add a PSP to. From that project, select **Vertical Ellipsis (...) > Edit**. + +4. From the **Pod Security Policy** drop-down, select the PSP you want to apply to the project. + Assigning a PSP to a project will: + + - Override the cluster's default PSP. + - Apply the PSP to the project. + - Apply the PSP to any namespaces you add to the project later. + + >**Prerequisites:** + > + > - Create a Pod Security Policy within Rancher. Before you can assign a default PSP to a new project, you must have a PSP available for assignment. For instruction, see [Creating Pod Security Policies]({{< baseurl >}}/rancher/v2.x/en/admin-settings/pod-security-policies/). + > - Assign a default Pod Security Policy to the project's cluster. You can't assign a PSP to a project until one is already applied to the cluster. + +5. Click **Save**. + +**Result:** The PSP is applied to the project and any namespaces added to the project. + +>**Note:** Any workloads that are already running in a cluster or project before a PSP is assigned will not be checked if it complies with the PSP. Workloads would need to be cloned or upgraded to see if they pass the PSP. diff --git a/content/rancher/v2.x/en/tasks/projects/add-project-members/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/projects-namespaces/project-members/_index.md similarity index 90% rename from content/rancher/v2.x/en/tasks/projects/add-project-members/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/projects-namespaces/project-members/_index.md index 04046b75e43..940e4e2e551 100644 --- a/content/rancher/v2.x/en/tasks/projects/add-project-members/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/projects-namespaces/project-members/_index.md @@ -1,15 +1,17 @@ --- -title: Adding Project Members -weight: +title: Adding and Managing Project Members +weight: 3022 +aliases: + - /rancher/v2.x/en/tasks/projects/add-project-members/ --- If you want to provide a user with access and permissions to _specific_ projects and resources within a cluster, assign the user a project membership. ->**Tip:** Want to provide a user with access to _all_ projects within a cluster? See [Adding Cluster Members]({{< baseurl >}}/rancher/v2.x/en/clusters/adding-users) instead. +>**Tip:** Want to provide a user with access to _all_ projects within a cluster? See [Adding Cluster Members]({{< baseurl >}}/rancher/v2.x/en/clusters/cluster-members/) instead. There are two contexts where you can add project members: -- [Adding Members to a New Project]({{< baseurl >}}/rancher/v2.x/en/tasks/projects/create-project) +- [Adding Members to a New Project]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/projects-namespaces/project-members/) You can add members to a project as you create it (recommended if possible). diff --git a/content/rancher/v2.x/en/tasks/projects/add-registries/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/registries/_index.md similarity index 77% rename from content/rancher/v2.x/en/tasks/projects/add-registries/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/registries/_index.md index ab5a9f56bde..bd60189f703 100644 --- a/content/rancher/v2.x/en/tasks/projects/add-registries/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/registries/_index.md @@ -1,10 +1,16 @@ --- -title: Adding Registries -weight: +title: Registries +weight: 3063 +aliases: + - /rancher/v2.x/en/tasks/projects/add-registries/ --- Registries are secrets containing credentials used to authenticate with [private registries](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/). Deployments use these secrets to authenticate with a private registry and then pull a Docker image hosted on it. +>**Note:** Currently, credentials are pulled automatically only if the workload is created in the Rancher UI and not kubectl. + +Registries are secrets containing credentials used to authenticate with [private registries](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/). Deployments use these secrets to authenticate with a private registry and then pull a Docker image hosted on it. + >**Prerequisites:** You must have a [private registry](https://docs.docker.com/registry/deploying/) configured. >**Note:** Currently, credentials are pulled automatically only if the workload is created in the Rancher UI and not kubectl. @@ -22,7 +28,7 @@ Registries are secrets containing credentials used to authenticate with [private 1. Select the website that hosts your private registry. Then enter credentials that authenticate with the registry. 1. Click **Save**. - + **Result:** Your secret is added to the project or namespace, depending on the scope you chose. You can view the secret in the Rancher UI from the **Resources > Registries** view. ## What's Next? diff --git a/content/rancher/v2.x/en/tasks/projects/add-a-secret/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/secrets/_index.md similarity index 74% rename from content/rancher/v2.x/en/tasks/projects/add-a-secret/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/secrets/_index.md index c95c8ccb660..aadd08f68ac 100644 --- a/content/rancher/v2.x/en/tasks/projects/add-a-secret/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/secrets/_index.md @@ -1,8 +1,15 @@ --- -title: Adding a Secret -weight: +title: Secrets +weight: 3062 +aliases: + - /rancher/v2.x/en/tasks/projects/add-a-secret --- +[Secrets](https://kubernetes.io/docs/concepts/configuration/secret/#overview-of-secrets) store sensitive data like passwords, tokens, or keys. They may contain one or more key value pairs. +When configuring a workload, you'll be able to choose which secrets to include. Like config maps, secrets can be referenced by workloads as either an environment variable or a volume mount. + +>**Note:** Any update to secrets won't reflect automatically inside pods, until the pods are restarted. + [Secrets](https://kubernetes.io/docs/concepts/configuration/secret/#overview-of-secrets) store sensitive data like passwords, tokens, or keys. They may contain one or more key value pairs. When creating a secret, you can make it available for any deployment within a project, or you can limit it to a single namespace. @@ -24,7 +31,7 @@ When creating a secret, you can make it available for any deployment within a pr > ![Bulk Key Value Pair Copy/Paste]({{< baseurl >}}/img/rancher/bulk-key-values.gif) 1. Click **Save**. - + **Result:** Your secret is added to the project or namespace, depending on the scope you chose. You can view the secret in the Rancher UI from the **Resources > Secrets** view. ## What's Next? diff --git a/content/rancher/v2.x/en/tasks/workloads/add-a-dns-record/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/service-discovery/_index.md similarity index 94% rename from content/rancher/v2.x/en/tasks/workloads/add-a-dns-record/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/service-discovery/_index.md index aaba2afdc6f..6bc3693feb0 100644 --- a/content/rancher/v2.x/en/tasks/workloads/add-a-dns-record/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/service-discovery/_index.md @@ -1,8 +1,11 @@ --- -title: Adding a DNS Record -weight: 75 +title: Service Discovery +weight: 3045 +aliases: + - /rancher/v2.x/en/tasks/workloads/add-a-dns-record/ --- + For every workload created, a complementing Service Discovery entry is created. This Service Discovery entry enables DNS resolution for the workload's pods using the following naming convention: `..svc.cluster.local`. @@ -47,10 +50,6 @@ However, you also have the option of creating additional Service Discovery recor ## Related Links -### Tutorials - -- [Service Discovery]({{< baseurl >}}/rancher/v2.x/en/concepts/service-discovery) - ### External Links - [Adding entries to Pod /etc/hosts with HostAliases](https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/) diff --git a/content/rancher/v2.x/en/concepts/volumes-and-storage/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/volumes-and-storage/_index.md similarity index 97% rename from content/rancher/v2.x/en/concepts/volumes-and-storage/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/volumes-and-storage/_index.md index a7cb44d3c05..e92694c5e1c 100644 --- a/content/rancher/v2.x/en/concepts/volumes-and-storage/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/volumes-and-storage/_index.md @@ -1,6 +1,8 @@ --- title: Volumes and Storage -weight: 2225 +weight: 3050 +aliases: + - /rancher/v2.x/en/concepts/volumes-and-storage/ --- There are two ways to create volumes on Kubernetes: Persistent Volumes (PVs) and Storage Classes. diff --git a/content/rancher/v2.x/en/tasks/clusters/adding-storage/provisioning-storage/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/volumes-and-storage/examples/_index.md similarity index 77% rename from content/rancher/v2.x/en/tasks/clusters/adding-storage/provisioning-storage/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/volumes-and-storage/examples/_index.md index e29fc390d43..26c4f07257a 100644 --- a/content/rancher/v2.x/en/tasks/clusters/adding-storage/provisioning-storage/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/volumes-and-storage/examples/_index.md @@ -1,6 +1,8 @@ --- -title: Provisioning Storage -weight: 3500 +title: Provisioning Storage Examples +weight: 3053 +aliases: + - /rancher/v2.x/en/tasks/clusters/adding-storage/provisioning-storage/ --- Rancher supports persistent storage with a variety of volume plugins. However, before you use any of these plugins to bind persistent storage to your workloads, you have to configure the storage itself, whether its a cloud-based solution from a service-provider or an on-prem solution that you manage yourself. diff --git a/content/rancher/v2.x/en/tasks/clusters/adding-storage/provisioning-storage/nfs/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/volumes-and-storage/examples/nfs/_index.md similarity index 96% rename from content/rancher/v2.x/en/tasks/clusters/adding-storage/provisioning-storage/nfs/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/volumes-and-storage/examples/nfs/_index.md index ec4a49d4cf1..5ec977c7b74 100644 --- a/content/rancher/v2.x/en/tasks/clusters/adding-storage/provisioning-storage/nfs/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/volumes-and-storage/examples/nfs/_index.md @@ -1,6 +1,8 @@ --- title: Provisioning NFS Storage -weight: 3500 +weight: 3054 +aliases: + - /rancher/v2.x/en/tasks/clusters/adding-storage/provisioning-storage/nfs/ --- Before you can use the NFS storage volume plug-in with Rancher deployments, you need to provision an NFS server. diff --git a/content/rancher/v2.x/en/tasks/workloads/add-persistent-volume-claim/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/volumes-and-storage/persistent-volume-claim/_index.md similarity index 95% rename from content/rancher/v2.x/en/tasks/workloads/add-persistent-volume-claim/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/volumes-and-storage/persistent-volume-claim/_index.md index 93ef3081f8b..709e9504ddd 100644 --- a/content/rancher/v2.x/en/tasks/workloads/add-persistent-volume-claim/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/volumes-and-storage/persistent-volume-claim/_index.md @@ -1,6 +1,8 @@ --- -title: Adding a Persistent Volume Claim -weight: 100 +title: Persistent Volume Claims +weight: 3052 +aliases: + - /rancher/v2.x/en/tasks/workloads/add-persistent-volume-claim --- _Persistent Volume Claims_ (or PVCs) are objects that request storage resources from your cluster. They're similar to a voucher that your deployment can redeem for storage access. When you create a deployment, you should usually attach a PVC so that your application can lay claim to persistent storage. This claim lets your deployment application store its data in an external location, so that if one of the application's containers fails, it can be replaced with a new container and continue accessing its data stored externally, as though an outage never occured. @@ -39,4 +41,3 @@ _Persistent Volume Claims_ (or PVCs) are objects that request storage resources 7. **Optional:** From **Customize**, select the [Access Modes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes) that you want to use. **Result:** Your PVC is created. You can now attach it to any workload in the project. - diff --git a/content/rancher/v2.x/en/tasks/clusters/adding-storage/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/volumes-and-storage/persistent-volumes-and-storage-classes/_index.md similarity index 96% rename from content/rancher/v2.x/en/tasks/clusters/adding-storage/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/volumes-and-storage/persistent-volumes-and-storage-classes/_index.md index f3c86dbaedf..cfe86c940ce 100644 --- a/content/rancher/v2.x/en/tasks/clusters/adding-storage/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/volumes-and-storage/persistent-volumes-and-storage-classes/_index.md @@ -1,9 +1,11 @@ --- -title: Adding Storage -weight: 3500 +title: Persistent Volumes and Storage Classes +weight: 3051 +aliases: + - /rancher/v2.x/en/tasks/clusters/adding-storage/ --- ->**Prerequisites:** +>**Prerequisites:** > >- Working with storage requires the `Manage Volumes` [role]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/#project-role-reference). >- You must have a storage medium provisioned. For more information, see [Provisioning Storage](provisioning-storage). @@ -30,7 +32,7 @@ Persistent volumes can either be a disk or file system that you host on premise, 1. Select the **Volume Plugin** for the disk type or service that you're using. >**Note:** If the cluster you are adding storage for is a cloud service that also offers cloud storage, you must enable the `cloud provider` option for the cluster, and you must use the service's plug-in to use cloud storage. For example, if you have a Amazon EC2 cluster and you want to use cloud storage for it: - + 1. You must enable the `cloud provider` option for the EC2 cluster. 2. You must use the `Amazon EBS Disk` volume plugin. @@ -60,7 +62,7 @@ Persistent volumes can either be a disk or file system that you host on premise, ## Adding Storage Classes -_Storage Classes_ allow you to dynamically provision persistent volumes on demand. Think of storage classes as storage profiles that are created automatically upon a request (which is known as a _persistent volume claim_). +_Storage Classes_ allow you to dynamically provision persistent volumes on demand. Think of storage classes as storage profiles that are created automatically upon a request (which is known as a _persistent volume claim_). 1. From the **Global** view, open the cluster for which you want to dynamically provision persistent storage volumes. @@ -71,7 +73,7 @@ _Storage Classes_ allow you to dynamically provision persistent volumes on deman 1. From the `Provisioner` drop-down, select the service that you want to use to dynamically provision storage volumes. >**Note:** If the cluster you are adding a storage class for is a cloud service that also offers cloud storage, you must enable the `cloud provider` option for the cluster, and you must use the service's plug-in to use cloud storage. For example, if you have a Amazon EC2 cluster and you want to use cloud storage for it: - + 1. You must enable the `cloud provider` option for the EC2 cluster. 2. You must use the `Amazon EBS Disk` provisioner. @@ -87,4 +89,4 @@ Mount Persistent Volumes to workloads so that your applications can store their You can mount Persistent Volumes in one of two contexts: - During deployment of a workload (recommended if possible). For more information, see [Deploying Workloads](../../workloads/deploy-workloads/). -- Following workload creation. For more information, see [Adding Persistent Volume Claims](../../workloads/add-persistent-volume-claim/). \ No newline at end of file +- Following workload creation. For more information, see [Adding Persistent Volume Claims](../../workloads/add-persistent-volume-claim/). diff --git a/content/rancher/v2.x/en/concepts/workloads/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/_index.md similarity index 89% rename from content/rancher/v2.x/en/concepts/workloads/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/workloads/_index.md index 7dfb09147a7..c4ad6632002 100644 --- a/content/rancher/v2.x/en/concepts/workloads/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/_index.md @@ -1,7 +1,11 @@ --- title: Workloads -weight: 2175 +weight: 3025 +aliases: + - /rancher/v2.x/en/concepts/workloads/ + - /rancher/v2.x/en/tasks/workloads/ --- + You can build any complex containerized application in Kubernetes using two basic constructs: pods and workloads. Once you build an application, you can expose it for access either within the same cluster or on the Internet using a third construct: services. ### Pods @@ -43,7 +47,7 @@ In many use cases, a workload has to be either: - Accessed by other workloads in the cluster. - Exposed to the outside world. - + You can achieve these goals by creating a _Service_. Services are mapped to the underlying workload's pods using a [selector/label approach (view the code samples)](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#service-and-replicationcontroller). Rancher UI simplifies this mapping process by automatically creating a service along with the workload, using the service port and type that you select. #### Service Types @@ -62,12 +66,16 @@ There are several types of services available in Rancher. The descriptions below >Exposes the service externally using a cloud provider’s load balancer. `NodePort` and `ClusterIP` services, to which the external load balancer will route, are automatically created. +## Workload Options + +This section of the documentation contains instructions for deploying workloads and using workload options. + + - [Deploy Workloads]({{< baseurl >}}/rancher/v2.x/en/tasks/workloads/deploy-workloads/) + - [Upgrade Workloads]({{< baseurl >}}/rancher/v2.x/en/tasks/workloads/upgrade-workloads/) + - [Rollback Workloads]({{< baseurl >}}/rancher/v2.x/en/tasks/workloads/rollback-workloads/) + ## Related Links ### External Links - [Services](https://kubernetes.io/docs/concepts/services-networking/service/) - -### Tutorials - -- [Workloads]({{< baseurl >}}/rancher/v2.x/en/tasks/workloads/) diff --git a/content/rancher/v2.x/en/tasks/workloads/add-a-sidecar/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/add-a-sidecar/_index.md similarity index 95% rename from content/rancher/v2.x/en/tasks/workloads/add-a-sidecar/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/workloads/add-a-sidecar/_index.md index a044732e71f..9ff53474a61 100644 --- a/content/rancher/v2.x/en/tasks/workloads/add-a-sidecar/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/add-a-sidecar/_index.md @@ -1,6 +1,8 @@ --- title: Adding a Sidecar -weight: 200 +weight: 3029 +aliases: + - /rancher/v2.x/en/concepts/workloads/add-a-sidecar/ --- A _sidecar_ is a container that extends or enhances the main container in a pod. The main container and the sidecar share a pod, and therefore share the same network space and storage. You can add sidecars to existing workloads by using the **Add a Sidecar** option. @@ -15,11 +17,11 @@ A _sidecar_ is a container that extends or enhances the main container in a pod. 1. Select a **Sidecar Type**. This option determines if the sidecar container is deployed before or after the main container is deployed. - **Standard Container:** - + The sidecar container is deployed after the main container. - **Init Container:** - + The sidecar container is deployed before the main container. 1. From the **Docker Image** field, enter the name of the Docker image that you want to deploy in support of the main container. During deployment, Rancher pulls this image from [Docker Hub](https://hub.docker.com/explore/). Enter the name exactly as it appears on Docker Hub. diff --git a/content/rancher/v2.x/en/tasks/workloads/deploy-workloads/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/deploy-workloads/_index.md similarity index 97% rename from content/rancher/v2.x/en/tasks/workloads/deploy-workloads/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/workloads/deploy-workloads/_index.md index dd628ed2a90..0f799a9a42d 100644 --- a/content/rancher/v2.x/en/tasks/workloads/deploy-workloads/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/deploy-workloads/_index.md @@ -1,6 +1,8 @@ --- title: Deploying Workloads -weight: 25 +weight: 3026 +aliases: + - /rancher/v2.x/en/concepts/workloads/deploy-workloads/ --- Deploy a workload to run an application in one or more containers. diff --git a/content/rancher/v2.x/en/tasks/workloads/rollback-workloads/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/rollback-workloads/_index.md similarity index 87% rename from content/rancher/v2.x/en/tasks/workloads/rollback-workloads/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/workloads/rollback-workloads/_index.md index 0c83bdb1993..431711c16f8 100644 --- a/content/rancher/v2.x/en/tasks/workloads/rollback-workloads/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/rollback-workloads/_index.md @@ -1,6 +1,8 @@ --- title: Rolling Back Workloads -weight: 150 +weight: 3027 +aliases: + - /rancher/v2.x/en/concepts/workloads/rollback-workloads/ --- Sometimes there is a need to rollback to the previous version of the application, either for debugging purposes or because an upgrade did not go as planned. diff --git a/content/rancher/v2.x/en/tasks/workloads/upgrade-workloads/_index.md b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/upgrade-workloads/_index.md similarity index 92% rename from content/rancher/v2.x/en/tasks/workloads/upgrade-workloads/_index.md rename to content/rancher/v2.x/en/kubernetes-in-rancher/workloads/upgrade-workloads/_index.md index 0a7882d990f..ef46dfc6bb1 100644 --- a/content/rancher/v2.x/en/tasks/workloads/upgrade-workloads/_index.md +++ b/content/rancher/v2.x/en/kubernetes-in-rancher/workloads/upgrade-workloads/_index.md @@ -1,6 +1,8 @@ --- title: Upgrading Workloads -weight: 125 +weight: 3028 +aliases: + - /rancher/v2.x/en/concepts/workloads/upgrade-workloads/ --- When a new version of an application image is released on Docker Hub, you can upgrade any workloads running a previous version of the application to the new one. diff --git a/content/rancher/v2.x/en/tasks/_index.md b/content/rancher/v2.x/en/tasks/_index.md deleted file mode 100644 index ae1250144c6..00000000000 --- a/content/rancher/v2.x/en/tasks/_index.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -title: Tutorials -weight: 3000 ---- -This section of the docs provide step-by-step instructions on how to accomplish a goal within Rancher. diff --git a/content/rancher/v2.x/en/tasks/clusters/adding-a-node/_index.md b/content/rancher/v2.x/en/tasks/clusters/adding-a-node/_index.md deleted file mode 100644 index 22b6749fc45..00000000000 --- a/content/rancher/v2.x/en/tasks/clusters/adding-a-node/_index.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Adding a Node -weight: 3475 -draft: true ---- -Coming Soon - -## By Node/Cloud Provider - -Coming Soon - -## By Custom - -Coming Soon diff --git a/content/rancher/v2.x/en/tasks/clusters/adding-a-pod-security-policy/_index.md b/content/rancher/v2.x/en/tasks/clusters/adding-a-pod-security-policy/_index.md deleted file mode 100644 index 6bbd2ef58c9..00000000000 --- a/content/rancher/v2.x/en/tasks/clusters/adding-a-pod-security-policy/_index.md +++ /dev/null @@ -1,97 +0,0 @@ ---- -title: Adding a Pod Security Policy -weight: 3475 ---- - -_Pod Security Policies_ are objects that control security-sensitive aspects of pod specification (like root privileges). - -You can add a Pod Security Policy (PSPs hereafter) in the following contexts: - -- [When creating a cluster](#cluster-creation--adding-a-default-pod-security-policy) -- [When editing an existing cluster](#existing-cluster--adding-a-pod-security-policy) -- [When creating a project](#project-creation--adding-a-pod-security-policy) -- [When editing an existing project](#existing-project--adding-a-pod-security-policy) - -> **Note:** We recommend adding PSPs during cluster and project creation instead of adding it to an existing one. - -For more information about PSPs, refer to [Pod Security Policy]({{< baseurl >}}/rancher/v2.x/en/admin-settings/pod-security-policies). - -## Cluster Creation: Adding a Default Pod Security Policy - -When you create a new cluster, you can configure it to apply a PSP immediately. As you create the cluster, use the **Cluster Options** to enable a PSP. The PSP assigned to the cluster will be the default PSP for projects within the cluster. - ->**Prerequisite:** ->Create a Pod Security Policy within Rancher. Before you can assign a default PSP to a new cluster, you must have a PSP available for assignment. For instruction, see [Creating Pod Security Policies]({{< baseurl >}}/rancher/v2.x/en/admin-settings/pod-security-policies/). ->**Note:** ->For security purposes, we recommend assigning a PSP as you create your clusters. - -To enable a default Pod Security Policy, set the **Pod Security Policy Support** option to **Enabled**, and then make a selection from the **Default Pod Security Policy** drop-down. - -When the cluster finishes provisioning, the PSP you selected is applied to all projects within the cluster. - -For detailed instruction about assigning a PSP to a new cluster, see [Creating a Cluster]({{< baseurl >}}/rancher/v2.x/en/tasks/clusters/creating-a-cluster/). - -## Existing Cluster: Adding a Pod Security Policy - -If you don't apply a PSP as you create your cluster, you can always add one later. - ->**Prerequisite:** ->Create a Pod Security Policy within Rancher. Before you can assign a default PSP to an existing cluster, you must have a PSP available for assignment. For instruction, see [Creating Pod Security Policies]({{< baseurl >}}/rancher/v2.x/en/admin-settings/pod-security-policies/). - -1. From the **Global** view, find the cluster that you want to apply your PSP to. Select **Vertical Ellipsis (...) > Edit** for the cluster you want to enable PSPs for. - -2. Expand the **Cluster Options** accordion. - -3. From **Pod Security Policy Support**, select **Enabled**. - - >**Note:** Not all cluster providers support PSPs, so this option may not be available. - - **Step Result:** The **Default Pod Security Policy** drop-down activates. - -4. From **Default Pod Security Policy**, select the PSP you want to apply to the cluster. - -5. Click **Save**. - -**Result:** The PSP is applied to the cluster and any projects within the cluster. - ->**Note:** Any workloads that are already running in a cluster or project before a PSP is assigned will not be checked if it complies with the PSP. Workloads would need to be cloned or upgraded to see if they pass the PSP. - -## Project Creation: Adding a Pod Security Policy - -When you create a new project, you can assign a PSP directly to the project. Assigning a PSP to a project will: - -- Override the cluster's default PSP. -- Apply the PSP to the project. -- Apply the PSP to any namespaces you add to the project later. - ->**Prerequisites:** -> -> - Create a Pod Security Policy within Rancher. Before you can assign a default PSP to a new project, you must have a PSP available for assignment. For instruction, see [Creating Pod Security Policies]({{< baseurl >}}/rancher/v2.x/en/admin-settings/pod-security-policies/). -> - Assign a default Pod Security Policy to the project's cluster. You can't assign a PSP to a project until one is already applied to the cluster. For more information, see [Existing Cluster: Adding a Pod Security Policy](#existing-cluster--adding-a-pod-security-policy). - -As you create the project, make a selection from the **Pod Security Policy** drop-down to assign a PSP. - - - -## Existing Project: Adding a Pod Security Policy - -You can always assign a PSP to an existing project if you didn't assign one during creation. - ->**Prerequisites:** -> -> - Create a Pod Security Policy within Rancher. Before you can assign a default PSP to an existing project, you must have a PSP available for assignment. For instruction, see [Creating Pod Security Policies]({{< baseurl >}}/rancher/v2.x/en/admin-settings/pod-security-policies/). -> - Assign a default Pod Security Policy to the project's cluster. You can't assign a PSP to a project until one is already applied to the cluster. For more information, see [Existing Cluster: Adding a Pod Security Policy](#existing-cluster--adding-a-pod-security-policy). - -1. From the **Global** view, find the cluster containing the project you want to apply a PSP to. - -1. From the main menu, select **Projects/Namespaces**. - -3. Find the project that you want to add a PSP to. From that project, select **Vertical Ellipsis (...) > Edit**. - -4. From the **Pod Security Policy** drop-down, select the PSP you want to apply to the project. - -5. Click **Save**. - -**Result:** The PSP is applied to the project and any namespaces added to the project. - ->**Note:** Any workloads that are already running in a cluster or project before a PSP is assigned will not be checked if it complies with the PSP. Workloads would need to be cloned or upgraded to see if they pass the PSP. diff --git a/content/rancher/v2.x/en/tasks/clusters/adding-managing-cluster-members/_index.md b/content/rancher/v2.x/en/tasks/clusters/adding-managing-cluster-members/_index.md deleted file mode 100644 index 57d7b0a8c19..00000000000 --- a/content/rancher/v2.x/en/tasks/clusters/adding-managing-cluster-members/_index.md +++ /dev/null @@ -1,53 +0,0 @@ ---- -title: Adding Cluster Members -weight: 3525 ---- - -If you want to provide a user with access and permissions to _all_ projects, nodes, and resources within a cluster, assign the user a cluster membership. - ->**Tip:** Want to provide a user with access to a _specific_ project within a cluster? See [Adding Project Members]({{< baseurl >}}/rancher/v2.x/en/tasks/projects/add-project-members/) instead. - -There are two contexts where you can add cluster members: - -- [Adding Members to a New Cluster]({{< baseurl >}}/rancher/v2.x/en/tasks/clusters/creating-a-cluster) - - You can add members to a cluster as you create it (recommended if possible). - -- [Adding Members to an Existing Cluster](#adding-members-to-an-existing-cluster) - - You can always add members to a cluster later. See below. - -### Adding Members to an Existing Cluster - -Following cluster creation, you can add users as cluster members so that they can access its resources. - -1. From the **Global** view, open the cluster that you want to add members to. - -2. From the main menu, select **Members**. Then click **Add Member**. - -3. Search for the user or group that you want to add to the cluster. - - If external authentication is configured: - - - Rancher returns users from your [external authentication]({{< baseurl >}}/rancher/v2.x/en/admin-settings/authentication/) source as you type. - - >**Using AD but can't find your users?** - >There may be an issue with your search attribute configuration. See [Configuring Active Directory Authentication: Step 5]({{< baseurl >}}/rancher/v2.x/en/admin-settings/authentication/configuring-ad/). - - - A drop-down allows you to add groups instead of individual users. The drop-down only lists groups that you, the logged in user, are part of. - - >**Note:** If you are logged in as a local user, external users do not display in your search results. For more information, see [External Authentication Configuration and Principal Users]({{< baseurl >}}/rancher/v2.x/en/admin-settings/authentication/#external-authentication-configuration-and-principal-users). - -4. Assign the user or group **Cluster** roles. - - [What are Cluster Roles?]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/#cluster-roles) - - >**Tip:** For Custom Roles, you can modify the list of individual roles available for assignment. - > - > - To add roles to the list, [Add a Custom Role]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/creating-roles/#adding-a-custom-role). - > - To remove roles from the list, [Lock/Unlock Roles]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/creating-roles/#locking-unlocking-roles). - -**Result:** The chosen users are added to the cluster. - -- To revoke cluster membership, select the user and click **Delete**. This action deletes membership, not the user. -- To modify a user's roles in the cluster, delete them from the cluster, and then re-add them with modified roles. \ No newline at end of file diff --git a/content/rancher/v2.x/en/tasks/projects/_index.md b/content/rancher/v2.x/en/tasks/projects/_index.md deleted file mode 100644 index 43214fef9d8..00000000000 --- a/content/rancher/v2.x/en/tasks/projects/_index.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Projects -weight: 3650 -draft: true ---- -_Projects_ are a new feature in Rancher that allows you to group namespaces. Users can be added as members to the project, and the project owner can assign roles to each member to control their project access. diff --git a/content/rancher/v2.x/en/tasks/projects/add-project-alerts/_index.md b/content/rancher/v2.x/en/tasks/projects/add-project-alerts/_index.md deleted file mode 100644 index 84eae19507d..00000000000 --- a/content/rancher/v2.x/en/tasks/projects/add-project-alerts/_index.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Adding Project Alerts -weight: -draft: true ---- -Coming Soon diff --git a/content/rancher/v2.x/en/tasks/projects/create-pod-security-policies/_index.md b/content/rancher/v2.x/en/tasks/projects/create-pod-security-policies/_index.md deleted file mode 100644 index 70308048c88..00000000000 --- a/content/rancher/v2.x/en/tasks/projects/create-pod-security-policies/_index.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Creating Pod Security Policies -weight: -draft: true ---- -Coming Soon diff --git a/content/rancher/v2.x/en/tasks/projects/create-project/_index.md b/content/rancher/v2.x/en/tasks/projects/create-project/_index.md deleted file mode 100644 index 8fb7c996ec6..00000000000 --- a/content/rancher/v2.x/en/tasks/projects/create-project/_index.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -title: Creating Projects -weight: ---- - -1. From the **Global** view, choose **Clusters** from the main menu. From the **Clusters** page, open the cluster from which you want to create a project. - -1. From the main menu, choose **Projects/Namespaces**. Then click **Add Project**. - -1. Enter a **Project Name**. - -1. **Optional:** Select a **Pod Security Policy**. - - [What are Pod Security Policies?]({{< baseurl >}}/rancher/v2.x/en/admin-settings/pod-security-policies) - - >**Note:** This option is only available if you've already created a Pod Security Policy. For instruction, see [Creating Pod Security Policies]({{< baseurl >}}/rancher/v2.x/en/admin-settings/pod-security-policies/#creating-pod-security-policies). - -1. **Recommended:** Add project members. - - Use the **Members** accordion to provide other users with project access and roles. - - By default, your user is added as the project `Owner`. - - 1. Click **Add Member**. - - 1. From the **Name** combo box, search for a user or group that you want to assign project access. - - >**Note:** You can only search for groups if external authentication is enabled. - - 1. From the **Role** drop-down, choose a role. - - [What are Roles?]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/#cluster-and-project-roles) - - >**Tip:** Choose Custom to create a custom role on the fly: [Custom Project Roles]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/#custom-project-roles). - - 1. To add more members, repeat substeps a—c. - - -1. Click **Create**. - -**Result:** Your project is created. You can view it from the cluster's **Projects/Namespaces** view. \ No newline at end of file diff --git a/content/rancher/v2.x/en/tasks/projects/enable-project-logging/_index.md b/content/rancher/v2.x/en/tasks/projects/enable-project-logging/_index.md deleted file mode 100644 index 0f02a92be43..00000000000 --- a/content/rancher/v2.x/en/tasks/projects/enable-project-logging/_index.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Enabling Project Logging -weight: -draft: true ---- -Coming Soon diff --git a/content/rancher/v2.x/en/tasks/projects/launch-a-catalog-app/_index.md b/content/rancher/v2.x/en/tasks/projects/launch-a-catalog-app/_index.md deleted file mode 100644 index 47da8f3b928..00000000000 --- a/content/rancher/v2.x/en/tasks/projects/launch-a-catalog-app/_index.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Launching a Catalog App -weight: -draft: true ---- -After you've enabled default catalogs or setup a custom catalog, you can launch apps using a catalog instead of a standard deployment. - ->**Prerequisite:** Enable a catalog. For more information, see [Catalogs and Charts]({{< baseurl >}}/rancher/v2.x/en/concepts/catalogs). - -1. From the **Global** view, open the project that you want to deploy to. - -2. From the main menu, choose **Catalog Apps**. Then click **Launch**. - -3. Find the app that you want to launch, and then click **View Now**. - -4. Under **Configuration Options** enter a **Name**. By default, this name is also used to create a Kubernetes namespace for the application. - - * If you would like to change the **Namespace**, click **Customize** and enter a new name. - * If you want to use a different namespace that already exists, click **Customize**, and then click **Use an existing namespace**. Choose a namespace from the list. - -5. Select a **Template Version**. - -6. Complete the rest of the **Configuration Options**. - - * For native Helm charts (i.e., charts from the **Helm Stable** or **Helm Incubator** catalogs), answers are provided as key value pairs in the **Answers** section. - * Keys and values are available within **Detailed Descriptions**. - -7. Review the files in **Preview**. When you're satisfied, click **Launch**. - -**Result**: Your application is deployed to your chosen namespace. You can view the application status from the project's: - -- **Workloads** view -- **Catalog Apps** view diff --git a/content/rancher/v2.x/en/tasks/projects/manage-pod-security-policies/_index.md b/content/rancher/v2.x/en/tasks/projects/manage-pod-security-policies/_index.md deleted file mode 100644 index 9da1ef07f4f..00000000000 --- a/content/rancher/v2.x/en/tasks/projects/manage-pod-security-policies/_index.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Managing Pod Security Policies -weight: -draft: true ---- -Coming Soon diff --git a/content/rancher/v2.x/en/tasks/projects/manage-project-alerts/_index.md b/content/rancher/v2.x/en/tasks/projects/manage-project-alerts/_index.md deleted file mode 100644 index 9a2ce2dcde6..00000000000 --- a/content/rancher/v2.x/en/tasks/projects/manage-project-alerts/_index.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Managing Project Alerts -weight: -draft: true ---- -Coming Soon diff --git a/content/rancher/v2.x/en/tasks/projects/manage-project-logging/_index.md b/content/rancher/v2.x/en/tasks/projects/manage-project-logging/_index.md deleted file mode 100644 index 2ff795cd31f..00000000000 --- a/content/rancher/v2.x/en/tasks/projects/manage-project-logging/_index.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Managing Project Logging -weight: -draft: true ---- -Coming Soon diff --git a/content/rancher/v2.x/en/tasks/projects/manage-project-members/_index.md b/content/rancher/v2.x/en/tasks/projects/manage-project-members/_index.md deleted file mode 100644 index 3ca33000d8c..00000000000 --- a/content/rancher/v2.x/en/tasks/projects/manage-project-members/_index.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Managing Project Members -weight: -draft: true ---- -Coming Soon diff --git a/content/rancher/v2.x/en/tasks/projects/switch-project/_index.md b/content/rancher/v2.x/en/tasks/projects/switch-project/_index.md deleted file mode 100644 index f7ab9fdb8eb..00000000000 --- a/content/rancher/v2.x/en/tasks/projects/switch-project/_index.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: Switching Projects (and Clusters) -weight: -draft: true ---- - -To switch between clusters, use the **Global** drop-down available in the main menu. - -![Global Menu]({{< baseurl >}}/img/rancher/global-menu.png) - -Alternatively, you can switch between projects and clusters using the main menu. - -- To switch between clusters, open the **Global** view and select **Clusters** from the main menu. Then open a cluster. -- To switch between projects, open a cluster, and then select **Projects/Namespaces** from the main menu. Select the link for the project that you want to open. \ No newline at end of file diff --git a/content/rancher/v2.x/en/tasks/workloads/_index.md b/content/rancher/v2.x/en/tasks/workloads/_index.md deleted file mode 100644 index 9f174b46aca..00000000000 --- a/content/rancher/v2.x/en/tasks/workloads/_index.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -title: Workloads -weight: 3675 ---- - -This section of the documentation contains instructions for deploying workloads and using workload options. - -- [Deploy Workloads]({{< baseurl >}}/rancher/v2.x/en/tasks/workloads/deploy-workloads/) -- [Upgrade Workloads]({{< baseurl >}}/rancher/v2.x/en/tasks/workloads/upgrade-workloads/) -- [Rollback Workloads]({{< baseurl >}}/rancher/v2.x/en/tasks/workloads/rollback-workloads/)