[Feature]: Integration with Kubernetes

[baiyangtx]

Description

K8S is an important computing engine and a crucial orchestration method in cloud-native scenarios. One of Amoro's positioning is to provide an integrated solution for data lake and data warehouse in cloud-native scenarios, so it is necessary to consider the integration with K8S.

The following tasks need to be improved to support integration with K8S:

• Support deploying AMS on Kubernetes.
• Support scaling, resizing, and managing Optimizer on Kubernetes clusters through AMS.
• Supplement "Deploy with Kubernetes" in the deployment section of the documentation.

In addition, there are some details that need to be optimized in the Kubernetes scenario.

Use case/motivation

No response

Describe the solution

No response

Subtasks

• [Feature]: Support Kubernetes deployment for AMS #1335
• [Feature]: Make FlinkOptimizerContainer to support running Optimizer on K8s. #508
• [Improvement]: Documents about intergration with kubernetes #1918
• [Subtask][Imporvement]: Helm script supports FlinkOptimizerContainer #2054
• [Improvement]: Ingress configration for ams when deploying with Helm. #2020

Related issues

• [Improvement]: AMS server-expose-host should be adapted to domain name scenarios. #1922
• [Feature]: AMS Support Database Secert On K8S #1945
• [Improvement]: Support liveness port testing for standby instance #1957
• [Improvement]: Helm Chart Support Overwrite JVM Optional #1962
• [Feature]: Official Amoro Docker Image. #2033
• [Feature]: Implement KubernetesOptimizerContainer to support running Optimizer natively on K8S. #1958
• [Improvement]: Helm adds Kyuubi (as a terminal backend) and PostgreSQL related conf #2306
• [Feature]: Support Flink optmizer run in session cluster #2652

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct