Kishor Joshi
Kishor Joshi
@olemarkus, we could get the Node resource, extract the providerID and invoke the ec2 `DescribeInstances` API to get the VPC id. The controller already has permissions to access the Node...
@timharsch, I'm closing the issue. Feel free to reach out to us if you have further concerns.
@micksabox, which 1.x version were you on previously?
@syscll, you can run `make docs-preview` and verify the documentation page on your local browser.
@syscll, I feel the `clientConfig` section in step 4 is confusing. We need to clarify it further so users don't need to spend time trying to debug failures.
@stevo-f3, when you make changes to the ingress/service, controller will restore the changes. We will investigate further why the sync-period setting did not work in this case.
@kennedy-dan, are there other pods in the cluster with similar errors (unable to talk to the api server) or this is the only pod? Does the pod get restarted after...