KAS setup is broken in v16.11.1, v16.10.4, and v16.9.6 upgrade
On the 3k architecture of GitLab v16.9.3, we could able to register a Kubernetes cluster.
After update of GitLab with latest release v16.11.1, the Agent could not be accessible any more.
{width="779" height="84"}
We have figured out how the multiple KAS nodes have to be configured within the cluster architecture, and a dedicated solution was found just 1 week ago (Apr 18th 2024)
[Unable to connect a kubernetes cluster in 3k GitLab architecture(multiple nodes)](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/8480 "Unable to connect a kubernetes cluster in 3k GitLab architecture(multiple nodes)")
KAS server is running, and port 8150-8155 on the rails server listen the protocols, correctly
Are there some change on the KAS configuration?
## The Problem
The following KAS patch releases contain ~"breaking change" from the %"17.0" revision, because they have been tagged from the wrong source (`master` instead of stable branches):
- `v16.11.1`
- `v16.10.4`
- `v16.9.6`
See for context:
- https://gitlab.com/gitlab-org/gitlab/-/issues/458462#note_1883585482
- https://gitlab.com/gitlab-org/gitlab/-/issues/458462#note_1884622114
## Workaround
- Downgrade KAS:
- `v16.11.1` -> `v16.11.0`
- `v16.10.4` -> `v16.10.1` (note the jump in the patch component! Jump is due to the KAS <-> GitLab version alignment)
- `v16.9.6` -> `v16.9.3` (note the jump in the patch component! Jump is due to the KAS <-> GitLab version alignment)
Use [this procedure](https://gitlab.com/gitlab-org/gitlab/-/issues/458462#note_1887669590) for Docker and Omnibus installations if you need to unblock asap.
The next GitLab patch release will fix those changes.
issue