Wrong SSH username on GCE #16642
Comments
|
@DerrickMartinez what image are you using for your instances and what is the cluster creation command? |
|
Hi I am experiencing the same issue. Image I am using for my instance groups is: If I add a global public key to GCP metadata it works, however since kops instance group sets the username as admin, key will not work if I disable the global public key. this works as gcp infers that the username should be public key added by kops does not as username set is I am using kops client version 1.30.0 and kubernetes version of 1.27.7 |
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
/kind bug
1. What
kopsversion are you running? The commandkops version, will displaythis information.
v1.29.0
2. What Kubernetes version are you running?
kubectl versionwill print theversion if a cluster is running or provide the Kubernetes version specified as
a
kopsflag.1.29.5
3. What cloud provider are you using?
GCP
4. What commands did you run? What is the simplest way to reproduce this issue?
After an instance is in service you cannot SSH. The SSH username is set to admin, not ubuntu.
Here is a valid, working instance template that it should look like
It looks like fi.SecretNameSSHPrimary is a const of admin
pkg/model/gcemodel/autoscalinggroup.go: gFmtKeys = append(gFmtKeys, fmt.Sprintf("%s: %s", fi.SecretNameSSHPrimary, key))I would be willing to submit a PR depending on how we want to fix this.
The text was updated successfully, but these errors were encountered: