Roberto Jung Drebes
@drebes.org
And if “forced” it’s fine to just give wontprovide@email.com
October 6, 2025 at 11:06 AM
And if “forced” it’s fine to just give wontprovide@email.com
git merge -
Just kidding.
Just kidding.
August 12, 2025 at 5:29 PM
git merge -
Just kidding.
Just kidding.
Florianópolis também se aplica na direção “Direita”. 😅
August 8, 2025 at 4:19 AM
Florianópolis também se aplica na direção “Direita”. 😅
Here’s to the crazy ones. 😛
August 7, 2025 at 6:09 PM
Here’s to the crazy ones. 😛
It’s engraved with “Here’s to the crazy ones.”
August 7, 2025 at 6:07 PM
It’s engraved with “Here’s to the crazy ones.”
They should rename it to Sosumi Movies.
August 6, 2025 at 9:27 PM
They should rename it to Sosumi Movies.
Here goes your mercury dose.
June 14, 2025 at 6:14 PM
Here goes your mercury dose.
Also depends if the resource API has CRUD or “apply” semantics. In the case of S3 it’s crud so you have to read, no?
January 16, 2025 at 7:50 AM
Also depends if the resource API has CRUD or “apply” semantics. In the case of S3 it’s crud so you have to read, no?
Depends if it’s a standard controller (which just reconciliates) or an operator (that embeds orchestration logic). It really depends on the domain but generally the more it handles state the more you need tight orchestration and custom logic).
January 16, 2025 at 7:47 AM
Depends if it’s a standard controller (which just reconciliates) or an operator (that embeds orchestration logic). It really depends on the domain but generally the more it handles state the more you need tight orchestration and custom logic).
In a way, we’re back to the old configuration management (ansible versus puppet) arguments. :)
January 16, 2025 at 5:51 AM
In a way, we’re back to the old configuration management (ansible versus puppet) arguments. :)
For simple systems, the single run/actor model tends to do better IMO, for complex ones the later. But then the operator that reconciliates becomes its own beast.
January 16, 2025 at 5:48 AM
For simple systems, the single run/actor model tends to do better IMO, for complex ones the later. But then the operator that reconciliates becomes its own beast.
The problem with the second is that you can’t be sure you can ever converge to the model, since it’s part of a he design to rerun rerun rerun until spec and status converge.
January 16, 2025 at 5:46 AM
The problem with the second is that you can’t be sure you can ever converge to the model, since it’s part of a he design to rerun rerun rerun until spec and status converge.
The problem with the first is that it implies a need for much more ordering (where TF benefits from having a resource graph, which has its own issues), as on a single run you’re expected to completely converge to the model.
January 16, 2025 at 5:45 AM
The problem with the first is that it implies a need for much more ordering (where TF benefits from having a resource graph, which has its own issues), as on a single run you’re expected to completely converge to the model.
It’s the old terraform (you’re the only actor) versus kubernetes resource model (reconciliation loops/annealing) conflict. In both cases they seem to have taken a conscious approach.
January 16, 2025 at 5:44 AM
It’s the old terraform (you’re the only actor) versus kubernetes resource model (reconciliation loops/annealing) conflict. In both cases they seem to have taken a conscious approach.
Thank you for your service.
October 31, 2024 at 11:53 AM
Thank you for your service.
Where is this available?
October 31, 2024 at 11:50 AM
Where is this available?
“Decisions without accountability”, this is what we already have strategic consultancies for.
October 28, 2024 at 1:26 PM
“Decisions without accountability”, this is what we already have strategic consultancies for.