Documentation update on installation process

[iivanov5]

Hi,

As I was trying to install NGINX Gateway Fabric via Helm, I was left with the false sense that the Helm Chart is going to install the Gateway API CRDs as well, and there is no note and the section about manifests is misleading.

I think it will be a good idea to put a note in the helm section that you need to install the Gateway API CRDs beforehand. I also think that even better idea will be for the Helm Chart to install them if they are missing from the cluster.

Thanks in advance.

[sjberman]

Hi @iivanov5, our installation docs and helm chart README both describe this necessary step. Is there something unclear with these that we can improve on?

[iivanov5]

Hi @sjberman, I was in a hurry and skipped directly to the helm installation as the option I wanted, which is my fault, and missed the first part as I believed it was just another option for installation of the NGF.

Still it would be nice to have an option in the Helm Chart to install Gateway API CRDs if needed. Maybe provide a value like 'install.gatewayapi: true' or something.

[mkingst]

Hi @iivanov5 . We discussed this in the past, particularly regarding including the Gateway API CRDs as part of the installation in Helm. The reason we kept them separate was due to compatibility and maintenance concerns. The APIs can be updated frequently with each release, and it’s important for users to ensure they are using the correct version supported by the NGINX Gateway Fabric. We’ve taken note of this though, and we can explore the possibility of offering an option for this in the future. Thank you for sharing your thoughts!

[iivanov5]

Hi,

Thank you for the feedback.