Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fleet: Add created-by to workload resources #13189

Open
manno opened this issue Jan 23, 2025 · 0 comments
Open

Fleet: Add created-by to workload resources #13189

manno opened this issue Jan 23, 2025 · 0 comments
Assignees
Labels
area/fleet JIRA kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@manno
Copy link
Member

manno commented Jan 23, 2025

Internal ref: SURE-7092

Users are unable to tell who created which GitRepo and when looking at deployed workloads, it's equally unclear whom they belong to.

Idea:

  • UI adds user/displayname label to created GitRepos
  • Fleet copies those labels onto bundles, etc. (this already works)
  • UI can show the created-by name in resource views

Label names to use, https://fleet.rancher.io/ref-configuration#labels :

fleet.cattle.io/created-by-user-id
fleet.cattle.io/created-by-display-name
@manno manno changed the title Add created-by to workload resources? [SURE-7092] Add created-by to workload resources? Jan 23, 2025
@torchiaf torchiaf self-assigned this Jan 23, 2025
@torchiaf torchiaf transferred this issue from rancher/fleet Jan 23, 2025
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Jan 23, 2025
@torchiaf torchiaf changed the title [SURE-7092] Add created-by to workload resources? Fleet: Add created-by to workload resources Jan 23, 2025
@torchiaf torchiaf added this to the v2.11.0 milestone Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/fleet JIRA kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
Status: To Triage
Development

No branches or pull requests

2 participants