niggl/kubecon25
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(day1): Added operator q&a
All checks were successful
Build latest image / build-container (push) Successful in 50s
Details

Browse Source
This commit is contained in:
Nicolai Ort 2025-04-02 16:00:12 +02:00
parent 4f39c1102c
commit 9ad9af0f9c
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
content/day1/03_operator-mistakes.md
View File

@ -66,4 +66,13 @@ tags:
- But controller runtime abstracts the patch source so you have to compare before and after state yourself - but you should not do that
- What about state sharing across multiple threads?
- Controller runtime handels each reconcile as idempotent, so you can just multithread
- But handling consistency can still be hard
- But handling consistency can still be hard because you have to design all of your operations as idempotent by rebuilding the state each time
- What are your thoughts on controllers that do stuff in the real world (especially b/c it takes longer and there are no natie observers)
- Do something like the krt project by keeping the state seperatly
- What if someone changes things at the cloud provider
- A question of philosophy -> Usually just treat the operator at the source of throuth
- How do you test your operators?
- Depends on your output (kubernetes objects make stuf simple)
- For cilium: Simple b/c it's just creating kubernetes projects
- With oputside interaction: In-memory state representation or mocking
- For complex controllers split the operator into: Ingestion, data model and transformation