Not clear where the helm stable versions are about karpenter-provider-aws HOT 6 CLOSED

I see, got it. That's outdated wording, I'll cut an update. As of last September, all new releases published to the public ECR are stable. We used to publish our snapshot releases to the public ECR as well, those would be tagged with their git hash.

from karpenter-provider-aws.

The v prefix was dropped from the chart release tag starting at 0.35.0 (ref). This was done to comply with semver and improve compatibility with tools that rely on that compliance (e.g. helm semver ranges). This change only affected the tags in the OCI repo, not anywhere else. This is reflected in the current version of the Karpenter Getting Started Guide.

from karpenter-provider-aws.

Thanks @jmdeal for your quick reply and for clarifying it.
So the concept ofstable versions also went away, and I can use whatever is new and it should be ok, right?
Thanks again for the quick help.

from karpenter-provider-aws.

I'm not sure what you mean by stable versions, could you clarify?

from karpenter-provider-aws.

Hi @jmdeal , I apologies I was referring to stable releases not versions, it is about this -> https://karpenter.sh/docs/upgrading/compatibility/
in the paragraph:

Stable Releases
Stable releases are the most reliable releases that are released with weekly cadence. Stable releases are our only recommended versions for production environments. Sometimes we skip a stable release because we find instability or problems that need to be fixed before having a stable release. Stable releases are tagged with a semantic version prefixed by a v. For example v0.13.0

Thanks again!

from karpenter-provider-aws.

Awesome, thank you @jmdeal !

from karpenter-provider-aws.