feat: add support for installing apisix ingress composite mode via helm chart

[Padmabishek]

Issue description

request help: I wanted to use apisix-composite architecture for an etcd-less apisix-ingress/gateway. Is it stable yet? When will be helm charts available for composite architecture? Is it safe to use for production? If not , when can we expect this feature to be stabilized. Thanks a lot for your help!

Environment

• your apisix-ingress-controller version: 1.7.0
• your Kubernetes cluster version: v1.24.14

[Vacant2333]

@Revolyssup hello, can u help this

[Padmabishek]

@Revolyssup Any update on this ? Is this feature stabilized on 1.8.0 , I don't see anything regarding the feature in the release notes , please help

[Revolyssup]

@Padmabishek The architecture without etcd is experimental.

[Revolyssup]

@Padmabishek Helm supports deploying it. helm install ingress-apisix apisix/apisix-ingress-controller --create-namespace
-n ingress-apisix
--set config.apisix.serviceNamespace=ingress-apisix
--set config.etcdserver.enabled=false

[Vacant2333]

@Padmabishek looks like this issue was resoulve now? @Revolyssup how do u think, do we need update it to the docs?

[Revolyssup]

@kayx23 Will you take up this issue? Here maybe you can try installing the standalone mode via helm chart and document it in the doc.

[kayx23]

Let me circle back to this some time next week.

[Padmabishek]

Hi @kayx23, Do we have any documentation available now ?

[kayx23]

Hello - not yet, haven't had the bandwidth for this thus far.

[Padmabishek]

I will try installation with below option and update my observations here. helm install ingress-apisix apisix/apisix-ingress-controller --create-namespace -n ingress-apisix --set config.apisix.serviceNamespace=ingress-apisix --set config.etcdserver.enabled=false

[github-actions[bot]]

This issue has been marked as stale due to 90 days of inactivity. It will be closed in 30 days if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the [email protected] list. Thank you for your contributions.

[github-actions[bot]]

This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.

[ceelian]

@Padmabishek did this work as expected? Thx.