add maintainers for charts

[lerrigatto]

What this PR does / why we need it:

We need (preliminary) maintainers for the charts repo.
My plan is to add the bare minimum to the repo (readme, codeowners) and start opening issues to discuss the implementation of the charts design doc: kubevirt/community#224
And, obviously, to write the charts :)

The charts repo have been created recently: #4093

I have added a new group for charts maintainers, I added @dhiller and myself but it doesn't need to be. Please let me know who should be in that list instead.
I added the repo to the release team, as for sure it's going to be related to them.

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• Design: A design document was considered and is present (link) or not required
• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• Community: Announcement to kubevirt-dev was considered

[kubevirt-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[lerrigatto]

@dhiller

[sourcery-ai]

Hey @lerrigatto - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[lerrigatto]

CC @atanasdinov you spent a lot of time writing the design doc, do you want to open the VEP and track the work on the charts? https://github.com/kubevirt/enhancements/issues
Also should I add you to the repo maintainers?

[atanasdinov]

CC @atanasdinov you spent a lot of time writing the design doc, do you want to open the VEP and track the work on the charts? https://github.com/kubevirt/enhancements/issues Also should I add you to the repo maintainers?

Yes, I'll do it. As mentioned offline, I've been really busy over the last couple of weeks but I'll find a slot to go through the VEP process and create an initial draft of the chart that we can start reviewing and polishing.

Thanks for starting this!

[lerrigatto]

{"component":"peribolos","level":"fatal","msg":"Configuration failed: failed to configure kubevirt team charts-maintainers repos: failed to list team 0(charts-maintainers) repos: return code not 2XX: 404 Not Found","severity":"fatal","time":"2025-05-26T19:47:32Z"}

And that isn't how you add teams :D
I will try to rtfm and fix this next week.

[dhiller]

@lerrigatto thanks - one change request inline, other than that it looks great!

Note that at some point we should add an OWNERS file to the charts repo.

[dhiller]

/approve

Thank you @lerrigatto !

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhiller

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [dhiller]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dhiller]

/override pull-kubevirt-org-github-config-updater

As the team doesn't exist this is an expected failure.

[kubevirt-bot]

@dhiller: Overrode contexts on behalf of dhiller: pull-kubevirt-org-github-config-updater

Details

In response to this:

/override pull-kubevirt-org-github-config-updater

As the team doesn't exist this is an expected failure.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.