🐛 Fix AWSManagedClusterTemplate short name

[alexander-demicev]

What type of PR is this?
/kind bug

What this PR does / why we need it:

Fix AWSManagedClusterTemplate short name. The current short name conflicts with CAPZ, making it impossible to install the latest CAPA version on the same management cluster as CAPZ.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist:

• squashed commits
• includes documentation
• includes emoji in title
• adds unit tests
• adds or updates e2e tests

Release note:

action required
The short name for AWSManagedClusterTemplate has changed from amct to awsmct. If you have any automation that relies on the short name it will needf to be updated.

[richardcase]

/cherry-pick release-2.9

[k8s-infra-cherrypick-robot]

@richardcase: once the present PR merges, I will cherry-pick it on top of release-2.9 in a new PR and assign it to you.

In response to this:

/cherry-pick release-2.9

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.

[richardcase]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 5cea11b8a66bc0d8fccdc3d54e8737eb1de743af

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: richardcase

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:

• OWNERS [richardcase]

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

[damdo]

Aha, fun.

We should probably add an action required section about this in the release notes, warning the user that if they have any scripts or automation using this shortname they should update it.

I'd start the release-note comment with a single line at the top saying, and describe this

action required

[damdo]

/hold

For release note change

[furkatgofurov7]

@richardcase @damdo hey,

When can we expect a new patch release including this fix? We are pretty much close to our deadlines and bumped CAPA recently to 2.9.0 which uses CAPI v1.10.x series, so definitely would like to keep supporting newer CAPI if possible (and that needs a new CAPA patch release with this changes) and avoids a downgrade on our side.

[richardcase]

I can do the release tomorrow morning when the cherry pick merged

[furkatgofurov7]

/lgtm

[richardcase]

/release-note-edit

action required
The short name for AWSManagedClusterTemplate has changed from amct to awsmct. If you have any automation that relies on the short name it will needf to be updated.

[richardcase]

/unhold

[k8s-infra-cherrypick-robot]

@richardcase: new pull request created: #5663

In response to this:

/cherry-pick release-2.9

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.