-
Notifications
You must be signed in to change notification settings - Fork 234
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
Support managing snapshot policies #806
Comments
[Triage] |
Exactly. We can introduce a new CRD for that and add a reconciler to the operator to handle it. |
Wouldn't creating a ISMPolcy with a snapshot: https://opensearch.org/docs/latest/im-plugin/ism/policies/#snapshot archieve the same? |
Hmm. What opensearch needs is a way to document the api in a systemic way using openAPI/swagger style. That would simplify the usage of the opensearch api a lot for future operator developement. (That is atleast the path elastic took) opensearch needs an api like this: https://www.elastic.co/docs/api/doc/kibana/v8 This would also make sure that the api- documentation is automatically generated and also up-to-date. I can't believe we don't have something like this yet.. |
Discussed in #796
The operator already supports managing snapshot repositories. A step further would be to add a custom resource and reconciler logic (similar to ISMPolicies) to also manage snapshot policies via the operator.
The text was updated successfully, but these errors were encountered: