After some review, I agree as well. Vladimir's push to simplify the OSH charts and get rid of stuff that isn't needed or doesn't make sense is a good one. Let's give Calico the boot. Steve Taylor On 2/5/2024 5:05:08 PM, Karl Kloppenborg <kkloppenborg@resetdata.com.au> wrote: Hi Vladimir, I agree with this, plus most people utilising OpenstackHelm in production are rolling their own CNI configurations prior to deploying OSH. Lets remove it. Thanks, Karl Kloppenborg. From: Vladimir Kozhukalov <kozhukalov@gmail.com> Date: Tuesday, 6 February 2024 at 10:20 am To: openstack-discuss@lists.openstack.org <openstack-discuss@lists.openstack.org> Subject: [openstack-helm] Remove Calico chart Hi everyone, I would like to suggest removing the calico chart from the openstack-helm-infra repository which does not seem worth it to support any more. Tigera provides great tools for managing Calico deployments (helm chart, operator and even plain kubectl manifest). Also there are plenty of other networking solutions on the market and it looks like users can choose on their own the CNI implementation. There have not been many contributions to this chart for quite some time and we don't use this chart in any test jobs. In the deploy-env role we use the upstream Calico manifest [1]. Having said that, I think that we can remove it immediately even without any depreciation period. Opinions are welcome. [1] https://opendev.org/openstack/openstack-helm-infra/src/branch/master/roles/d... [https://opendev.org/openstack/openstack-helm-infra/src/branch/master/roles/d...] -- Best regards, Kozhukalov Vladimir