Closed Arau closed 5 years ago
I think rather than 'Deprecated', there is room to have something like 'Custom Installations' - and link to the github deployment repo for examples. Perhaps we could cite why it might be appropriate to do a custom installation - for those wanting to avoid operators or requiring special circumstances.
On a general note, I think there is room for more operator specific content on the docs site - ideally I'd like to have the available options on a page in the reference section at least. I'm hoping we can get to a point where the docs are relatively self contained.
In case we find people who dislike Helm, is there a non-Helm way of getting the Operator installed from basic manifests?
We are adding a non helm installation of the operator, but only when we finish all the P0, P1 docs. It is in the roadmap of this doc but I don't know yet if I will be able to fit it into this PR yet.
I like the idea of custom installations, so I'll prepare the PR accordingly.
I was planning to add the reference doc for the operator. But once again, with less priority than other PRs.
My language edits are now in the branch. See here for all changes. @Arau @actionbuddha
My language edits are now in the branch. See here for all changes. @Arau @actionbuddha
Thank you!!!
Made some minor changes to phrasing.
I have applied the changes about what goes where. Please revisit to see if that makes sense now.
Thank you
This PR is not for merge yet but to have your opinion about the content.
I moved the previous installation to a deprecated section. The operator installation is in the place of honour.
Do you think we should remove the whole deprecated section?