This article provides information on a workaround for the issue and correct the broken network access for ABX actions.
ABX agent is started using a docker run command, which provides the hardcoded kube-dns address. When k8s subnets are changed, the kube-dns address is no longer valid and ABX actions have no access to the proxy and hence no network access.
VMware is aware of this issue.
A resolution for this issue is being evaluated for inclusion in a future release.
To work around this issue you will need to follow these steps:
base64 -d <<< '/Td6WFoAAATm1rRGAgAhARYAAAB0L+Wj4AYXA1xdABGIQkY99Bhqpmevep9yj5xO8pryhHT59/XljWc+hwVZTUfDg1ejdkzLQv8q5iUjza8BZmjIRHE2f2ak0zT1wFWKdtuWRZvJF7XnAndTrYSU3XaGZVvFIe9Dd5bHpv6i3V88O2dxRbHQdx3MZhHr2+av8NHm9k8zXqYS/J1SS9ryVTGWWFSNTFDtYWmeeELPFtzL7d5VjnGB7vK1Sg1o6I3DyDAncBVzI8yl3IUiZI4zKA3owwove6nqR2YxL6eeAW+ATFdencI9tRxjKXc/6hCCF1q2kktxSLvDQk3ZJDiK2KW62gYCNi4/m6rr8KwbNyyJOGUhNegp1VqUZ18/qbCPyCsG9yf/8S0k+oJvhqBd0h1z7a0amqw01OhCTw7y8l5KQTv8bL4TyCFExSa4dHfxLHXD23MiWb3oAIBoLpTL2J7BEZAT0zWpjj2vBDYATGLBeZoQfeyg3grtuKpoXsFYrXn8YRKOX1MUu8WY05bd8ZuZyz5Vd/Eyv2UYiGOElYdwyJER+cjK9TQfy+rBT2cGMHvCqBVsp0glcPtrS0Pyln+1aeIbL/PoXF7AbDwdEDywLaotMY65iWTZSXtuvbOhLCFKRheyN4zsu97R9eFDWlPEekp8GoGBkwkqGfw2E7MrEm1V9ss4z3llIIr+7EIVyTs3CAliOu4By3kVlHa3nV43FASPB/ltH8Ha5SD/LelE+nvWfGCciqgX+g/4oN8mSLXfvJbOTA3PQBDUos8ELKngYSADH6Y5Xu5joEKkGFNpG+xxQBAUS1Xalv5Bt4a8cOI8JugYJxnwnCZblQWqrM2Oxfi3UcYpdXX1ve3Nj4rUfFurcUltdsS9gyy0lYXOZ1Rc1bn0k6jO889v3exaEZpjKeffy92gAX8UchN9S72mBU8tJHuO5Ro8VytWlAl3iH7VVWoadiIAbtlWKFJvmn3aRy1yBZRE6EuJTeistUQNwAjFsUnNS83LZLEJ+mIAxwkTDCFkq8+YS+w8+HY944eAyLw1cl6f2Q45g2EzeL4w6CWpmGk8UD3ivo3HMDeBbNSLt0DvfqEz7SX/h8a0766OyaIV/5ci3O7HQ7iAowLFr/TXVNecjXPSYAW9EwqZ+mGU47m6ILt7wPqvaTTHXqbHJpbGY2YVsteQALXkdGuUo7vXAAH4BpgMAAAmijrEscRn+wIAAAAABFla' | xz -d | bash -