-
Notifications
You must be signed in to change notification settings - Fork 15
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
Prerequisites for installation on OpenShift lacking details #133
Comments
there is some content documented here that could help with the prerequisites |
@kevprice83 This is great feedback, thanks. Yes, I think we might need to add links to cloud DNS provider docs. Note that the requirement to create a |
@jayachristina yup the document I linked essentially describes in detail those steps. However, I would not expect those to be in the official guide but maybe some links and any appropriate context/guidance to accompany that which is probably what @smccarthy-ie is suggesting as well. @smccarthy-ie I'm about to try installing latest so will come back to this issue in case something significant changes regarding my original proposal in this issue. |
Unfortunately the original link gives a 404 https://docs.kuadrant.io/0.8.0/kuadrant-operator/doc/install/install-openshift/ It looks like the wording in the prerequisites has changed to "AWS/Azure or GCP with DNS capabilities" Note that the document has been rewritten on 'main' to be less openshift specific (how to install with OLM), |
The installation guide mentions the following in the prerequisites:
There is in fact a lot of work to be done to satisfy this requirement that I think could be facilitated by some additional details on why Kuadrant needs this, what is the purpose of the various records and the roles & responsibilities of the components within Kuadrant regarding this external service and its configuration.
I have documented the steps required to perform a successful integration with Route 53 here. I wouldn't expect such detailed steps to be documented for Kuadrant but maybe we can link to the AWS documentation that I had to follow to be able to do this and explain the relationship between the various configuration and records to be created with the different Kuadrant components responsible for managing this?
As I attempted to do in the guide I wrote I think it's important for the user to understand the roles of the following resources:
ManagedZone
HTTPRoute
DNSPolicy
Because to someone unfamiliar with Kuadrant it is not obvious and knowing this can also help the user self-resolve any issues that occur during the process rather than figuring it out themselves and ultimately opening a ticket before they have even completed the prerequisites successfully.
Let me know what you think and whether any of the guide I have written makes sense in the upstream documentation and I would be happy to submit a PR.
The text was updated successfully, but these errors were encountered: