How to Effectively Handle Air-Gapped Kubernetes Deployments?

We developed an in-house tool that creates an archive file from a functioning cluster, allowing easy transitions between versions in air-gapped systems. It's essential to ensure everything is documented well, so the client knows how to proceed with updates.

Using Rancher with RKE2 works wonders for setting up air-gapped clusters, making provisioning much smoother. Just ensure you have a solid process in place for deployments.

You might want to explore tools like Defence Unicorn's Zarf, which help package dependencies neatly for deployment. It streamlines the process significantly, especially for air-gapped setups.

I wouldn't advise bundling Kubernetes because it can become incredibly complex with various hardware and software setups. Instead, ship just your application. Have customers manage their own Kubernetes installations to avoid overwhelming support issues later on. Also, make sure clients provide their own image registry, and remember to package your Docker images correctly before handing it all over.

To handle packaging and transferring container images and dependencies, it's best to use a private on-premises registry with limited internet access for updates. Without it, managing everything will get chaotic very quickly. You can check out the RKE2 documentation for some guidance on airgap installations. As for Kubernetes, it usually depends on your contract with the customer — both bundling and client installations are valid approaches.