Lessons learned in designing and implementing operators for Kubernetes
- API anti-patterns to avoid in operator design
- Challenges in bridging the gap between imperative infrastructure management and declarative Kubernetes API
- Maximizing usefulness of client's cache and avoiding memory bloat
- Efficiently interacting with multiple clusters from a single operator instance
- Minimizing load imposed on the API server
The speaker shared an anecdote about a common anti-pattern of putting important information in annotations instead of the spec of a resource, which can lead to future regret.