Update CAPI v1.9 release team members

[Sunnatillo]

New CAPI v1.9 RT members announced here: https://kubernetes.slack.com/archives/C8TSNPY4T/p1723216277709389

This PR removes old and adds new v1.9 RT members from/to the list in alphabetical order.

Part of kubernetes-sigs/cluster-api#11092

[k8s-ci-robot]

Welcome @Sunnatillo!

It looks like this is your first PR to kubernetes/community 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/community has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @Sunnatillo. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[cahillsf]

many of these users don't appear to be mapped in users.yaml. you will need to update the list to map their GH IDs to their slack user IDs: #7645

[Sunnatillo]

many of these users don't appear to be mapped in users.yaml. you will need to update the list to map their GH IDs to their slack user IDs: #7645

Thank your for the review.
Added users to user.yaml file.

[Sunnatillo]

@sbueringer @fabriziopandini

[cblecker]

/ok-to-test

[fabriziopandini]

/lgtm

[Sunnatillo]

@jeefy @mrbobbytables
Could we merge this please?

[Sunnatillo]

@alejandrox1 @coderanger @munnerz @DylanGraham @jberkus
Could we merge this please?

[fabriziopandini]

cc @MadhavJivrajani @palnabarun if you have some spare time

[jberkus]

/approve

In the future, can ClusterAPI have a file somewhere in your repo with the release team members? Slack messages are emphemeral.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jberkus, Sunnatillo

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

The pull request process is described here

Needs approval from an approver in each of these files:

• communication/slack-config/OWNERS [jberkus]

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

[sbueringer]

/approve

In the future, can ClusterAPI have a file somewhere in your repo with the release team members? Slack messages are emphemeral.

Not sure if I have full context, we have the list here https://github.com/kubernetes-sigs/cluster-api/blob/main/OWNERS_ALIASES#L120

[sbueringer]

And here with slack handles https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/releases/release-1.9.md#release-team