Block a user
fix: apply different network policies based on current target
This feels entirely correct. As we discussed, the complexity comes from the Anywhere part of K8sAnywhere module, so it should be solved within the logical boundaries of K8sAnywhere. And all that K8sAnywhere has to do is decide which implementation to delegate to, which a Strategy seems perfectly suited for here.
refactor: Remove InterpretStatus/Error & Outcome from Topology
I love this! Feels natural and clean.
refactor: Interpret score with a provided method on Score
I 100% agree with the pros as required elements of the design :
No need to change existing Score/Interpret implementations Easier and more intuitive for developers to discover and use …