* Sync main to v2.13.0 (#2065) * It's bad form to ask users to pass something they just curled from the internet directly to sh Updated the instructions for uninstalling the rancher-system-agent to use a temporary script file instead of piping directly to sh. * doc(rancher-security): improve structure and content to latest, v2.13-preview and v2.12 (#2024) - add Rancher Kubernetes Distributions (K3s/RKE2) Self-Assessment and Hardening Guide section - add kubernetes cluster security best practices link to rancher-security section - add k3s-selinux and update selinux-rpm details - remove rhel/centos 7 support Signed-off-by: Andy Pitcher <andy.pitcher@suse.com> * Updating across supported versions and translations. Signed-off-by: Sunil Singh <sunil.singh@suse.com> --------- Signed-off-by: Andy Pitcher <andy.pitcher@suse.com> Signed-off-by: Sunil Singh <sunil.singh@suse.com> Co-authored-by: Tejeev <tj@rancher.com> Co-authored-by: Andy Pitcher <andy.pitcher@suse.com> Co-authored-by: Sunil Singh <sunil.singh@suse.com> * Update roletemplate aggregation doc and version information * Add versioned docs * Remove ext token and kubeconfig feature flag sections and document bearer Token * Update corresponding v2.13 pages * update doc for pni in gke * Adding reverted session idle information from PR 1653 Signed-off-by: Sunil Singh <sunil.singh@suse.com> * [2.13.0] Add versions table entry * [2.13.0] Add webhook version * [2.13.0] Add CSP Adapter version * [2.13.0] Add deprecated feature table entry * [2.13.0] Update CNI popularity stats * Update GKE Cluster Configuration for Project Network Isolation instructions * Fix link and port to 2.13 * [2.13.0] Add Swagger JSON * [v2.13.0] Add info about Azure AD Roles claims (#2079) * Add info about Azure AD roles claims compatibility * Apply suggestions from code review Co-authored-by: Sunil Singh <sunil.singh@suse.com> * Add suggestions to v2.13 --------- Co-authored-by: Sunil Singh <sunil.singh@suse.com> * [2.13.0] Remove preview designation * user public api docs (#2069) * user public api docs * Apply suggestions from code review Co-authored-by: Andreas Kupries <akupries@suse.com> * Apply suggestions from code review Co-authored-by: Peter Matseykanets <pmatseykanets@gmail.com> * explain plaintext is never stored * add users 2.13 versioned docs * remove extra ``` * Apply suggestions from code review Co-authored-by: Lucas Saintarbor <lucas.saintarbor@suse.com> * add space before code block --------- Co-authored-by: Andreas Kupries <akupries@suse.com> Co-authored-by: Peter Matseykanets <pmatseykanets@gmail.com> Co-authored-by: Lucas Saintarbor <lucas.saintarbor@suse.com> * support IPv6 (#2041) * [v2.13.0] Add Configure GitHub App page (#2081) * Add Configure GitHub App page * Apply suggestions from code review Co-authored-by: Billy Tat <btat@suse.com> * Fix header/GH URL & add suggestions to v2.13 * Apply suggestions from code review Co-authored-by: Petr Kovar <pknbe@volny.cz> * Apply suggestions from code review to v2.13 * Add note describing why to use Installation ID * Apply suggestions from code review Co-authored-by: Billy Tat <btat@suse.com> --------- Co-authored-by: Billy Tat <btat@suse.com> Co-authored-by: Petr Kovar <pknbe@volny.cz> * [v2.13.0] Add info about Generic OIDC Custom Mapping (#2080) * Add info about Generic OIDC Custom Mapping * Apply suggestions from code review Co-authored-by: Sunil Singh <sunil.singh@suse.com> Co-authored-by: Billy Tat <btat@suse.com> * Apply suggestions from code review Co-authored-by: Sunil Singh <sunil.singh@suse.com> Co-authored-by: Billy Tat <btat@suse.com> * Add suggestions to v2.13 * Remove repetitive statement in intro * Move Prereq intro/note to appropriate section * Fix formatting, UI typo, add Custom Claims section under Configuration Reference section * Add section about how a custom groups claim works / note about search limitations for groups in RBAC --------- Co-authored-by: Sunil Singh <sunil.singh@suse.com> Co-authored-by: Billy Tat <btat@suse.com> * [v2.13.0] Add info about OIDC SLO support (#2086) * Add shared file covering OIDC SLO support to OIDC auth pages * Ad How to get the End Session Endpoint steps * Add generic curl exampleto retrieve end_session_endpoint * [2.13.0] Bump release date --------- Signed-off-by: Andy Pitcher <andy.pitcher@suse.com> Signed-off-by: Sunil Singh <sunil.singh@suse.com> Co-authored-by: Lucas Saintarbor <lucas.saintarbor@suse.com> Co-authored-by: Tejeev <tj@rancher.com> Co-authored-by: Andy Pitcher <andy.pitcher@suse.com> Co-authored-by: Sunil Singh <sunil.singh@suse.com> Co-authored-by: Jonathan Crowther <jonathan.crowther@suse.com> Co-authored-by: Peter Matseykanets <peter.matseykanets@suse.com> Co-authored-by: Petr Kovar <petr.kovar@suse.com> Co-authored-by: Krunal Hingu <krunal.hingu222@gmail.com> Co-authored-by: Raul Cabello Martin <raul.cabello@suse.com> Co-authored-by: Andreas Kupries <akupries@suse.com> Co-authored-by: Peter Matseykanets <pmatseykanets@gmail.com> Co-authored-by: Jack Luo <jiaqi.luo@suse.com> Co-authored-by: Petr Kovar <pknbe@volny.cz>
10 KiB
Icons & Symbols
- ☰
- The navigation menu toggle, a button in the far top left corner of the Rancher UI. Clicking the ☰ opens a sidebar that provides access to the main sections of the Rancher interface.
- ⋮
- The submenu toggle, a button found at the far right of many table rows throughout the Rancher UI. Clicking the ⋮ opens a submenu containing a contextual list of tasks related to the item in that row.
A
- Apps
- When describing navigation within Rancher, the section of the Rancher UI where you manage Helm charts and Helm chart repositories. In earlier versions of Rancher, this section was called Apps & Marketplace, or Catalogs.
- Apps & Marketplace
- The section of the Rancher UI where you manage Helm charts and Helm chart repositories. In earlier versions of Rancher, this section was called Catalogs. In later versions, it is called Apps.
Versions: Rancher v2.6.5 and later
Synonyms: Apps & Marketplace, Catalogs
Versions: Rancher v2.5.0–2.6.5
Synonyms: Apps, Catalogs
C
- Catalogs
- The section of the Rancher UI where you manage Helm charts and Helm chart repositories. In later versions of Rancher, this section is called Apps & Marketplace, or Apps.
- Community
- A build of Rancher that's available to the entire Rancher community.
Versions: 1. Rancher v2.4 and earlier 2. Rancher v2.7 and later
Synonyms: Apps, Apps & Marketplace
Related terms: Extension catalogs
Related terms: Prime, Rancher Prime
D
- Downstream cluster
- An alternative name for a managed cluster, a Kubernetes cluster that is managed by a Rancher server.
Synonyms: Managed cluster
Related terms: Hosted cluster, Imported cluster, Rancher server, Registered cluster, Upstream cluster
E
- Extension
- Helm charts that can extend and enhance the Rancher UI, and tailor Rancher to your specific environment. Some Extensions require manual installation on a cluster, while others are built into Rancher. Built-in Extensions include Fleet and Harvester. Manually installed Extensions include Kubewarden and Elemental.
- Extension catalogs
- Container image repositories that can be imported to add UI extensions to your Rancher instance.
Versions: Rancher v2.7.0 and later
Related terms: Apps & Marketplace, Catalogs, Integrations
Versions: Rancher v2.7.0 and later
H
- Hosted cluster
- A managed cluster that is hosted in the cloud, by a Kubernetes provider. Rancher supports a variety of hosted Kubernetes providers, including Amazon Elastic Kubernetes Service (EKS), Azure Kubernetes Service (AKS), and Google Kubernetes Engine (GKE). Rancher integrates with the hosted Kubernetes provider's cloud APIs, so that you can manage the cluster from the Rancher UI.
Related terms: Downstream cluster, Imported cluster, Managed cluster, Registered cluster
I
- Imported cluster
- An existing cluster that was provisioned by a third party, then set up to be managed by Rancher. Registered clusters in later versions of Rancher are roughly synonymous with imported clusters. The main difference is that there are more management features exposed in the Rancher UI for registered clusters than for imported clusters.
Versions: Rancher v2.0–2.4
Related terms: Downstream cluster, Hosted cluster, Managed cluster, Reistered cluster
K
- K3s
- A lightweight Kubernetes distribution chiefly designed for workloads that run unattended under tight resource constraints.
- Kubeconfig
-
A Rancher resource
kubeconfigs.ext.cattle.ioused to generate kubeconfigs. - kubeconfig
-
The kubeconfig file is used to configure access to Kubernetes when used in conjunction with
kubectlor other clients. The kubeconfig contents can be generated by creating a Kubeconfig resource.
Related terms: RKE, RKE2
Versions: Rancher v2.12.0 and later
L
- Local cluster
- An alternative name for a Rancher server, the Kubernetes cluster that hosts Rancher and manages other clusters. Here, local refers to the location of the Rancher installation, not to the user's local workstation. Local clusters can be hosted on-premises, in air-gapped environments, or in the cloud.
Synonyms: Rancher server, Upstream cluster
Related terms: Downstream cluster, Hosted cluster, Imported cluster, Managed cluster, Registered cluster
M
- Managed cluster
- A Kubernetes cluster that is managed by a Rancher server. Managed clusters can run on a variety of infrastructure and can be located anywhere, including in the cloud, on-premises, or in air-gapped environments.
Synonyms: Downstream cluster
Related terms: Hosted cluster, Imported cluster, Rancher server, Registered cluster
R
- Rancher
- A Kubernetes management tool to deploy and run clusters anywhere and on any provider. Rancher includes all the software and downstream cluster components used to manage the entire Rancher deployment.
- Rancher Kubernetes Engine (RKE)
- A CNCF-certified Kubernetes distribution that runs entirely within Docker containers. There are two main versions of RKE available. The 1.x software line is sometimes called RKE1, or simply RKE. The next-generation line is called RKE2.
- Rancher Prime
- Rancher Prime is a new edition of the commercial, enterprise offering built on the the same source code. Installation assets are hosted on a trusted registry owned and managed by Rancher with additional value coming in from security assurances, extended lifecycles, access to focused architectures and Kubernetes advisories.
- Rancher server
- The Kubernetes cluster that hosts Rancher and manages the other clusters in the Rancher deployment.
- Registered cluster
- An existing cluster that was provisioned by a third party, then set up to be managed by Rancher. Older versions of Rancher use Imported cluster to refer to a similar concept. The main difference is that there are more management features exposed in the Rancher UI for registered clusters than for imported clusters.
- RKE1
- An alternative name for the v1.x software line of Rancher Kubernetes Engine (RKE). Sometimes called RKE for short. RKE1 is a certified Kubernetes distribution and CLI/library which creates and manages a Kubernetes cluster.
- RKE2
- A fully conformant version of the Rancher Kubernetes Engine (RKE) that is designed for security and compliance with US federal government standards.
- Roles
- Roles determine what actions a Rancher user can make within a cluster or project.
Synonyms: RKE1
Related terms: K3s, RKE2
Synonyms: Local cluster, Upstream cluster
Related terms: Downstream cluster, Hosted cluster, Imported cluster, Managed cluster, Registered cluster
Versions: Rancher v2.5 and later
Related terms: Downstream cluster, Hosted cluster, Imported cluster, Managed cluster
Synonyms: Rancher Kubernetes Engine
Related terms: K3s, RKE2
Versions: Rancher v2.6.0 and later (to provision clusters), Rancher 2.5.0 and later (to register clusters)
Related terms: K3s, RKE
U
- Upstream cluster
- An alternative name for the Rancher server, the Kubernetes cluster that hosts Rancher and manages the other clusters in the Rancher deployment.
- User
-
A Rancher resource
users.management.cattle.iothat defines a user within Rancher.
Synonyms: Local cluster, Rancher server
Related terms: Downstream cluster, Hosted cluster, Imported cluster, Managed cluster, Registered cluster
W
- Workload
- Objects that set deployment rules for pods. Based on these rules, Kubernetes performs the deployment and updates the workload with the current state of the application. Workloads let you define the rules for application scheduling, scaling, and upgrade.