The key in the example is kubernetes.io/colo-tx-name but the documentation refers to kubernetes.io/e2e-az-name
Just mentioning as it was a bit confusing at first.
The affinity should work with whatever the name used may be. The key is equal to something, and thus the scheduler will go looking for that something in order to determine where the pod will be deployed, as long as the key and value are used consistently.
Sure. I was just pointing out that the key used in the example on 11.14 is not the same as the key mentioned in the text underneath the example, so it looks like a typo?
I discovered that too. I've raised a similar erratum request.