-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[aws-eks] Cluster Version Pinning #7762
Labels
@aws-cdk/aws-eks
Related to Amazon Elastic Kubernetes Service
effort/small
Small work item – less than a day of effort
feature-request
A feature should be added or improved.
Milestone
Comments
pahud
added
feature-request
A feature should be added or improved.
needs-triage
This issue or PR still needs to be triaged.
labels
May 3, 2020
Yes, this is exactly what I was thinking. We should get make If we want a nice experience we can offer an extensible enum-like type, which is a common pattern we use: export class KubernetesVersion {
public static of(version: string) { return new KubernetesVersion(version); }
public static V1_14 = KubernetesVersion.of("1.14");
public static V1_15 = KubernetesVersion.of("1.15");
private constructor(public readonly version: string) { }
} Then, usage is: new Cluster(this, 'MyCluster', {
version: KubernetesVersion.V1_14,
// or, if I want to use a version that is not defined in the "enum":
version: KubernetesVersion.of("1.99")
} |
@eladb Let me make it :-) |
eladb
changed the title
EKS cluster version pinning
[EKS Feature] cluster version pinning
Jun 24, 2020
Nice to see this one 👍 |
eladb
changed the title
[EKS Feature] cluster version pinning
[EKS Feature] Cluster Version Pinning
Jun 24, 2020
PR WIP. Will create a PR draft today. |
mergify bot
pushed a commit
that referenced
this issue
Jul 3, 2020
feat(eks): support cluster version pinning Support cluster version pinning with the mandatory `version` property in the `Cluster` construct. Fixes: #7762 BREAKING CHANGE: `version` is now a mandatory property ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
iliapolo
changed the title
[EKS Feature] Cluster Version Pinning
[aws-eks] Cluster Version Pinning
Aug 16, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
@aws-cdk/aws-eks
Related to Amazon Elastic Kubernetes Service
effort/small
Small work item – less than a day of effort
feature-request
A feature should be added or improved.
The
Cluster
resource in the eks construct library allows us to create Amaozn EKS cluster without specifying theversion
, however, when we create self-managed ASG nodegroup we need specify the version before we can construct correct ssm parameter store path for the AMI, which at this moment will honor the hardcodedLATEST_KUBERNETES_VERSION
variable. However, if we version bumpLATEST_KUBERNETES_VERSION
, users with existing cluster and nodegroup will risk upgrading their self-managed nodegroup k8s version. For example1.14
to1.15
or even1.14
to1.16
, while their cluster may remain1.14
.However, for the
Nodegroup
resource, we don't have to specify the version as cloudformation will determine the version from the cluster, which ensures the version consistency.I guess we might need to make the version property mandatory for
Cluster
and let users determine the version for their cluster as well as self-managed nodegroups if any.Benefits
version
Use Case
Proposed Solution
Other
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: