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

Handle user workloads/charts #323

Closed
e-minguez opened this issue Mar 15, 2024 · 0 comments · Fixed by #477
Closed

Handle user workloads/charts #323

e-minguez opened this issue Mar 15, 2024 · 0 comments · Fixed by #477
Labels
enhancement New feature or request triaged The team has reviewed the issue
Milestone

Comments

@e-minguez
Copy link
Contributor

e-minguez commented Mar 15, 2024

Currently EIB deploys Edge components and user workloads using the same approach, creating addon files for RKE2 on the /var/lib/rancher/rke2/server/manifests/.
This means that the files are the source of truth, not the k8s object itself and in the event of a modification is required (either a upgrade or a parameter tweak), the change needs to be done on the files themselves... and in HA scenarios, keep them synced (EIB currently creates the manifest files on the initializer node only).

For Edge workloads we will manage this by the upgrade mechanism somehow but for user workloads they need to be aware of this or maybe we can just deploy the thing and then use the .skip mechanism to let the users treat them as k8s objects.

@jdob jdob added enhancement New feature or request triaged The team has reviewed the issue labels Mar 15, 2024
@jdob jdob added this to the v1.1 milestone May 13, 2024
@atanasdinov atanasdinov linked a pull request Jun 27, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triaged The team has reviewed the issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants