[Stretch Cluster] Support parsing remote Kubernetes cluster credentials from env #11335
Conversation
…onment variable - Introduced `STRIMZI_REMOTE_KUBE_CONFIG` env var to define remote clusters. - Parsed configuration into a map of cluster ID to `ClusterInfo` (API URL + Secret). - Added validation to handle invalid or malformed input. - Added unit tests to cover valid, empty, missing, and invalid configurations. Signed-off-by: Aswin A <[email protected]>
Addressed review comments Signed-off-by: Aswin A <[email protected]>
Refactored code Signed-off-by: Aswin A <[email protected]>
Addressed review comments Signed-off-by: Aswin A <[email protected]>
aswinayyolath
changed the title
|
This PR introduces support for parsing remote Kubernetes cluster credentials from the The main purpose of this change is to allow the Cluster Operator to discover and connect to multiple remote Kubernetes clusters using their respective API server URLs and Secrets. The credentials are provided in a simple key-value format, and the parsing logic ensures each cluster entry includes both a valid URL and a Secret reference. Example format: cluster-1.url=https://<api-url-1>
cluster-1.secret=<secret-name-1>
cluster-2.url=https://<api-url-2>
cluster-2.secret=<secret-name-2>This enables future functionality such as deploying Kafka pods across multiple clusters, starting with cluster credential awareness. I’d really appreciate your time in reviewing this! Please let me know if there’s anything you’d like me to update or clarify |
aswinayyolath
changed the title
Type of change
Select the type of your PR
Description
Please describe your pull request
Checklist
Please go through this checklist and make sure all applicable tasks have been done