-
Notifications
You must be signed in to change notification settings - Fork 5
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
[Feature]: public access for CRD struct #32
Comments
Should xline-operator be used as a binary, so there is no need to provide a public CRD definition as a library? |
Absolutely, xline-operator run as a binary, At the same time, the CRD definition should also be provided as a libiary so that others can use it. Let user can apply CR with rust code and not kubectl for integration into their platform. |
That makes sense, I suggest move these CRDs into a separated crate. |
@iGxnon ,How about |
|
I'll handle this in #37 |
This is not need any more due to the xline-operator is rewriting with golang. closing... |
Description about the feature
Wee need to allow users to operate crd resources outside xline-operator (for example, create xline cluster), which means that the struct corresponding to operator crd should be publicly accessible, currently within the crate scope.
xline-operator/operator-k8s/src/crd/v1alpha1/cluster.rs
Lines 31 to 33 in 1a15e69
This is a good first issue for me, i want to work for it and assign me please,Thanks. Remind me if i missed something.
Code of Conduct
The text was updated successfully, but these errors were encountered: