feat: Rancher Fleet multi-cluster deployment for EdgeKit#5
Draft
Copilot wants to merge 6 commits into
Draft
Conversation
Open
- Add fleet.yaml for Rancher Fleet multi-cluster GitOps deployment (central clusters get the broker; edge clusters get the agent) - Add helm/edgekit/values-server.yaml for central cluster (server only, NodePort 31883/31901) - Add helm/edgekit/values-client.yaml for edge cluster (client only, external broker URL) - Extend helm/edgekit/values.yaml with server.service.nodePorts - Update server-service.yaml template to emit nodePort fields when service type is NodePort - Add docs/rancher.md: full Rancher / k3s deployment guide - Update README.md and docs/quickstart.md with Rancher section
Copilot
AI
changed the title
[WIP] Integrate Rancher for client and server environments
feat: Rancher Fleet multi-cluster deployment for EdgeKit
May 25, 2026
tomgrv
requested changes
May 26, 2026
tomgrv
left a comment
Contributor
There was a problem hiding this comment.
@copilot Update as per new branch and updated codebase
…r topology - Merge origin/copilot/integrate-edgex-platform (EdgeX Foundry 4.0 integration) - Resolve conflicts in fleet.yaml, values-server.yaml, values-client.yaml: use valuesFiles references and LoadBalancer service type from base branch - Fix cross-cluster broker URL placeholder (was in-cluster DNS, now CENTRAL_LB_IP_OR_HOSTNAME) in values-client.yaml and values-thin-client.yaml - Add NodePort alternative comment to values-server.yaml for bare-metal k3s - Update docs/rancher.md: three cluster roles (central/edge/edge-thin), LoadBalancer as primary with NodePort fallback, thin-client section - Update README.md Rancher section: add edge-thin cluster type, fix commands - Update docs/quickstart.md: reference three cluster roles
Author
Updated in commit |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
EdgeKit needs to run across two cluster tiers in a SUSE Rancher environment: the MQTT broker on a central k3s cluster and edge agents on individual k3s edge nodes (e.g. ARK-1222 on SL Micro 6.2).
Rancher Fleet GitOps
fleet.yamlat repo root — Fleet deploys broker vs. agent based on cluster labels:edgekit/role=central→ server only, NodePort exposededgekit/role=edge→ client only, pointed at central node IPSplit Helm values
values-server.yaml— central cluster: server enabled, client disabled,NodePortservice on 31883 (MQTT) / 31901 (WS)values-client.yaml— edge cluster: server disabled, client enabled with external broker URL placeholderHelm chart changes
values.yaml— addsserver.service.nodePorts.{mqtt,ws}(empty by default, auto-allocated when blank)server-service.yaml— conditionally emitsnodePort:fields only whentype: NodePortand a port value is set; ClusterIP rendering is unchangedDocs
docs/rancher.md— full deployment guide: Fleet GitOps setup, manual install, LoadBalancer alternative, firewall requirementsREADME.mdanddocs/quickstart.mdupdated with Rancher sections