You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened?#897 enables us to refactor the metadata code to be simpler , to be 100% clear that the driver will retrieve NodeGetInfo info from EITHER ec2 metadata OR k8s client. This will also let us simplify the unit tests and write a new unit test that, if metadata is enabled, do not try to create a k8s client.
What you expected to happen?
How to reproduce it (as minimally and precisely as possible)?
Anything else we need to know?:
Environment
Kubernetes version (use kubectl version):
Driver version:
The text was updated successfully, but these errors were encountered:
wongma7
added
the
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
label
May 21, 2021
What happened? #897 enables us to refactor the metadata code to be simpler , to be 100% clear that the driver will retrieve NodeGetInfo info from EITHER ec2 metadata OR k8s client. This will also let us simplify the unit tests and write a new unit test that, if metadata is enabled, do not try to create a k8s client.
What you expected to happen?
How to reproduce it (as minimally and precisely as possible)?
Anything else we need to know?:
Environment
kubectl version
):The text was updated successfully, but these errors were encountered: