update provider base image
Type of change
-
Bug Fix -
Feature - [*] Base image upgrade
Related to #312 (closed) Related to #314 (closed)
Does this introduce a change in the core logic?
- [NO]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS - [*] Azure
-
GCP -
IBM
Does this introduce a breaking change?
- [NO]
What is the current behavior?
Current base image of gcz-provider is node:16.15.1
What is the new/expected behavior?
Upgraded base image of gcz-provider is node:16.20.2-alpine
Any other useful information
Changes are tested in azure kubernetes deployment. No issues detected.
Edited by saketh somaraju [EPAM]