-
Notifications
You must be signed in to change notification settings - Fork 1.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
feat(nodegroup): new integration: spot ocean #6694
Comments
Along with the above proposal, I want to add some context and stress the demand we are seeing on this side. Demand for an upstream integration has been increasing as users continue to utilize this tool and expect official, maintained and updated resources. I get this request from a variety of our users on a weekly basis and it's only growing. In terms of support and maintenance: Spot by Netapp pledges to fully maintain this integration.
|
I would just like to echo that this feature being added would be helpful. I have several ocean clusters and would like to be able to use eksctl to manage them a bit tighter than having to bounce around between CLI management tools. |
At Ticketmaster we leverage Spot by NetApp via the current forked EKSCTL to manage our EKS clusters, and have been doing so for years. Over the last year I've seen management of the fork improve (more quickly and regularly rebase upstream changes to the fork as well as adding Spot API support for new Spot/NetApp features) and we would very much appreciate the ability to upstream this capability. I have to acknowledge the previous attempt at #2364 and my hope is this is presented in a more suitable manner and possibly work together to progress this. |
This would be an absolute game changing for our usage of eksctl |
Would greatly appreciate this work being upstreamed, as Kubernetes continues to rapidly develop, having tighter integration of the full EKSCTL with Spot by NetApp helps us to avoid version issues, ans maintain our fleet of EKS clusters in multiple regions. |
I'd definitely like to see this upstreamed. I believe it would help reduce ecosystem fragmentation and provide a better experience for eksctl users. |
Would be great to have upstream support and streamline usage of eksctl |
I would definitely love to see this integration for all the reasons mentioned above. |
We love managing kubernetes via cli and eksctl is too handy to create a cluster/node group. A direct integration to create an Ocean cluster/node group using eksctl would give us an effortless way to create and maintain unmanaged Kubernetes clusters through Ocean and save a lot of time. Really looking forward to see it getting upstreamed. |
This would be a very welcome addition to our use case. |
This integration would be a huge benefit for our usage of eksctl! |
I'd find this feature very useful especially since I'm already familiar with eksctl. Please add! |
I see a ton of value for our joint customers getting this upstreamed. Prioritize this :) |
Eksctl is a super useful tool, and this integration would be hugely beneficial for simplifying management of Ocean nodegroups as well. Please add! |
Would love to see this integration working. One of the best ways to manage EKS clusters is by using CLI tools like eksctl, and having a daily usage tool working together with Spot by NetApp products will save a ton of DYI work for DevOps Engineers / SREs, etc. Can't agree more with the other users who commented on this thread. |
Would love to see this upstreamed! |
Hello everyone, we are working with eksctl to provision the Kubernetes cluster, and today have two possibilities, create a Cluster with Spotinst integration and without Spotinst integration. We have seen a bad experience working with two different implementations that are the same thing. It makes sense that Waveworks adds that possibility to the same project, considering that big companies already work with this implementation. |
Eksctl is a great tool for managing eks clusters, at Ticketmaster we run eks + spot.io, and we manage the clusters using the forked version of eksctl with the spot.io integration, over the years the quality of the integration has improved and support from spot.io on keeping the fork up to date has been great. We would love to see the support for spot.io in Eksctl upstreamed. |
Dupe of #2364 @mikestef9 There's a lot of interest from the community for this feature, can we reconsider the decision? |
I am wondering whats next to get this feature request reconsidered. I know that two years ago it was decided not to integrate, but as the traffic above shows there is a lot of desire to have this feature bolted in upstream |
The stance has not changed since the original comment. However, since that comment, we have launched native EKS add-ons marketplace integration https://aws.amazon.com/blogs/aws/new-aws-marketplace-for-containers-now-supports-direct-deployment-to-amazon-eks-clusters/ Adding the Ocean controller to EKS add-ons Marketplace integration is best path forward here. |
@mikestef9 AWS MP for containers only solves for Ocean helm charts but offers "no" solution for managing Ocean via standard Infrastructure as Code primitives aka eksctl. Is there an alternate ability in the AWS MP to solve for eksctl? |
Spot Ocean is a commercial product and not open source, right? Best to integrate with marketplace. |
Why do you want this feature?
Similarly to the existing integration with kops instance groups, we'd like to integrate Ocean by Spot with eksctl.
What feature/behavior/change do you want?
Seamlessly integration of Ocean with unmanaged nodegroups, as part of a demand of AWS customers.
Pull request
#6731
Please check out our proposal documentation.
The text was updated successfully, but these errors were encountered: