[AMORO-1335]Amoro AMS Support On K8S

[czy006]

Why are the changes needed?

AMS Run On K8S

Close #1335.

Brief change log

• add helm chart for amoro
• ams running on k8s

How was this patch tested?

• ams log4j2 and config.xml can be rewrite
• ams server and web ui on k8s open normal
• Run test locally on k8s before making a pull request

Documentation

• Does this pull request introduce a new feature? (yes)
• If yes, how is the feature documented? (docs)

[majin1102]

Thank you for your contribution. Your PR is very valuable to Amoro community.

Review request @baiyangtx bai @HuangFru

[Kyofin]

Good feature !

[baiyangtx]

Thanks for your contribution, Your PR is very valuable to me. I will try this as soon as possible.

[baiyangtx]

I tested it on Minikube. It's easy to install the AMS service using Helm. However, I don't think we should currently support multi-replica deployment for the following reasons:

1. Amoro is not a stateless service and caches a lot of state in memory. The current HA design is an active/standby architecture, and when the standby node becomes the master, the memory state needs to be reinitialized.

2. In the current design, the standby node has no accessible ports for Thrift or REST, so the pod liveness probe will have problems.

I suggest that we only support single-replica deployment in the first Helm version and support multi-replica deployment after resolving the pod liveness probe problems.

[baiyangtx]

LGTM, Thanks a lot for your contribution!

[HuangFru]

I've tried this in Rancher Desktop with K8s on my local machine, works fine.
LGTM. Thanks for your contribution!