[PROPOSAL] Move damdo to maintainer

[richardcase]

GitHub handle

damdo

Action

Add

Merge date

29th November 2025

Reason for change

Damiano has been contributing to CAPA for quite some time. His contributions include code, reviews, community engagement in slack. He also attends almost every office hours.

He has shown commitment to the project and therefore I would like to propose he move to be a maintainer.

@damdo - thank you for your contributions to CAPA and also to CAPI in general. The project and its community is better for having you involved.

🖱️Tasks

Tasks to be done

• Update cluster-api-aws-maintainers section in OWNER_ALIASES in CAPA repo
• Create a PR with the change and add /hold
• Announce the change in the CAPA slack channel
• Add PSA in the notes doc for the next CAPA office hours
• After the lazy consensus review period remove the hold
• Update cluster-api-provider-aws-maintainers team in this file
• Update approvers for CAPA jobs here
• Update approvers from CAPA image promotion here
• Update k8s-infra-staging-cluster-api-aws@kubernetes.io here
• Update sig-cluster-lifecycle-cluster-api-aws-alerts@kubernetes.io here

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[damdo]

Thanks for the kind words @richardcase

[dlipovetsky]

+1

Thank you for all you do, @damdo!

[richardcase]

One thing we need to be careful of is the balance of the maintainers from different companies.