Hey everyone! I just got back from KubeCon and had the chance to connect with some folks who are also dealing with clusters in airgapped environments. I found the talks really interesting and it was great to hear about all the innovative possibilities out there, but many of them didn't quite relate to our specific situations. I'm curious – did anyone else find the conference valuable for topics relevant to airgapped setups? And are there other niche conferences that focus specifically on airgapped solutions?
5 Answers
I missed KubeCon, but I'm currently working on a fully airgapped Kubernetes setup. My main challenge is syncing OCI artifacts across different versions. It's definitely tricky, but it’s been a fun project so far.
You might want to consider using Harbor; it's been invaluable for managing images in almost airgapped systems. We push images to Harbor with self-hosted runners and then pull from there.
There were definitely some airgap-related discussions on Edge Day, especially one regarding manufacturing. And the Telco co-hosted sessions touched on networking challenges for airgapped scenarios. It's true, not everything can be applied, but some insights were quite helpful.
Being on the vendor side, I've noticed a real demand for airgapped solutions, but I didn’t see much discussion about it in the talks. Still, my conversations with people at the conference were super enlightening.
I know there was at least one talk at Rejekts that was specifically about airgapped setups. It seems like most vendors are still focused on SaaS solutions, but quite a few of the talks provide useful insights for airgapped environments.
Yes, I did find some talks that were quite relevant! There were discussions on GPU usage and network traffic analysis with Cilium that hit close to home for me. The DRA talk was also interesting, and while most talks only skimmed the surface, I still managed to glean some useful insights.
Have you checked out Zarf? It sets up a container registry and a Gitea repo in your cluster, and it smartly redirects image requests to your local registry!