Describe an architecture for a management framework using standard Open Source components #2
Labels
No labels
OpenGitOps
bootc
bug
documentation
duplicate
enhancement
epic
good first issue
help wanted
invalid
question
story
user-story
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
OS2/os2base#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Architectural proposal is available in the README.md
The design can choose a pull oriented obeservability design (e.g. with promtrial and Loki/Grafana) or a push based (e.g. with a MQTT brooker queue that pushes "events" directly to Grafana via a MQTT plugin)
To broaden the use cases for config and IaC management, research a set of alternative orchestrators.
A more complete upstream possibility adding the benefit of using gitops principles for device managment would be possible with a solution like 🛳️ FleetDM - this needs to be researched and discussed.
3 minute demo video: https://www.youtube.com/watch?v=q1Tm3IBcx24
Read more: https://fleetdm.com/docs/get-started/why-fleet
After some time discussing several potential directions, the focus for the PoC is moving towards the Cloud Native bootC standard and immutable distros and resilliency via GitOps patterns and methods.
Closing this issue as solved. Tasks for the PoC will be created in issues tagged bootc and OpenGitOps.