Skip to content

Conversation

@jan-mrm
Copy link
Contributor

@jan-mrm jan-mrm commented Jan 23, 2026

This implements that the HTTPRoute of gateway.networking.k8s.io/v1 is picked up in the network view of the ArgoCD UI and also adds auto generation of external links to the resource (so the clickable links in the UI, similar to what is done for Ingress).

Implementation details and open questions:

  1. HTTPRoute fits generally into the implementation schema. The only downside is that we cannot determine wether its http or https, since that information is only present in the referenced Gateway resource. My assumption is that accessing another resource can / should not be done? I did not try it but I'm not sure how it would work with the permissions even. Also the referenced Gateway could be in another namespace.
    So in the implementation I just assume https. A user could add another links using the general external-link annotation.

  2. Gateway is not added here since, at least to my understanding, it needs more refactoring or discussion. The HTTPRoute references a Gateway which does not fit into the TargetRefs.
    TargetLabels and Labels is for the connection between Service and Pod.

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Title of the PR
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

closes #17087 at least partially depending on the scope (HTTPRoute is added, Gateway is not)

Screenshot:
screenshot-network-view

… auto generate)

Signed-off-by: jan-mrm <67435696+jan-mrm@users.noreply.github.com>
@jan-mrm jan-mrm requested a review from a team as a code owner January 23, 2026 13:56
@bunnyshell
Copy link

bunnyshell bot commented Jan 23, 2026

🔴 Preview Environment stopped on Bunnyshell

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

  • 🔵 /bns:start to start the environment
  • 🚀 /bns:deploy to redeploy the environment
  • /bns:delete to remove the environment

Signed-off-by: jan-mrm <67435696+jan-mrm@users.noreply.github.com>
Signed-off-by: jan-mrm <67435696+jan-mrm@users.noreply.github.com>
Signed-off-by: jan-mrm <67435696+jan-mrm@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support Gateway API in network view

1 participant