Gangway

Gangway guided users through signing in to a Kubernetes cluster using an existing OpenID Connect identity provider. It helped them obtain credentials and configure kubectl, the command-line client, without an administrator manually preparing every user's setup. It was a login helper, not the identity provider or the rules controlling cluster access. Since development has ended, replacement should preserve that identity mapping and authorization while changing the user-facing login process.

Deployment and operating notes

The Gangway repository now states that VMware ended active development and that it will no longer be updated. Gangway helped users obtain OIDC credentials and configure kubectl; it was not the identity provider or the Kubernetes authorization policy. Those components can remain in use while the login experience changes.

Inventory issuer URL, client IDs, redirect URIs, username and group claims, refresh-token behavior and generated kubeconfigs. Evaluate a supported OIDC client or cluster access tool against the API server’s current authentication configuration. Test login, expiry and refresh for ordinary users, then verify RBAC with both permitted and denied operations. Keep an independently tested administrator access path before changing issuer or claim mappings. Existing downloaded kubeconfigs may keep pointing at old credentials or helpers, so document how users replace them. A new login UI does not automatically migrate sessions or fix overly broad group bindings. No universal drop-in Gangway replacement was proved in this review.