Is the ingress-gateway ns really necessary?

[kevprice83]

It seems the ingress-gateway ns created in this part of the guide is not used anywhere.

It states that it would be for the DNS configuration but that is done as part of this guide, it seems like it's possibly redundant and was just referring to a generic namespace where the gateway was intended to be deployed.

I think we can remove it right?

[david-martin]

TLDR:

• closing this issue as the original problem has been addressed and will be included in the next version of kuadrant docs >1.0 (it's already there on the dev version)
• There are some process things to work out around linking and 404s. To be bottomed out in When a link does not reference a version, it produces a 404. #170 (comment)

A few things on this issue.

The docs for the linked version, 0.8.0, have been removed from the docs site, so the 2 links in the issue description give a 404.
I'd like to say that's less likely to happen since the 1.0 release, but I also like to have something more concrete on that. I plan on continuing that thread in #170 (comment)

A later version of those docs is available for 0.11.0 and 1.0.x (for the first one) at this time:

• 0.11.0
  • https://docs.kuadrant.io/0.11.0/kuadrant-operator/doc/install/install-openshift/#aws-route-53-credentials-for-dns
  • https://docs.kuadrant.io/0.11.0/kuadrant-operator/doc/user-guides/secure-protect-connect-single-multi-cluster/#create-the-managedzone-resource
• 1.0.x
  • https://docs.kuadrant.io/1.0.x/kuadrant-operator/doc/install/install-openshift/#aws-route-53-credentials-for-dns
  • (404) https://docs.kuadrant.io/1.0.x/kuadrant-operator/doc/user-guides/secure-protect-connect-single-multi-cluster/#create-the-managedzone-resource

In 1.0.x, the 2nd guide has split into 2 guides, for kubernetes and openshift:

• https://docs.kuadrant.io/1.0.x/kuadrant-operator/doc/user-guides/full-walkthrough/secure-protect-connect-k8s/
• https://docs.kuadrant.io/1.0.x/kuadrant-operator/doc/user-guides/full-walkthrough/secure-protect-connect-openshift/

However, on main/dev (what will be the version after 1.0),
things have changed again.
There are new Install with Helm and Install with OLM guides,
and the follow on "Secure, protect, connect" doc has been merged into 1 version that can be followed for both kubernetes and openshift.

In the latest version of these install guides, the user is no longer instructed to create the ingress-gateway namespace, so I'm going to close this issue.