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

Status Of Project #288

Closed
sstubbs opened this issue Jul 23, 2020 · 6 comments
Closed

Status Of Project #288

sstubbs opened this issue Jul 23, 2020 · 6 comments
Labels
question Direction unclear; possibly a bug, possibly could be improved.

Comments

@sstubbs
Copy link

sstubbs commented Jul 23, 2020

Hi,

I have used this library in the past for testing purposes. I would like to now build an operator that's ready for production but I am wondering how stable this project is and how many more breaking changes there will be until there is a stable release. If not I will have to use one of the go options but I prefer to use rust if possible.

@clux
Copy link
Member

clux commented Jul 23, 2020

There will almost certainly be some more breaking changes. It's hard to estimate. We hope that we're starting to stabilise, but the last release was pretty major. Expecting a certain amount of fallout.

@clux
Copy link
Member

clux commented Jul 23, 2020

That said, changes will be documented in CHANGELOG, and you can pin your versions as appropriate.

@nightkr
Copy link
Member

nightkr commented Jul 23, 2020

The API isn't stable yet (we're not 1.0!), but the basic ideas are mostly in place, especially for the API client (kube, as opposed to kube_runtime).

As @clux mentioned, 0.36.0 was a pretty big and breaking release. That said, I just upgraded an internal project from 0.28.1 to 0.37.0 yesterday in an hour or so. Pretty much all of the changes were either sedable renames (such as APIClient -> Client) or deleting a bunch of code (dropping our custom internal controller runtime in favour of kube_runtime).

@nightkr
Copy link
Member

nightkr commented Jul 23, 2020

That said, it's a good discussion to raise. API breakage is one thing, but #286 shows that it might be worth starting to let releases bake for a bit longer.

@sstubbs
Copy link
Author

sstubbs commented Jul 23, 2020

ok thanks I think I will use this anyway as I'm a big fan of rust and this library and just not upgrade as frequently as I generally do. I don't really require anything too fancy for what I'm doing. Just doing basic mariadb and cyrusimap operators that we use internally. Currently I'm using helm charts that I did. I find a lot of the prebuilt go operators are overkill for my needs.

@clux clux added the question Direction unclear; possibly a bug, possibly could be improved. label Jul 26, 2020
@clux
Copy link
Member

clux commented Jul 26, 2020

Awesome. I'll close this for now. We'll revisit stability guarantees and actually define what this entails once 1.0.0 is right on the horizon.

Edit: #508

@clux clux closed this as completed Jul 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Direction unclear; possibly a bug, possibly could be improved.
Projects
None yet
Development

No branches or pull requests

3 participants