Document what is and what is not supported with KAS -> agentk

We are currently in the process of introducing KAS -> agentk connectivity, see Support kas->agent connections (#496 - closed).

This is mostly to support use cases where KAS (GitLab) is behind a firewall and agentk isn't able to connect to it directly. For example, GitLab is inside a corporate network and agentk is running in a cloud environment.

Supporting this connectivity direction enables us to fully remove support for certificate-based agents - which is nice.

However, these agents won't be able to make full use of the Flux features that we offer because Flux currently directly connects to GitLab. This includes simply pulling a Git repository or OCI artifact, but also impacts the Dashboard for Kubernetes features which are based on the aforementioned Flux setup.

Ideas

  • Support proxying GitLab API traffic through the agent.
  • Other proxying solutions?
  • Others?
Edited by Timo Furrer