Skip to content

🚀 Argocd: Add optional ingress link in argocd views #7646

@dfl-aeb

Description

@dfl-aeb

Workspace

argocd

🔖 Feature description

Add optional ingress link access in the ArgoCD deployment views, so users can open app endpoints directly from the UI (while keeping the existing ArgoCD application link).

🎤 Context

Today, the ArgoCD plugin view provides quick access to the ArgoCD app itself, but not to the actual ingress endpoints exposed by the deployed application.
For day-to-day operations, users often want both:

  • open the ArgoCD app (for sync/health/debugging), and
  • open the application endpoint (ingress URL) directly.
    Having ingress links available in the same place would reduce context switching and improve usability for platform/dev teams reviewing deployments.

I built a small experimental UI prototype with AI support and attached a screenshot for discussion.

Image Image

✌️ Possible Implementation

Keep the current ArgoCD link unchanged.

  • Add a separate ingress action in the deployment UI (same area as the existing app actions).
  • If multiple ingress URLs are available, show them via a compact dropdown/list.
  • Display the URL itself in the list (not only a resource name), so users can clearly see where they are navigating.

Would this direction be acceptable for the project before preparing a formal PR?

👀 Have you spent some time to check if this feature request has been raised before?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

Are you willing to submit PR?

Yes I am willing to submit a PR!

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions