---
title: "Air-Gapped"
description: "1 posts about Air-Gapped, summarised, each linking to the original."
---

# Air-Gapped
> 1 posts about Air-Gapped, summarised, each linking to the original.

## Articles

### [Scale OpenShift Dev Spaces in air-gapped environments](https://yomu.fyi/post/scale-openshift-dev-spaces-in-air-gapped-environments.md)
- Company: [Red Hat](https://yomu.fyi/company/red-hat.md)
- Author: Ajay Kanse
- Published: Oct 16, 2026
- Type: Problem & solution

Scaling OpenShift Dev Spaces in air-gapped environments requires addressing four friction points: third-party monitoring agents, rootless container runtimes, custom install namespaces, and admission webhooks. Dynatrace OneAgent sidecar conflicts are resolved by labeling all Dev Spaces namespaces with dynatrace.com/inject: “false” to prevent init container injection. Rootless Podman inside workspace pods needs user namespace UID/GID ranges respecting a 65,536 UID ceiling; UDI 3.22 requires a manual script with a corrected range, while UDI 3.26 handles mapping automatically. Stale admission webhooks from a previous operator install namespace must be manually deleted before reinstalling into a different namespace to avoid conflicting definitions. A readiness checklist includes mirroring operator catalogs, deploying an internal Open VSX server with PostgreSQL, configuring PKI trust via ConfigMap, and disabling the default devfile registry.