Introduction to Rancher

Yes, basic Kubernetes knowledge is required. You should be familiar with Pods, Deployments, Services, and Namespaces, and be comfortable using kubectl. Rancher experience is not required, we build that from scratch.

Preparation: Our Kubernetes fundamentals training (DW2) provides the ideal foundation. It covers exactly the concepts we build upon in the Rancher workshop.

Kubernetes is the container orchestration platform, Rancher is the management layer on top. Kubernetes provides the infrastructure (Pods, Services, Volumes), while Rancher adds what Kubernetes lacks:

• A central UI for multiple clusters simultaneously
• Integrated user management with RBAC and LDAP/Active Directory integration
• An app marketplace with preconfigured Helm charts
• GitOps via Fleet for automated multi-cluster deployments
• Dedicated components like Longhorn (storage) and RKE2/K3s (Kubernetes distributions)

In short: Kubernetes runs containers, Rancher makes operating multiple Kubernetes clusters manageable. Our Kubernetes fundamentals workshop (DW2) teaches the K8s foundation, this workshop shows how Rancher builds on it.

Rancher plays to its strengths with two groups in particular: teams with multi-cluster needs and teams that want to rely on open source.

Multi-cluster across different environments: Rancher runs on top of existing CNCF-compliant clusters and lets you choose the distribution (RKE2, K3s, or cloud-managed). You manage on-premises, cloud, and edge clusters from a single interface and also import managed cloud clusters (AKS, EKS, GKE). OpenShift, by contrast, is its own distribution that replaces vanilla Kubernetes.

Open source instead of a subscription: Rancher Manager is open source (Apache 2.0) and free even in production. OpenShift requires a Red Hat subscription. If you need flexibility in infrastructure and licensing, Rancher is usually the better fit.

OpenShift shines where a closed platform with integrated CI/CD and the Red Hat ecosystem is required. In the workshop, we compare the architectural differences so you can make an informed decision.

Rancher Manager is open source (Apache 2.0) and free to use, including in production. Rancher Prime is SUSE's enterprise offering with commercial support, extended security features, and certified builds.

In practice: For getting started and many production scenarios, the open-source version is sufficient. Rancher Prime becomes relevant when you need SLAs for support, require FIPS-certified builds, or your compliance team demands a vendor contract. The features are identical; the difference lies in support and certification.

In the workshop, we work with the open-source variant and show where Rancher Prime adds value. This way, you can make an informed internal case for whether your team needs the open-source or enterprise version.

Yes, Rancher can import and centrally manage both self-provisioned clusters and managed cloud clusters (AKS, EKS, GKE). You configure Cloud Credentials in Rancher, import the cluster, and manage workloads, RBAC, and monitoring through the same interface as your on-premises clusters.

This is one of the key advantages for teams with hybrid or multi-cloud setups: a unified management interface regardless of whether the cluster runs on AWS, Azure, GCP, or in your own data center. In the workshop, you practice both provisioning new clusters and importing existing clusters into your Rancher Manager.

Both are Kubernetes distributions from Rancher/SUSE, but with different focus areas:

RKE2 is the enterprise distribution focused on security and compliance: FIPS 140-2 support, CIS hardening out of the box, Canal as default CNI. Typical use: regulated environments, data centers, production.

K3s is lightweight (single binary, ~100 MB RAM), uses Flannel as default CNI, and is suited for edge scenarios, IoT, CI/CD runners, and smaller environments.

Commonalities: Both are CNCF-certified, use containerd as runtime, and can be centrally managed through Rancher Manager. In the workshop, you set up both distributions and compare installation process, resource footprint, and bundled components. This way, you can make an informed decision in your projects about which distribution fits which scenario.

All practical exercises take place in the DevNinjas Dojo, our browser-based cloud learning environment. Every participant receives dedicated resources: own Kubernetes clusters, VMs, containers (depending on the workshop topic). You work not in a shared environment, but have full control over your own infrastructure.

Benefits:

• Your own clusters & servers: You get dedicated resources for your exercises
• No software installation required: Everything runs in your browser
• Works everywhere: Even in strict enterprise networks with VPN, proxy, and firewalls
• Open protocols: SSH, HTTPS, standardized web terminals (no proprietary client)
• Ready immediately: Login and start with the exercise right away

You only need a modern browser (Chrome, Firefox, Edge) and internet access. The Dojo is available to you throughout the entire workshop.

Yes, upon completion you will receive an official certificate of attendance from DevNinjas as PDF. This confirms your successful participation and the topics covered. The certificate is perfect for conversations with your employer and your personnel file.

Additionally, you will receive a verified digital badge that you can directly embed in your LinkedIn profile (section "Licenses & Certifications"). The badge follows the Open Badges 2.0 standard and is verifiable via QR code at any time. This way you showcase your qualification and position yourself with recruiters.

Yes, all our workshops are also available as corporate training. We tailor content, duration and focus to the needs of your team.

Corporate trainings take place either on-site or remote. Submit your individual request and we will prepare an offer for you.