request help: Need help on installing Apisix 3.6.0 in kubernetes through yaml files.

[nphariharan]

Issue description

The below link explains the steps for installing Apisix i.e. - 2.15.0 in kubernetes through yaml files. https://apisix.apache.org/docs/ingress-controller/tutorials/the-hard-way/

I want to install Apisix 3.6.0 in AWS EKS Cluster(Version - 1.28) in standalone mode i.e. without etcd server through yaml files.

Please provide me the complete steps with yaml files.

Environment APISIX version (run apisix version): 3.6.0 AWS EKS Cluster version - 1.28 APISIX Dashboard version, if relevant: NA Plugin runner version, for issues related to plugin runners: NA LuaRocks version, for installation issues (run luarocks --version): NA I could not get detailed example for installing the same. Please provide any useful link for the same.

Environment

• your apisix-ingress-controller version (output of apisix-ingress-controller version --long):
• your Kubernetes cluster version (output of kubectl version):
• if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):

[Vacant2333]

pls check these: https://apisix.apache.org/docs/apisix/2.15/stand-alone/ https://apisix.apache.org/blog/2023/02/09/secure-apisix-admin/#standalone-mode

[nphariharan]

The above link describes installation of apisix outside kubernetes. But I want to install Apisix in kubernetes. Do you have any guide for the same? At least give me the complete Apisix-config map and Apisix deployment yaml file.

[zll600]

@nphariharan Can you check this doc to change config.yaml for apisix: https://apisix.apache.org/docs/apisix/deployment-modes/#standalone

the key part should be add following part to config.yaml

  role: data_plane
  role_data_plane:
    config_provider: yaml
#END

[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.