Ok, nice. Thanks for the feedback. Here are two PRs to cleanup the chart and scripts [1], [2]. [1] https://review.opendev.org/c/openstack/openstack-helm-infra/+/916555 [2] https://review.opendev.org/c/openstack/openstack-helm/+/916155 On Fri, Apr 19, 2024 at 8:30 AM Stephen Taylor <steveftaylor@gmail.com> wrote:

Same here. I don't see any reason to continue to support our own ingress chart.

Steve

On 4/18/2024 8:46:35 PM, Karl Kloppenborg <kkloppenborg@resetdata.com.au> wrote:

Hi Vladimir,

I agree with this. Let’s get it done.

--Karl.

*From: *Vladimir Kozhukalov <kozhukalov@gmail.com> *Date: *Thursday, 18 April 2024 at 1:02 pm *To: *openstack-discuss@lists.openstack.org < openstack-discuss@lists.openstack.org> *Subject: *[openstack-helm] Cleanup OSH ingress chart

Hi dear colleagues,

Some time ago we switched all our test deployment jobs to using the upstream Ingress-nginx chart. So it looks like we can recommend using one of the third party ingress controller charts to all our users. The deployment requirements for third party ingress controllers like ingress class name and ingress pod labels are described in the documentation [1] and this script [2] can be used as an example.

I suggest removing the OSH ingress chart to reduce the code base that we need to support.

Opinions are very welcome.

[1] https://docs.openstack.org/openstack-helm/latest/install/deploy_ingress_cont...

[2] https://opendev.org/openstack/openstack-helm/src/branch/master/tools/deploym...

--

Best regards, Kozhukalov Vladimir

-- Best regards, Kozhukalov Vladimir