Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Connection Hub Components Configurable #54

Open
tunahanertekin opened this issue Feb 7, 2023 · 0 comments
Open

Make Connection Hub Components Configurable #54

tunahanertekin opened this issue Feb 7, 2023 · 0 comments
Labels
cloud-instance Cloud instance represents any Kubernetes cluster in edge or central cloud. physical-instance Physical instance represents Kubernetes (k3s) clusters running on a robot. tech-story

Comments

@tunahanertekin
Copy link
Member

The Technical Story

Two components are deployed with connection hub using Helm:

  • Kubernetes Federation
  • Submariner

These components can be configured using Helm values manually. Connection hub CRD should be exporting necessary values to extend component configuration.

Parent Story

  • robolaunch/robolaunch#40
  • robolaunch/robolaunch#58
  • robolaunch/robolaunch#59
@tunahanertekin tunahanertekin added physical-instance Physical instance represents Kubernetes (k3s) clusters running on a robot. cloud-instance Cloud instance represents any Kubernetes cluster in edge or central cloud. tech-story labels Feb 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cloud-instance Cloud instance represents any Kubernetes cluster in edge or central cloud. physical-instance Physical instance represents Kubernetes (k3s) clusters running on a robot. tech-story
Projects
None yet
Development

No branches or pull requests

1 participant