forked from Fediversity/meta
66 lines
1.4 KiB
Markdown
66 lines
1.4 KiB
Markdown
Attendence:
|
||
|
||
- Koen
|
||
|
||
- Ronny
|
||
|
||
- Kevin
|
||
|
||
- Bogdan
|
||
|
||
- Robert
|
||
|
||
- Jime
|
||
- Laurens
|
||
|
||
- Nix operation 4:
|
||
|
||
the plan is to have a mirror on forgejo
|
||
|
||
[https://github.com/nixops4/nixops4](https://github.com/nixops4/nixops4)
|
||
|
||
- July 9 Kickoff
|
||
|
||
Amsterdam, start at Science park, have dinner in the evening.
|
||
|
||
- Technical architecture document
|
||
|
||
Option to use Kubernetes
|
||
|
||
Con:
|
||
|
||
a. We want create some resistance of being able to run it in a 'non sovereign way'.
|
||
|
||
b. We don't need a packaging mechanism other than Nix.
|
||
|
||
c. If you put Kubernetes in between 'you have to learn' Kubernetes as a 'being fluent' in the entire solution
|
||
|
||
d. reproducable? declarative?
|
||
|
||
e. no native IPv6
|
||
|
||
Pro:
|
||
|
||
a. small to large systems
|
||
|
||
b. run more services in case of (scheduling part of Kubernetes)
|
||
|
||
c. makes it easy to run on hyperscalers
|
||
|
||
d. makes it easy to move away from the hyperscalers
|
||
|
||
Scheduling mechanism: nomad
|
||
|
||
- does not do more than needed; no containers but raw Nix
|
||
|
||
- no truly OSS fork (yet?)
|
||
|
||
|
||
|
||
Note: [https://nluug.nl/evenementen/nluug/voorjaarsconferentie-2024/talks/alain-van-hoof-kubernetes-from-scratch-the-hard-way/](https://nluug.nl/evenementen/nluug/voorjaarsconferentie-2024/talks/alain-van-hoof-kubernetes-from-scratch-the-hard-way/)
|
||
|
||
|
||
|
||
Fediversity Tech Workshop 16:30h to 17:30h CEST 2 june 2024
|
||
|
||
NixOS NixOPS and Kubernetes? |