Verify openstackCredsFile #550
Assignees
Comments
Merged
|
The existing pattern (e.g. for pull secrets and SSH pubkeys) is to try and pick a sane default, but to have a wizard prompt when we aren't sure and an environment variable to override. That seems sane to me, if we have doubts about our automatic-detection logic. And even if we do get that wrong, folks can now do a multi-step install to slot in the creds they wish we'd found :). |
|
/assign @flaper87 |
flaper87
added a commit
to flaper87/installer
that referenced
this issue
Nov 1, 2018
OpenStack creds cold be in 3 different paths (etc, home config and current dir). Instead of re-implementing the logic to find and read the clouds.yaml file, we should use gophercloud which is the standard go library for OpenStack. Note that deployments on OpenStack are currently broken unless there's a `clouds.yaml` under `/etc/openstack`. Fixes openshift#550
flaper87
added a commit
to flaper87/installer
that referenced
this issue
Nov 1, 2018
OpenStack creds cold be in 3 different paths (etc, home config and current dir). Instead of re-implementing the logic to find and read the clouds.yaml file, we should use gophercloud which is the standard go library for OpenStack. Note that deployments on OpenStack are currently broken unless there's a `clouds.yaml` under `/etc/openstack`. Fixes openshift#550
flaper87
added a commit
to flaper87/installer
that referenced
this issue
Nov 2, 2018
OpenStack creds cold be in 3 different paths (etc, home config and current dir). Instead of re-implementing the logic to find and read the clouds.yaml file, we should use gophercloud which is the standard go library for OpenStack. Note that deployments on OpenStack are currently broken unless there's a `clouds.yaml` under `/etc/openstack`. Fixes openshift#550
flaper87
added a commit
to flaper87/installer
that referenced
this issue
Nov 2, 2018
OpenStack creds cold be in 3 different paths (etc, home config and current dir). Instead of re-implementing the logic to find and read the clouds.yaml file, we should use gophercloud which is the standard go library for OpenStack. Note that deployments on OpenStack are currently broken unless there's a `clouds.yaml` under `/etc/openstack`. Fixes openshift#550
flaper87
added a commit
to flaper87/installer
that referenced
this issue
Nov 5, 2018
OpenStack creds cold be in 3 different paths (etc, home config and current dir). Instead of re-implementing the logic to find and read the clouds.yaml file, we should use gophercloud which is the standard go library for OpenStack. Note that deployments on OpenStack are currently broken unless there's a clouds.yaml under /etc/openstack. Fixes openshift#550
flaper87
added a commit
to flaper87/installer
that referenced
this issue
Nov 5, 2018
OpenStack creds cold be in 3 different paths (etc, home config and current dir). Instead of re-implementing the logic to find and read the clouds.yaml file, we should use gophercloud which is the standard go library for OpenStack. Note that deployments on OpenStack are currently broken unless there's a clouds.yaml under /etc/openstack. Fixes openshift#550
flaper87
added a commit
to flaper87/installer
that referenced
this issue
Nov 8, 2018
OpenStack creds cold be in 3 different paths (etc, home config and current dir). Instead of re-implementing the logic to find and read the clouds.yaml file, we should use gophercloud which is the standard go library for OpenStack. Note that deployments on OpenStack are currently broken unless there's a clouds.yaml under /etc/openstack. Fixes openshift#550
flaper87
added a commit
to flaper87/installer
that referenced
this issue
Nov 8, 2018
OpenStack creds cold be in 3 different paths (etc, home config and current dir). Instead of re-implementing the logic to find and read the clouds.yaml file, we should use gophercloud which is the standard go library for OpenStack. Note that deployments on OpenStack are currently broken unless there's a clouds.yaml under /etc/openstack. Fixes openshift#550
flaper87
added a commit
to flaper87/installer
that referenced
this issue
Nov 8, 2018
OpenStack creds cold be in 3 different paths (etc, home config and current dir). Instead of re-implementing the logic to find and read the clouds.yaml file, we should use gophercloud which is the standard go library for OpenStack. Note that deployments on OpenStack are currently broken unless there's a clouds.yaml under /etc/openstack. Fixes openshift#550
flaper87
added a commit
to flaper87/installer
that referenced
this issue
Nov 13, 2018
OpenStack creds cold be in 3 different paths (etc, home config and current dir). Instead of re-implementing the logic to find and read the clouds.yaml file, we should use gophercloud which is the standard go library for OpenStack. Note that deployments on OpenStack are currently broken unless there's a clouds.yaml under /etc/openstack. Fixes openshift#550
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Platform openstack:
With this PR, #427 need to verify that the correct file to get OpenStack creds is this:
/etc/openstack/clouds.yaml. Another option would beopenStackCredsFile = os.Getenv("HOME") + "/.config/openstack"Once the OpenStack folks verify, this issue can be closed.
With an OpenStack launch of installer, you will see a secret
openstack-credsin-n kube-systemwith encodedclouds.yamlin the data of the secret. Might want to add multiple files/conditional to what creds file is found on the host system during launch in that secret.The text was updated successfully, but these errors were encountered: