TLDR: most GCP projects have enable-oslogin set to TRUE by default. However to inject a ssh-key through metadata and then login successfully, the enable-oslogin must be set to FALSE.
Longer: When user runs this repo with default setting, likely enable-oslogin is set to TRUE on the GCP project resulting in user receiving SSH error of Permission Denied. to avoid this another metadata field must be set to over write project level settings.
TLDR: most GCP projects have enable-oslogin set to TRUE by default. However to inject a ssh-key through metadata and then login successfully, the enable-oslogin must be set to FALSE.
Longer: When user runs this repo with default setting, likely enable-oslogin is set to TRUE on the GCP project resulting in user receiving SSH error of
Permission Denied
. to avoid this another metadata field must be set to over write project level settings.