Clarify ECK support scope for ingress controllers

[kunisen]

Background

In an internal ticket (stl-1548) and also an internal slack channel, @jeanfabrice, @pebrc and I discussed about support scope of ingress controllers.
We came up with the plan to clarify this in public doc as below:

Docs need updated

• https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-recipes.html
• https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-traffic-splitting.html
• https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-maps.html
• https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-maps-http-configuration.html#k8s-maps-ingress
• https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-stack-helm-chart.html#k8s-eck-stack-ingress

Text to add

Note: Support Scope for Ingress Controllers

Ingress is a standard Kubernetes concept. While ECK-managed workloads can be publicly exposed via ingresses and we provide example ingress configuration recipes, setting up an Ingress controller requires in-house Kubernetes expertise. If configuring ingress presents challenges, we recommend using a standard Load Balancer (LB) as an alternative solution.

docs-content pages to edit

• http://localhost:3000/deploy-manage/deploy/cloud-on-k8s/recipes
• http://localhost:3000/deploy-manage/deploy/cloud-on-k8s/requests-routing-to-elasticsearch-nodes
• http://localhost:3000/deploy-manage/deploy/cloud-on-k8s/elastic-maps-server
• http://localhost:3000/deploy-manage/deploy/cloud-on-k8s/http-configuration#k8s-maps-ingress
• http://localhost:3000/deploy-manage/deploy/cloud-on-k8s/managing-deployments-using-helm-chart

Sample view

:: Without link

:: With link

Clicking the link example ingress configuration recipes will redirect page to http://localhost:3000/deploy-manage/deploy/cloud-on-k8s/recipes

[eedugon]

@kunisen : instead of adding the title in the note, try a plain admonition, and let me know your thoughts:

I'm also rewording a bit the statement, for your consideration too:

:::{admonition} Support scope for Ingress Controllers
Ingress is a standard Kubernetes concept. While ECK-managed workloads can be publicly exposed using ingress resources, and we provide example configurations, setting up an Ingress controller requires in-house Kubernetes expertise. If ingress configuration is challenging or unsupported in your environment, consider using standard LoadBalancer services as a simpler alternative.
:::

[eedugon]

I've suggested a small change in the text and a plain admonition with the title instead of a note.

[kunisen]

Thanks @eedugon
It looks perfect to use admonition 🤩

[eedugon]

LGTM, thanks a lot!