Chris79OG opened a new pull request, #10932:
URL: https://github.com/apache/seatunnel/pull/10932
### Purpose of this pull request
Closes #10927.
Adds a focused managed Kubernetes notes section to the Kubernetes quickstart
and Helm guide. The new docs cover the platform-specific checks users usually
need before adapting the existing Minikube examples to EKS, GKE, AKS, ACK, TKE,
CCE, VKE, or OpenShift.
### Does this PR introduce _any_ user-facing change?
Yes. Users deploying SeaTunnel on managed Kubernetes services now get
explicit guidance for image registries, namespace/RBAC setup, ConfigMaps and
Secrets, connector packaging, checkpoint/state storage, networking exposure,
scheduling, and observability.
### How was this patch tested?
Documentation-only change.
Verified locally with:
```bash
git diff --check
```
### Check list
* [x] If any new Jar binary package adding in your PR, please add License
Notice according
[New License
Guide](https://github.com/apache/seatunnel/blob/dev/docs/en/developer/new-license.md)
* [x] If necessary, please update the documentation to describe the new
feature. https://github.com/apache/seatunnel/tree/dev/docs
* [x] If necessary, please update `incompatible-changes.md` to describe the
incompatibility caused by this PR.
* [x] If you are contributing the connector code, please check that the
following files are updated:
1. Update
[plugin-mapping.properties](https://github.com/apache/seatunnel/blob/dev/plugin-mapping.properties)
and add new connector information in it
2. Update the pom file of
[seatunnel-dist](https://github.com/apache/seatunnel/blob/dev/seatunnel-dist/pom.xml)
3. Add ci label in
[label-scope-conf](https://github.com/apache/seatunnel/blob/dev/.github/workflows/labeler/label-scope-conf.yml)
4. Add e2e testcase in
[seatunnel-e2e](https://github.com/apache/seatunnel/tree/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/)
5. Update connector
[plugin_config](https://github.com/apache/seatunnel/blob/dev/config/plugin_config)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
