argoproj / argoproj/argo-workflows
Support for Dynamic Node References in Links feature
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
Summary
Currently, Argo Workflows Links feature doesn't support dynamic node references within the workflow.status.nodes object.
Users cannot create links that reference specific node information (like hostNodeName).
This feature request is based on the discussion: https://github.com/argoproj/argo-workflows/discussions/14838
Use Cases
Link to Grafana/monitoring dashboards filtered by the specific node where a pod is running
Message from the maintainers:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Argo Workflows Links feature implementation and read discussion 14838 for the proposed behavior. Trace how workflow.status.nodes values are resolved, then define how dynamic references such as hostNodeName should work in generated links. Done means links can target node-specific monitoring information, with coverage for the supported reference behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100