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

feat: poc to manage configs with k8s CRDs #223

Closed
6 tasks
hcavarsan opened this issue May 18, 2024 · 2 comments
Closed
6 tasks

feat: poc to manage configs with k8s CRDs #223

hcavarsan opened this issue May 18, 2024 · 2 comments
Labels
wontfix This will not be worked on

Comments

@hcavarsan
Copy link
Owner

just a poc to validate export/import and sync configs with k8s crds. imho, this will mainly help homelabs if i can bootstrap a new cluster with all my configs and sync them.

steps:

  • the crds with config schema/struct
  • deploy the crds
  • create backend functions to read/store configs, just need to read the kubeconfig and context; the functions need to deserialize and convert into a config struct to import in sqlite
  • create backend functions to validate if the cluster has the crds installed
  • create frontend logic to pull these configs, read the inputs (kubeconfig, context), validate if crds are installed in the context, and call the function to delete all configs and then call the function to import configs from crds
  • create frontend logic to push these configs, need to validate inputs and call the function to validate if crds are installed and if not, then open a dialog to install them. After this, call the function to apply configs in the clusterI
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the wontfix This will not be worked on label Jul 17, 2024
Copy link

This issue has been automatically closed due to inactivity. Please re-open if this still requires investigation.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant