Perry The Cynic
Dabbler
- Joined
- Aug 15, 2023
- Messages
- 34
How should I think about the kubernetes cluster(-of-one) embedded in TrueNAS SCALE? Is it a feature that I can use, or is it an implementation detail I should stay away from? I'm not asking what I can do - I know my way around k8s. I'm asking what is supported.
Concrete questions:
Where is the kubernetes state stored? Is it part of the system configuration, or part of the system pool, or both? If I restore a configuration backup, what will happen to the cluster content? If I upgrade my TrueNAS SCALE system, will that wipe out the cluster and make a new one, or will it upgrade the cluster with my things still inside (and yes, I realize that might break them)? Which of these answers are API (stable)? :)
I'm sorely tempted to run some basic services inside the k8s cluster - Prometheus, Grafana, a bind server, a local package repository; that kind of thing. But will I shoot myself in the foot, stability wise, if I do? And yes, I realize there's a Prometheus "app", but come on... 1.0.47?
Thanks
-- perry
Concrete questions:
Where is the kubernetes state stored? Is it part of the system configuration, or part of the system pool, or both? If I restore a configuration backup, what will happen to the cluster content? If I upgrade my TrueNAS SCALE system, will that wipe out the cluster and make a new one, or will it upgrade the cluster with my things still inside (and yes, I realize that might break them)? Which of these answers are API (stable)? :)
I'm sorely tempted to run some basic services inside the k8s cluster - Prometheus, Grafana, a bind server, a local package repository; that kind of thing. But will I shoot myself in the foot, stability wise, if I do? And yes, I realize there's a Prometheus "app", but come on... 1.0.47?
Thanks
-- perry