eksctl
eksctl copied to clipboard
eksctl-io
Import eksctl as a library to integrate other utils
Why do you want this feature? I am using eksctl to build an eks provision tool in kubeflow community. In my previous version, we use eksctl as a cli in shell scripts to create eks cluster. Now, community is moving to golang ctl and we need to migrate existing functionalities implemented by shell to golang.
I don't know if eksctl can be used for this purpose. I notice no one package import eksctl yet. https://www.grank.io/pkg/github.com/weaveworks/eksctl.html
What feature/behavior/change do you want? Need eksctl SDK to create/delete cluster. All CLI features should be supported in SDK.
This would be good to have, and we could use it for testing purposes also.
Is there any opportunity to contribute to this effort? We'd love to use this for creating tooling for internal cluster setup that requires more than what's within the scope of eksctl (ie VPC peering), not just because Go is the community standard.
is there any plan to work on this topic or anyone actively working on it?
Remaining:
- [x] Incorrect use of
k8s.io/kubernetes(k8s/k8s PR) (see previous attempt to fix)- [x] Merged! :partying_face:
- [x] k8s
1.21released
- [x] bump k8s in
eksctlto1.21 - [ ] Explicitly stabilize some package interfaces (or none for now)
I would pick eksctl any time of the day if we have a sdk so that we can get ride of the scripts needed to integrate with the eksctl.
related to: https://github.com/weaveworks/eksctl/issues/3839
@errordeveloper can you please help us here, this looks like a must have now.
@errordeveloper can you please help us here, this looks like a must have now.
@rverma-nsl which eksctl operations are you trying to invoke and from what language?
almost all of them, top ones are create cluster, add nodegroup, add irsa roles, patch cluster upgrades and addons.
Why not just call these and abstract the binary calling operations behind an interface for example? How would you benefit from calling these things from code vs calling out to the binary? Once abstracted you can incorporate the calling into unit tests as well if testability is a concern.
I guess its basically same stuff as kubectl vs client-go. I am also using the same since storing eksctl config in a cm. It can work but won't be super pleasant with all the yaml marshalling :)
You could try and re-create what we do :) Nothing is behind an internal thing, so technically, you could import it. :)
I'm looking to do this for python, would it be possible to import the go libraries or is there another way to do such an import? For example a C package I can import into Python
