Jump to content
SUSE Linux Enterprise Micro 5.0, K3s 1.20.6, SUSE Rancher 2.5.8

Reference Implementation - SUSE Rancher

The purpose of this document is to provide an overview and procedure of implementing SUSE (R) offerings for SUSE Rancher, as a multi-cluster container management platform for organizations that deploy containerized workloads, orchestrated by Kubernetes. SUSE Rancher makes it easy to deploy, manage, and use Kubernetes everywhere, meet IT requirements, and empower DevOps teams.

Disclaimer: The articles and individual documents published in the SUSE Best Practices series were contributed voluntarily by SUSE employees and by third parties. If not stated otherwise inside the document, the articles are intended only to be one example of how a particular action could be taken. Also, SUSE cannot verify either that the actions described in the articles do what they claim to do or that they do not have unintended consequences. All information found in this article has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Therefore, we need to specifically state that neither SUSE LLC, its affiliates, the authors, nor the translators may be held liable for possible errors or the consequences thereof.

Publication Date: 2021-09-16

1 Introduction

On the digital transformation journey to a full cloud native landscape, utilization of microservices becomes the main approach with the dominant technology for such container orchestration being Kubernetes [1] With its large community of developers and abundant features and capabilities, Kubernetes has become the defacto standard and is included across most container-as-a-service platforms. With all of these technologies in place, both developer and operation teams can effectively deploy, manage and deliver functionality to their end users in a resilient and agile manner.

1.1 Motivation

While any developer or organization may simply start with a single, Kubernetes-based deployment, it is very common for that number of cluster instances to rapidly grow. While each of these may have specific focus areas, it becomes imperative to figure out how to use, manage, maintain and replicate all of these instances over time.

This is where SUSE Rancher leads the industry, being able to manage access, usage, infrastructure and applications across clusters, that are Cloud Native Computing Foundation ( CNCF [2] ) conformant and certified [3], anywhere across edge, on-premise data centers, or cloud service providers. SUSE Rancher optimizes creating and managing Kubernetes clusters like:

  • Lightweight edge-centric K3s

  • Rancher Kubernetes Engine ( RKE )

  • and other Kubernetes clusters that are based upon CNCF certified Kubernetes distributions or installations

and deployed across various supported infrastructure elements.

1.2 Scope

The scope of this document is to provide a general reference implementation of SUSE Rancher. This can be done in a variety of solution layered stacks, to become a fundamental component of a managing multiple Kubernetes ecosystems.

1.3 Audience

This document is intended for IT decision makers, architects, system administrators and technicians who are implementing a flexible, software-defined Kubernetes management platform. One should still be familiar with the traditional IT infrastructure pillars — networking, computing and storage — along with the local use cases for sizing, scaling and limitations within each pillars' environments.

2 Business aspect

Agility is driving developers toward more cloud native methodologies that focus on microservices architectures and streamlined workflows. Container technologies, like Kubernetes, embody this agile approach and help enable cloud native transformation.

By unifying IT operations with Kubernetes, organizations realize key benefits like increased reliability, improved security and greater efficiencies with standardized automation. Therefore, Kubernetes infrastructure platforms are adopted by enterprises to deliver:

Cluster Operations

Improved Production and DevOps efficiencies with simplified cluster usage and robust operations

Security Policy & User Management

Consistent security policy enforcement plus advanced user management on any Kubernetes infrastructure

Access to Shared Tools & Services

A high level of reliability with easy, consistent access to a broad set of tools and services

2.1 Business problem

Many organizations are deploying Kubernetes clusters everywhere – in the cloud, on-premises, and at the edge - to unify IT operations. Such organizations can realize dramatic benefits, including:

  • Consistently deliver a high level of reliability on any infrastructure

  • Improve DevOps efficiency with standardized automation

  • Ensure enforcement of security policies on any infrastructure

However, simply relying on upstream Kubernetes alone can introduce overhead and risk because Kubernetes clusters are typically deployed:

  • Without central visibility

  • Without consistent security policies

  • And must be managed independently

Deploying a scalable kubernetes requires consideration of a large ecosystem, encompassing many software and infrastructure components and providers. Further, the ability to continually address the needs and concerns of:

Developers

For those who just focus on writing code to build their apps securely using a preferred workflow, providing a simple, push-button deployment mechanism of their containerized workloads where needed.

IT Operators

General infrastructure requirements still rely upon traditional IT pillars are for the stacked, underlying infrastructure. Ease of deployment, availability, scalability, resiliency, performance, security and integrity are still core concerns to be addressed for administrative control and observability.

2.2 Business value

By allowing operation teams to focus on infrastructure and developers to deploy code the way they want too, SUSE and the Rancher offerings helps bring products to market faster and accelerate an organization’s digital transformation.

SUSE Rancher is a fundamental part of the complete software stack for teams adopting containers. It provides DevOps teams with integrated tools for running containerized workloads while also addressing the operational and security challenges of managing multiple Kubernetes clusters across any targetedd infrastructure.

Developers

SUSE Rancher makes it easy to securely deploy containerized applications no matter where the Kubernetes infrastructure runs -– in the cloud, on-premises, or at the edge. Using Helm or the App Catalog to deploy and manage applications across any or all these environments, ensuring multi-cluster consistency with a single deployment process.

IT Operators

SUSE Rancher not only deploys and manages production-grade Kubernetes clusters from datacenter to cloud to the edge, it also unites them with centralized authentication, access control and observability. Further, it streamlines cluster deployment on bare metal or virtual machines and maintains them using defined security policies.

3 Architectural overview

This section outlines the core elements of the SUSE Rancher solution, along with the suggested target platforms and components.

3.1 Solution architecture

The figure below illustrates the high-level architecture of the SUSE Rancher installation that manages multiple downstream Kubernetes clusters:

ArchitectureOverview Rancher
Figure 3.1: Architecture Overview - SUSE Rancher
Authentication Proxy

A user is authenticated via SUSE Rancher and then, if authorized, can access both the SUSE Rancher environment and the downstream clusters and workloads.

API Server

This provides the programmatic interface backend for a user, utilizing command-line interactions with SUSE Rancher and the managed clusters.

Data Store

The purpose of this service is to capture the configuration and state of SUSE Rancher and the managed clusters to aid in backup and recovery processes.

Cluster Controller

Interacting with a cluster agent on the downstream cluster, the cluster controller allows the communication path for users and services to leverage for workloads and cluster management.

Once setup, users can interact with SUSE Rancher through the web-based user interface (UI), the command-line interface ( CLI ), and programatically through the application programming interface ( API ). Depending upon the assigned roles, group membership and privileges, a user could:

  • manage all clusters, users, roles, projects

  • deploy new clusters, import other clusters, or remove existing ones

  • manage workloads across respective or labelled clusters

  • simply view clusters or workloads, or just benefit from what is running

For the best performance and security, the recommended deployment is a dedicated Kubernetes cluster for the SUSE Rancher management server. Running user workloads on this cluster is not advised. After deploying SUSE Rancher, one can then create or import clusters for orchestrated workloads.

4 Component model

This section describes the various components being used to create a SUSE Rancher solution deployment.

4.1 Component overview

By utilizing:

  • Software

    • Multi-cluster Management Server - SUSE Rancher

    • Kubernetes Platform - K3s

    • Linux Operating System - SUSE Linux Enterprise Micro

  • Compute Platform

one can create the necessary infrastructure and services. Further details for these components are described in the following sections.

4.2 Software - SUSE Rancher

SUSE Rancher is a Kubernetes native multi-cluster container management platform. It addresses these challenges by delivering the following key functions, as shown in the following figure:

Rancher Overview
Figure 4.1: Overview of SUSE Rancher
Certified Kubernetes Distributions

SUSE Rancher supports management of any CNCF certified Kubernetes distribution. That includes:

  • for development, edge, branch workloads, SUSE offerings like K3s, a CNCF certified lightweight distribution of Kubernetes

  • for on-premises workloads, a SUSE offering Rancher Kubernetes Engine ( RKE ), a CNCF certified Kubernetes distribution for both bare-metal and virtualized servers

  • for the public cloud, hosted Kubernetes services like

    • Amazon Elastic Kubernetes Service ( EKS [4] ),

    • Azure Kubernetes Service ( AKS [5] ) and

    • Google Kubernetes Engine ( GKE [6] ).

Simplified Cluster Operations and Infrastructure Management

SUSE Rancher provides simple, consistent cluster operations including provisioning and templates, configuration and lifecycle version management, along with visibility and diagnostics.

Security and Authentication

SUSE Rancher integrates and utilizes existing directory services, to automate processes and apply a consistent set of identity and access management ( IAM) plus security policies for all the managed clusters, no matter where they’re running.

Policy Enforcement and Governance

SUSE Rancher includes audit and security guideline enforcement, monitoring and logging functions, along with user, network and workload policies distributed across all managed clusters.

Platform Services

SUSE Rancher also provides a rich catalog of services for building, deploying and scaling containerized applications, including app packaging, logging, monitoring and service mesh.

Given SUSE Rancher relies upon being deployed on a Kubernetes platform, the next sections describe the suggested component layering approach.

4.3 Software - K3s

K3s is packaged as a single binary, which is about 50 megabytes in size. Bundled in that single binary is everything needed to run Kubernetes anywhere, including low-powered IoT and Edge-based devices. The binary includes:

  • the container runtime

  • any important host utilities like

    • iptables, socat and du.

The only OS dependencies are the Linux kernel itself and a proper dev, proc and sysfs mounts (this is done automatically on all modern Linux distributions). K3s bundles the Kubernetes components:

  • kube-apiserver,

  • kube-controller-manager,

  • kube-scheduler,

  • kubelet and

  • kube-proxy

into combined processes that are presented as a simple server and agent model, as represented in the following figure:

K3s Overview
Figure 4.2: Overview of K3s

K3s can run as a complete cluster on a single node or can be expanded into a multi-node cluster. Besides the core Kubernetes components, these are also included:

  • containerd,

  • Flannel,

  • CoreDNS,

  • ingress controller and

  • a simple host port-based service load balancer.

All of these components are optional and can be swapped out for your implementation of choice. With these included components, you get a fully functional and CNCF-conformant cluster so you can start running apps right away. K3s is now a CNCF Sandbox project, being the first Kubernetes distribution ever to be adopted into sandbox.

Learn more information about K3s at https://k3s.io

4.4 Software - SUSE Linux Enterprise Micro

SUSE Linux Enterprise Micro combines the assurance of enterprise-grade security and compliance with the immutability and portability of a modern, lightweight operating system. The top 4 features are:

Immutable OS

Immutable design ensures the OS is not altered during runtime and runs reliably every single time. Security signed and verified transactional updates are easy to rollback if things go wrong.

Security and Compliance

Fully open source and built using open standards, SUSE Linux Enterprise Micro leverages SUSE Linux Enterprise common code base, to provide FIPS 140-2, DISA SRG/STIG, integration with CIS and Common Criteria certified configurations. Includes fully supported security framework (SELinux) with policies.

Architectural Flexibility

Both Arm and x86-64 architectures are supported so you can deploy edge applications with confidence across multiple architectures.

Kubernetes-Ready

You can easily combine SUSE Linux Enterprise Micro with the latest cloud-native technologies including SUSE Rancher, Rancher Kubernetes Engine, Longhorn persistent block storage, and K3s, the world’s most popular Kubernetes distribution for use in low resource, distributed edge locations.

As a result, you get an ultra-reliable infrastructure platform that is also simple to use and comes out-of-the-box with best-in-class compliance. Furthermore, SUSE’s flexible subscription model ensures enterprise assurance for any edge, embedded or IoT deployment without vendor lock-in. A free, evaluation copy can be downloaded or if the organization already has subscriptions, both install media and updates can be obtained from SUSE Customer Center.

4.5 Compute Platform

Leveraging the enterprise grade functionality of the operating system mentioned in the previous section, many compute platforms can be the foundation of the deployment:

  • Virtual machines on supported hypervisors or hosted on cloud service providers

  • Physical, baremetal or single-board computers, either on-premise or hosted by cloud service providers

Tip
Tip

Any SUSE YES certified platform can be used for the nodes of this deployment, as long as the certification refers to the major version of the underlying SUSE operating system required by its release.

5 Deployment

This section describes the process steps for the deployment of the SUSE Rancher solution. It describes the process steps to deploy each of the component layers starting as a base functional proof-of-concept, having considerations on migration towards production, providing scaling guidance that is needed to create the solution.

5.1 Deployment overview

The deployment stack is represented in the following figure:

RI Deployment Rancher K3s SLEMicro
Figure 5.1: SUSE Rancher Deployment Stack

and details are covered for each layer in the following sections.

Note
Note

The following section’s content is ordered and described from the bottom layer up to the top.

5.2 Compute Platform

Preparation(s)

For each node used in the deployment:

  • Validate the necessary CPU, memory, disk capacity, and network interconnect quantity and type are present for each node and its intended role. Refer to the recommended CPU/Memory/Disk/Networking requirements as noted in the SUSE Rancher Hardware Requirements.

  • Further suggestions

    • Disk : Use a pair of local, direct attached, mirrored disk drives is present on each node (SSDs are preferred); these will become the target for the operating system installation.

    • Network : Prepare an IP addressing scheme and optionally create both a public and private network, along with the respective subnets and desired VLAN designations for the target environment.

      • Baseboard Management Controller : If present, consider using a distinct management network for controlled access.

    • Boot Settings : BIOS/uEFI reset to defaults for a known baseline, consistent state or perhaps with desired, localized values.

    • Firmware : Use consistent and up-to-date versions for BIOS/uEFI/device firmware to reduce potential troubleshooting issues later

5.3 SUSE Linux Enterprise Micro

Utilize an enterprise-grade Linux operating system , like SUSE Linux Enterprise Micro, as the base software layer.

Preparation(s)

To meet the solution stack prerequisites and requirements, SUSE operating system offerings, like SUSE Linux Enterprise Micro can be utilized.

  1. Ensure these services are in place and configured for this node to use:

    • Domain Name Service ( DNS ) - an external network-accessible service to map IP Addresses to hostnames

    • Network Time Protocol ( NTP ) - an external network-accessible service to obtain and synchronize system times to aid in timestamp consistency

    • Software Update Service - access to a network-based repository for software update packages. This can be accessed directly from each node via registration to

      • the general, internet-based SUSE Customer Center ( SCC ) or

      • an organization’s SUSE Manager infrastructure or

      • a local server running an instance of Repository Mirroring Tool ( RMT )

        Note
        Note

        During the node’s installation, it can be pointed to the respective update service. This can also be accomplished post-installation with the command-line tool named SUSEConnect.

Deployment Process

On the compute platform node, install the noted SUSE operating system, by following these steps:

  1. Download the SUSE Linux Enterprise Micro product (either for the ISO or Virtual Machine image)

  2. The installation process is described and can be performed with default values by following steps from the SUSE Linux Enterprise Micro product documentation, see Installation Quick Start

    Tip
    Tip

    Adjust both the password and the local network addressing setup to comply with local environment guidelines and requirements.

Deployment Consideration(s)

To further optimize deployment factors, leverage the following practices:

  • Automation

    • To reduce user intervention, unattended deployments of SUSE Linux Enterprise Micro can be automated

      • for ISO-based installations, by referring to the AutoYaST Guide

      • for raw-image based installation, by configuring the Ignition and Combustion tooling as described in the Installation Quick Start

5.4 K3s

Utilize an enterprise-grade Linux operating system , like SUSE Linux Enterprise Micro, as the base software layer.

Preparation(s)

To meet the solution stack prerequisites and requirements, SUSE operating system offerings, like SUSE Linux Enterprise Micro can be utilized.

  1. Ensure these services are in place and configured for this node to use:

    • Domain Name Service ( DNS ) - an external network-accessible service to map IP Addresses to hostnames

    • Network Time Protocol ( NTP ) - an external network-accessible service to obtain and synchronize system times to aid in timestamp consistency

    • Software Update Service - access to a network-based repository for software update packages. This can be accessed directly from each node via registration to

      • the general, internet-based SUSE Customer Center ( SCC ) or

      • an organization’s SUSE Manager infrastructure or

      • a local server running an instance of Repository Mirroring Tool ( RMT )

        Note
        Note

        During the node’s installation, it can be pointed to the respective update service. This can also be accomplished post-installation with the command-line tool named SUSEConnect.

  2. Identify the appropriate, supported version of the K3s binary (e.g. vX.YY.ZZ+k3s1), by reviewing the "Rancher Support Matrix" on the Support and Maintenance Terms of Service web page.

Deployment Process

Perform the following steps to install the first K3s server on one of the nodes to be used for the Kubernetes control plane

  1. Set the following variable with the noted version of K3s, as found during the preparation steps.

    K3s_VERSION=""
  2. Install the version of K3s with embedded etcd enabled:

    curl -sfL https://get.k3s.io | \
    	INSTALL_K3S_VERSION=${K3s_VERSION} \
    	INSTALL_K3S_EXEC='server --cluster-init --write-kubeconfig-mode=644' \
    	sh -s -
    Tip
    Tip

    To address Availability and possible scaling to a multiple node cluster, etcd is enabled instead of using the default SQLite datastore.

    • Monitor the progress of the installation: watch -c "kubectl get deployments -A"

      • The K3s deployment is complete when elements of all the deployments (coredns, local-path-provisioner, metrics-server, and traefik) show at least "1" as "AVAILABLE"

      • Use Ctrl+c to exit the watch loop after all deployment pods are running

Deployment Consideration(s)

To further optimize deployment factors, leverage the following practices:

  • Availability

    • A full high-availability K3s cluster is recommended for production workloads. The etcd key/value store (aka database) requires an odd number of servers (aka master nodes) be allocated to the K3s cluster. In this case, two additional control-plane servers should be added; for a total of three.

      1. Deploy the same operating system on the new compute platform nodes, then log into the new nodes as root or as a user with sudo privileges.

      2. Execute the following sets of commands on each of the remaining control-plane nodes:

        • Set the following additional variables, as appropriate for this cluster

          # Private IP preferred, if available
          FIRST_SERVER_IP=""
          
          # From /var/lib/rancher/k3s/server/node-token file on the first server
          NODE_TOKEN=""
          
          # Match the first of the first server
          K3s_VERSION=""
        • Install K3s

          curl -sfL https://get.k3s.io | \
          	INSTALL_K3S_VERSION=${K3s_VERSION} \
          	K3S_URL=https://${FIRST_SERVER_IP}:6443 \
          	K3S_TOKEN=${NODE_TOKEN} \
          	K3S_KUBECONFIG_MODE="644" INSTALL_K3S_EXEC='server' \
          	sh -
        • Monitor the progress of the installation: watch -c "kubectl get deployments -A"

          • The K3s deployment is complete when elements of all the deployments (coredns, local-path-provisioner, metrics-server, and traefik) show at least "1" as "AVAILABLE"

          • Use Ctrl+c to exit the watch loop after all deployment pods are running

            By default, the K3s server nodes are available to run non-control-plane workloads. In this case, the K3s default behavior is perfect for the SUSE Rancher server cluster as it doesn’t require additional agent (aka worker) nodes to maintain a highly available SUSE Rancher server application.

            Note
            Note

            This can be changed to the normal Kubernetes default by adding a taint to each server node. See the official Kubernetes documentation for more information on how to do that.

        • (Optional) In cases where agent nodes are desired, execute the following sets of commands, using the same "K3s_VERSION", "FIRST_SERVER_IP", and "NODE_TOKEN" variable settings as above, on each of the agent nodes to add it to the K3s cluster:

          curl -sfL https://get.k3s.io | \
          	INSTALL_K3S_VERSION=${K3s_VERSION} \
          	K3S_URL=https://${FIRST_SERVER_IP}:6443 \
          	K3S_TOKEN=${NODE_TOKEN} \
          	K3S_KUBECONFIG_MODE="644" \
          	sh -

5.5 SUSE Rancher

Utilize an enterprise-grade Linux operating system , like SUSE Linux Enterprise Micro, as the base software layer.

Preparation(s)

To meet the solution stack prerequisites and requirements, SUSE operating system offerings, like SUSE Linux Enterprise Micro can be utilized.

  1. Ensure these services are in place and configured for this node to use:

    • Domain Name Service ( DNS ) - an external network-accessible service to map IP Addresses to hostnames

    • Network Time Protocol ( NTP ) - an external network-accessible service to obtain and synchronize system times to aid in timestamp consistency

    • Software Update Service - access to a network-based repository for software update packages. This can be accessed directly from each node via registration to

      • the general, internet-based SUSE Customer Center ( SCC ) or

      • an organization’s SUSE Manager infrastructure or

      • a local server running an instance of Repository Mirroring Tool ( RMT )

        Note
        Note

        During the node’s installation, it can be pointed to the respective update service. This can also be accomplished post-installation with the command-line tool named SUSEConnect.

Deployment Process

While logged into the node, as root or with sudo privileges, install SUSE Rancher:

  1. Create the Helm Chart custom resource for cert-manager:

    • Set the following variable with the desired version of cert-manager

      CERT_MANAGER_VERSION=""
      Note
      Note

      At this time, the most current, supported version of cert-manager is v1.0.4

    • Create the cert-manager Helm Chart custom resource manifest

      cat <<EOF> cert-manager-helm-crd.yaml
      apiVersion: helm.cattle.io/v1
      kind: HelmChart
      metadata:
        name: cert-manager
        namespace: kube-system
      spec:
        chart: cert-manager
        targetNamespace: cert-manager
        version: ${CERT_MANAGER_VERSION}
        repo: https://charts.jetstack.io
      EOF
    • Create the cert-manager CRDs and apply the Helm Chart resource manifest:

      kubectl create namespace cert-manager
      
      kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/${CERT_MANAGER_VERSION}/cert-manager.crds.yaml
      
      sudo mv cert-manager-helm-crd.yaml /var/lib/rancher/k3s/server/manifests/
      • Monitor the progress of the installation: watch -c "kubectl get deployments -A"

        • The deployment is complete when all deployments (cert-manager, cert-manager-cainjector, cert-manager-webhook) show at least "1" as "AVAILABLE"

        • Use Ctrl+c to exit the watch loop after all pods are running

  2. Create the Helm Chart custom resource for SUSE Rancher:

    • Set the following variable to the hostname of the SUSE Rancher server instance

      HOSTNAME=""
      Note
      Note

      This hostname should be resolvable to an IP address of the K3s host, or a load balancer/proxy server that supports this installation of SUSE Rancher.

    • Create the SUSE Rancher Helm Chart custom resource manifest

      cat <<EOF> suse-rancher-helm-crd.yaml
      apiVersion: helm.cattle.io/v1
      kind: HelmChart
      metadata:
        name: rancher
        namespace: kube-system
      spec:
        chart: rancher
        targetNamespace: cattle-system
        repo: https://releases.rancher.com/server-charts/stable
        set:
          hostname: ${HOSTNAME}
      EOF
    • Apply the Helm Chart resource manifest:

      kubectl create namespace cattle-system
      sudo mv suse-rancher-helm-crd.yaml /var/lib/rancher/k3s/server/manifests/
      • Monitor the progress of the installation: watch -c "kubectl get pods -n cattle-system"

        • The installation is complete when all pods have a status of "Completed" or a status of "Running" with the number of "READY" pods being "1/1", "2/2", etc.

        • Use Ctrl+c to exit the watch loop after all pods are running

  3. (Optional) Create an SSH tunnel to access SUSE Rancher:

    Note
    Note

    This optional step is useful in cases where NAT routers and/or firewalls prevent the client web browser from reaching the exposed SUSE Rancher server IP address and/or port. This step requires that a Linux host is accessible through SSH from the client system and that the Linux host can reach the exposed SUSE Rancher service. The SUSE Rancher hostname should be resolvable to the appropriate IP address by the local workstation.

    • Create an SSH tunnel through the Linux host to the IP address of the SUSE Rancher server on the NodePort, as noted in Step 3:

      ssh -N -D 8080 user@Linux-host
    • On the local workstation web browser, change the SOCKS Host settings to "127.0.0.1" and port "8080"

      Note
      Note

      This will route all traffic from this web browser through the remote Linux host. Be sure to close the tunnel and revert the SOCKS Host settings when you’re done.

  4. Connect to the SUSE Rancher web UI and configure SUSE Rancher:

    • On the client system, use a web browser to connect to the SUSE Rancher service

    • Provide a new Admin password

      Important
      Important

      On the second configuration page, ensure the "Rancher Server URL" is set to the hostname specified when creating the SUSE Rancher HelmChart custom resource and the port is 443.

      • e.g., suse-rancher.sandbox.local:443

Deployment Consideration(s)

To further optimize deployment factors, leverage the following practices

  • Availability

    • In instances where a load balancer is used to access a K3s cluster, deploying two additional K3s cluster nodes, for a total of three, will automatically make SUSE Rancher highly available.

  • Security

    • The basic deployment steps described above are for deploying SUSE Rancher with automatically generated, self-signed security certificates. Other options are to have SUSE Rancher create public certificates via Let’s Encrypt associated with with a publicly resolvable hostname for the SUSE Rancher server, or to provide preconfigured, private certificates. See SUSE Rancher product documentation for more information.

  • Integrity

    • This deployment of SUSE Rancher uses the K3s etcd key/value store to persist its data and configuration, which offers several advantages. With a multi-node cluster and this resiliency through replication, having to provide highly-available storage isn’t needed. In addition, backing up the K3s etcd store protects the cluster as well as the installation of SUSE Rancher and permits restoration of a given state.

After this successful deployment of the SUSE Rancher solution, review the product documentation for details on how downstream Kubernetes clusters can be:

  • deployed ( refer to sub-section "Setting up Kubernetes Clusters in Rancher" ) or

  • imported ( refer to sub-section "Importing Existing Clusters" ), then

  • managed ( refer to sub-section "Cluster Administration" ) and

  • accessed ( refer to sub-section "Cluster Access" ) to address orchestration of workload, maintaining security and many more functions are readily available.

6 Summary

Using components and offerings from SUSE and the Rancher portfolio streamlines the ability to quickly and effectively engage in a digital transformation, taking advantage of cloud native resources and disciplines. Using such technology approaches lets you deploy and leverage transformations of infrastructure into a durable, reliable enterprise-grade environment.

Simplify

Simplify and optimize your existing IT environments

  • Using SUSE Rancher enables you to simplify Kubernetes cluster deployment and management of the the infrastructure components.

Modernize

Bring applications and data into modern computing

  • With SUSE Rancher, the digital transformation to containerized applications can extended, in a distributed computing context, tohhbenefit from the ability both to manage many target clusters, for each of the respective user bases and to facilitate the actual workload deployments.

Accelerate

Accelerate business transformation through the power of open source software

  • Given the open source nature of SUSE Rancher and the underlying software components, you can simplify management and make significant IT savings as you scale orchestrated, microservice deployments anywhere you need to and for whatever use cases are needed in an agile and innovative way.

7 References

White Papers
Websites

Glossary

  • Document Scope

    Reference Implementation

    A guide with the basic steps to deploy the highlighted components of the SUSE portfolio, including generalized pointers to other layers and elements. This is considered an introductory approach and a basis for other tested variations.

    Reference Architectures [7]

    A guide with the general steps to deploy and validate the structured solution components from both the SUSE and partner portfolios. This provides a shareable template of consistency for consumers to leverage for similar production ready solutions, including design considerations, implementation suggestions and best practices.

    Best Practice

    Information that can overlap both the SUSE and partner space. It can either be provided as a standalone guide that provides reliable technical information not covered in other product documentation, based on real-life installation and implementation experiences from subject matter experts or complementary, embedded sections within any of the above documentation types describing considerations and possible steps forward.

  • Factor(s)

    Automation [8]

    Infrastructure automation enables speed through faster execution when configuring the infrastructure and aims at providing visibility to help other teams across the enterprise work quickly and more efficiently. Automation removes the risk associated with human error, like manual misconfiguration; removing this can decrease downtime and increase reliability. These outcomes and attributes help the enterprise move towards implementing a culture of DevOps, the combined working of development and operations.

    Availability [9]

    The probability that an item operates satisfactorily, without failures or downtimes, under stated conditions as a function of its reliability, redundancy and maintainability attributes. Some major objectives to achieve a desired service level objectives are:

    • Preventing or reducing the likelihood and frequency of failures via design decisions within the allowed cost of ownership

    • Correcting or coping with possible component failures via resiliency, automated failover and disaster-recovery processes

    • Estimating and analyzing current conditions to prevent unexpected failures via predictive maintenance

    Integrity [10]

    Integrity is the maintenance of, and the insurance of the accuracy and consistency of a specific element over its entire lifecycle. Both physical and logical aspects must be managed to ensure stability, performance, re-usability and maintainability.

    Security [11]

    Security is about ensuring freedom from or resilience against potential harm, including protection from destructive or hostile forces. To minimize risks, one mus manage governance to avoid tampering, maintain access controls to prevent unauthorized usage and integrate layers of defense, reporting and recovery tactics.

  • Deployment Flavor(s)

    Proof-of-Concept [12]

    A partial or nearly complete prototype constructed to demonstrate functionality and feasibility for verifying specific aspects or concepts under consideration. This is often a starting point when evaluating a new, transitional technology. Sometimes it starts as a Minimum Viable Product ( MVP [13] ) that has just enough features to satisfy an initial set of requests. After such insights and feedback are obtained and potentially addressed, redeployments may be utilized to iteratively branch into other realms or to incorporate other known working functionality.

    Production

    A deployed environment that target customers or users can interact with and rely upon to meet their needs, plus be operationally sustainable in terms of resource utilization and economic constraints.

    Scaling

    The flexibility of a system environment to either vertically scale-up, horizontally scale-out or conversely scale-down by adding or subtracting resources as needed. Attributes like capacity and performance are often the primary requirements to address, while still maintaining functional consistency and reliability.

A Appendix

The following provide a bill of materials listing for the respective component layer(s) of the described deployment.

A.1 Compute Platform Bill of Materials

Recommended set of computing platform models, components and resources.

RoleQtySKUComponentNotes

System

1-3

n/a

  • Virtual Machine,

  • Single Board Computer (SBC) or

  • Industry Standard Server

Configuration

A.2 Software Bill of Materials

Recommended set of software, support and services.

RoleQtySKUComponentNotes

Operating System

1-3

874-007864

SUSE Linux Enterprise Micro,

  • x86_64,

  • Priority Subscription,

  • 1 Year

Configuration:

  • per node (up to 16 cores, stackable)

Kubernetes Management

1

R-0001-PS1

SUSE Rancher,

  • x86-64,

  • Priority Subscription,

  • 1 Year

Configuration:

  • per deployed instance

Rancher Management

2

R-0004-PS1

Rancher 10 Nodes

  • x86-64 or aarch64,

  • Priority Subscription,

  • 1 Year,

Configuration:

  • requires priority server subscription

Consulting and Training

1

R-0001-QSO

Rancher Quick Start,

  • Go Live Services

 
Note
Note

For the software components, other durations of support terms are also available.

A.3 Documentation Configuration / Attributes

This document was built using the following AsciiDoc and DocBook Authorting and Publishing Suite ( DAPS ) attributes:

Appendix=1 ArchOv=1 Automation=1 Availability=1 BP=1 BPBV=1 CompMod=1 DepConsiderations=1 Deployment=1 FCTR=1 FLVR=1 GFDL=1 Glossary=1 HWComp=1 HWDepCfg=1 Integrity=1 LN=1 PoC=1 Production=1 RA=1 RI=1 References=1 Requirements=1 SWComp=1 SWDepCfg=1 Scaling=1 Security=1 env-daps=1 focusRancher=1 iK3s=1 iRKE1=1 iRKE2=1 iRMT=1 iRancher=1 iSLEMicro=1 iSLES=1 iSUMa=1 layerK3s=1 layerSLEMicro=1

9 GNU Free Documentation License

Copyright © 2000, 2001, 2002 Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

0. PREAMBLE

The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

1. APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.

A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document’s overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.

The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.

A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work’s title, preceding the beginning of the body of the text.

A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.

The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.

2. VERBATIM COPYING

You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies.

3. COPYING IN QUANTITY

If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document’s license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.

4. MODIFICATIONS

You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

  1. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.

  2. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement.

  3. State on the Title page the name of the publisher of the Modified Version, as the publisher.

  4. Preserve all the copyright notices of the Document.

  5. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.

  6. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.

  7. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document’s license notice.

  8. Include an unaltered copy of this License.

  9. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.

  10. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.

  11. For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.

  12. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.

  13. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version.

  14. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.

  15. Preserve any Warranty Disclaimers.

If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version’s license notice. These titles must be distinct from any other section titles.

You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties—​for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.

5. COMBINING DOCUMENTS

You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".

6. COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.

7. AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation’s users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document’s Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.

8. TRANSLATION

Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.

If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.

9. TERMINATION

You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

10. FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.

Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.

ADDENDUM: How to use this License for your documents

Copyright (c) YEAR YOUR NAME.
   Permission is granted to copy, distribute and/or modify this document
   under the terms of the GNU Free Documentation License, Version 1.2
   or any later version published by the Free Software Foundation;
   with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
   A copy of the license is included in the section entitled “GNU
   Free Documentation License”.

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “ with…​Texts.” line with this:

with the Invariant Sections being LIST THEIR TITLES, with the
   Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.

If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.

Print this page