.png?width=2654&height=829&name=RGS_Vector_Logo-01%20(002).png "RGS_Vector_Logo-01 (002)"){kind=logo}
New NeuVector Classification Support
Recently the NeuVector team released NeuVector version 5.2. This new feature added some much-needed features for our Government customers. This post will walk through those features and how to implement them.
Learn
New to containers or looking to expand your knowledge? Our RGS team shares detailed product insights and relevant customer experiences in our resource library to support you on your Kubernetes journey.
Search
Posts by:
Andy Clemenko
Taking Advantage of Encryption at Rest with Longhorn
Data security is becoming increasingly important to our customers. One of the great features of Longhorn is the ability to encrypt the volumes at rest. This blog is all about how to do that. Encrypting data volumes at rest means the data on the nodes is encrypted. For added security, we will want at least three nodes for high availability.
Read More
How to Air Gap RKE2, Neuvector, Longhorn, and Rancher
This guide is very similar to Simple RKE2, Neuvector, Longhorn, and Rancher Install , except in one major way. This guide will provide a strategy for air gapping all the bits needed for RKE2, Longhorn and Rancher. This is just one opinion. We are starting from the idea that there is no container infrastructure available.
Simple RKE2, Longhorn, and Rancher Install
Throughout my career there has always been a disconnect between the documentation and the practical implementation. The Kubernetes (k8s) ecosystem is no stranger to this problem. This guide is a simple approach to installing Kubernetes and some REALLY useful tools. We will walk through installing all the following.
Leveraging RKE2 with TLS Passthrough
What did I do?
As a new engineer at Rancher Federal (Suse Rancher Government Solutions) I wanted to setup Keycloak with TLS Passthrough on my shinny new RKE2 cluster. For the uninitiated TLS Passthrough is a way for the ingress or proxy to all TLS to passthrough. Meaning the pod itself will terminate TLS and not the ingress/proxy. RKE2 is fantastic that it ships with Nginx Ingress. There are a few other options out there on the market for ingress. Another favorite is Traeifk. But for this cluster I wanted to use the built in pieces. Nginx it is!