-
Notifications
You must be signed in to change notification settings - Fork 8
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
Curlable Kubernaut API #46
Comments
There is one? How do you think the CLI works? |
Delete
List
Get
Create
|
The only reason the API isn't a first class citizen is because everyone wanted a CLI as the UX originally and handling tokens is messy. |
Sorry for not being clearer, I'm not actually asking for documentation for the existing REST API. I was aware of that and for my purposes the existing kubernaut client is good enough documentation for how that works. If you look at the description of the API I posted, it's different from the existing REST API in two ways:
|
While not "pretty" this is a simple work around for (1) Regarding <2>... customizable expirations is on the backlog to implemented. I have a hard time seeing how renew would work with GCE preemptible VM's on the backend though since they are automatically reaped after 24 hours without exception. |
That workaround isn't a super great option for me. Keep in mind I'm trying to write build files that work anywhere, and if I could count on a sane/working python environment everywhere, then I could just use the kubernaut cli. To be clear I don't really care about "pretty", all I care about is how much work I need to do to leverage kubernaut for my use cases, and how brittle that work is in different environments. It really could be way easier and more portable if the server API were tweaked a little.
It would just have a 24hr limit? I mean no claim is guaranteed to last anyways, right? |
Kubernaut curl API:
Rationale:
After having integrated kubernaut into a bunch of dev loops, I think
the above curl-based API would probably be simpler/easier to work
with and would avoid a bunch of the work associated with having a
fat client.
FWIW, the list part isn't actually directly needed by the
integrations, but it is useful for debugging/correcting resource
leaks.
The text was updated successfully, but these errors were encountered: