* [maven-release-plugin] prepare release v8.8.0

* [maven-release-plugin] prepare for next development iteration

* Create changes-8.8.0.md

* Reset changelog for 8.9.0

* [maven-release-plugin] prepare release v8.7.0

* [maven-release-plugin] prepare for next development iteration

Groovy naturally supports many dynamic features that we don't benefit for now but cost performance loss, in this patch we compile our Groovy-based DSL scripts statically to optimize performance.

* Introduce trivy to scan images
Signed-off-by: NGao Hongtao <hanahmily@gmail.com>

* Fix CVE
Signed-off-by: NGao Hongtao <hanahmily@gmail.com>

* Update licenses
Signed-off-by: NGao Hongtao <hanahmily@gmail.com>

* Remove log4j 1.x
Signed-off-by: NGao Hongtao <hanahmily@gmail.com>

* Update CHANGES.md
Signed-off-by: NGao Hongtao <hanahmily@gmail.com>

* Update LICENSE refer to webapp
Signed-off-by: NGao Hongtao <hanahmily@gmail.com>
Co-authored-by: 吴晟 Wu Sheng <wu.sheng@foxmail.com>

Add some defensive codes for NPE and bump up Kubernetes client version to expose exception stack trace (#6327)

* [maven-release-plugin] prepare release v8.4.0

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.3.0

* [maven-release-plugin] prepare for next development iteration

The current implementation of envoy ALS K8S analysis is based on the hierarchy, pod -> StatefulSet -> deployment, StatefulSet, or others. It's freaky and different from the Istio Kubernetes registry.

The new path is pod -> endpoint -> service, and we should leverage Informer API instead of raw Kubernetes API.

* [maven-release-plugin] prepare release v8.2.0

* [maven-release-plugin] prepare for next development iteration

* Upgrade dependencies and make the JDK11 compiling passed.

* Update license and fix license check file.

* Add CI for JDK11 compiling.

* Update doc.

* [maven-release-plugin] prepare release v8.1.0

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.0.0

* [maven-release-plugin] prepare for next development iteration

* Remove all shardingsphere cases.

* Add annotation(AlarmCore.start)

* Upgrade nacos version to 1.2.0

* Revert "Upgrade nacos version to 1.2.0"

This reverts commit 4d7b06f6d20ee09ad377ad6ef736aeab429314e0.

* Update nacos version to 1.2.0(Solve the security problem of the old version of fastsjon)

* Recovery annotation

* Recovery annotation

* Update nacos version to 1.2.0

* Update tls_key_generate.sh path

Update tls_key_generate.sh path

* Add annotation(AlarmCore.start)

* Revert "Upgrade nacos version to 1.2.0"

This reverts commit 4d7b06f6d20ee09ad377ad6ef736aeab429314e0.

* Update nacos version to 1.2.0(Solve the security problem of the old version of fastsjon)

* Recovery annotation

* Recovery annotation

* Update tls_key_generate.sh path

* Execution Authority

* Remove nacos

* remove nacos code

* remove nacos

remove nacos

* remove nacos

remove nacos

* remove nacos

* remove nacos
Co-authored-by: Nsongzhendong <289505773@qq.com>
Co-authored-by: Nsongzhendong <songzhendong@xiaomi.com>
Co-authored-by: 吴晟 Wu Sheng <wu.sheng@foxmail.com>

[CVE] Update Nacos 1.0.0 to Nacos 1.2.0(Solve the security problem of the old version of fastjson) (#4753)

* Update nacos version to 1.2.0(Solve the security problem of the old version of fastsjon)
Co-authored-by: Nsongzhendong <289505773@qq.com>
Co-authored-by: Nsongzhendong <songzhendong@xiaomi.com>