Skip to content
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

List Supported K8s Versions #2040

Closed
shivasuri opened this issue Apr 15, 2020 · 4 comments · Fixed by #2126
Closed

List Supported K8s Versions #2040

shivasuri opened this issue Apr 15, 2020 · 4 comments · Fixed by #2126
Labels
good first issue Good for newcomers help wanted Extra attention is needed kind/feature New feature or request

Comments

@shivasuri
Copy link

Before creating a feature request, please search existing feature requests to see if you find a similar one. If there is a similar feature request please up-vote it and/or add your comments to it instead

Why do you want this feature?
A clear and concise description of why you want this feature. Include use-cases and any specific constraints you may have.

Dynamically creating clusters for daily builds across several k8s versions.

What feature/behavior/change do you want?
A clear and concise description of the change you would like to see in eksctl.

Do not hesitate, when appropriate, to share the exact commands or API you would like, and/or to share a diagram (e.g.: asciiflow.com): "a picture is worth a thousand words".

Just something as simple as eksctl list-k8s-versions

@shivasuri shivasuri added the kind/feature New feature or request label Apr 15, 2020
@shivasuri
Copy link
Author

shivasuri commented Apr 15, 2020

here is a hacky way to get the list for anyone who wants it:
echo $(eksctl create cluster --version invalid 2>&1) | rev | sed 's/ //g' | cut -d ":" -f-1 | rev

@martina-if martina-if added good first issue Good for newcomers help wanted Extra attention is needed labels Apr 22, 2020
@smrutiranjantripathy
Copy link
Contributor

smrutiranjantripathy commented Apr 30, 2020

I'm doing research on this issue. Would like to submit a PR.
I'm thinking of creating a new command under eksctl get as
eksctl get supportedk8sversions and maintaining the supported versions in a file in the repository. Please suggest your opinion on this approach.

@sayboras
Copy link
Contributor

sayboras commented May 1, 2020

eksctl get supportedk8sversions and maintaining the supported versions in a file in the repository. Please suggest your opinion on this approach.

For your list of supported version, you can refer to https://github.com/weaveworks/eksctl/blob/master/pkg/apis/eksctl.io/v1alpha5/types.go#L297.

For the command, in my opinion existing eksctl version can be used to show supported kube versions (e.g. breaking down by eksctl client version and EKS server supported version)

smrutiranjantripathy added a commit to smrutiranjantripathy/eksctl that referenced this issue May 3, 2020
This change was made to list the EKS Server Supported Versions. Added the functionality for eksctl version command to show the EKS server supported versions in a new line.

Issue eksctl-io#2040
smrutiranjantripathy added a commit to smrutiranjantripathy/eksctl that referenced this issue May 3, 2020
This change was made to list the EKS Server Supported Versions. Added the functionality for eksctl version command to show the EKS server supported versions in a new line.

Issue eksctl-io#2040
@smrutiranjantripathy
Copy link
Contributor

I have raised a PR. Kindly take a look and provide feedback.

martina-if pushed a commit that referenced this issue May 12, 2020
List Supported K8s Versions in `eksctl version`

This change was made to list the EKS Server Supported Versions. Added the functionality for eksctl version command to show the EKS server supported versions in a new line.

Issue #2040
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed kind/feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants