4 ms·
Strategy is how you deal with idempotency and consistency in a distributed environment. Your manifest is idempotent but isn't applied instantly. You can apply
by ses1984 7y ago
Strategy is how you deal with idempotency and consistency in a distributed environment.
Your manifest is idempotent but isn't applied instantly.
You can apply a manifest, and get into some broken state, how do you recover? What if you try to roll back and things get worse?
- cfors 7y agoI suppose if you're not using git-ops related deployments, but Git has been proven to work well for this exact process. If you are tracking your releases as part of a Git commit, then you rollback with that. Doesn't seem that complicated, but maybe I'm missing some benefits of this strategy that others with more experience managing K8s resources have had. Edit: Retroactively speaking you also don't need to leverage etcd to store n*x your K8s resources in a secrets file where n is the potential rollback number, it's all stored in a Git repository.