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

Centralise state via git #13

Open
byrnedo opened this issue Oct 6, 2024 · 1 comment
Open

Centralise state via git #13

byrnedo opened this issue Oct 6, 2024 · 1 comment

Comments

@byrnedo
Copy link
Collaborator

byrnedo commented Oct 6, 2024

Not 100% sure yet on how much state should be centralised but even having what was applied by the client would help a lot.
As in, when you'd run skate apply, whatever you had in your yaml would be also saved to a git repo. Not necessarily what was scheduled, but more the submitted yaml. That would simplify adding nodes (you could see what needs to be rescheduled easily), it would also enable a gitops setup like dokku: a gitops container could run within the skate cluster, and schedule on to skate itself, since it'd be possible to get the global cluster state there (what nodes we have, whats already running).

@byrnedo
Copy link
Collaborator Author

byrnedo commented Oct 6, 2024

If secrets were also in this git state repo, we could avoid having to have all secrets on all nodes. Instead creating the secret if the node has a workload that needs it. Downside is having secrets in git....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant