Automate Tagging and Release of `aws/karpenter` and `aws/karpenter-core`

[jonathan-innis]

Tell us about your request

Currently, releasing a newer version of Karpenter, requires that we first tag the same version that we are releasing with in karpenter-core, then bump the version of karpenter-core in the karpenter go.mod to be the tagged version, then tag the version that we are releasing in karpenter to complete the release process.

We should automate this process so that kicking off a release involves starting a GH workflow for a release version which:

1. Tags the version in karpenter-core
2. Bumps the version of karpenter-core to the tagged version in the karpenter go.mod
3. Tags the version in karpenter
4. Create release notes that contains a link to the karpenter-core release notes for the same version.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?

N/A

Are you currently working around this issue?

N/A

Additional Context

No response

Attachments

No response

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[ringtail]

what is the difference between karpenter and karpenter-core?

[jonathan-innis]

Karpenter is the AWS-specific version of Karpenter and has the AWS cloudprovider inside of it. Karpenter-core is meant for any common packages and common controllers that we expect to run across all cloudprovider versions of karpenter.