Let's update the credentials secret for Ironic with a new key clouds.yaml and value of the actual YAML that can be used with the baremetal CLI.
The configuration should probably have two cloud records: internal that uses the service URL and external that uses the host IP of Ironic. Make sure our client container image can work with this configuration if the secret is mounted at the appropriate location.
Alternative: a new field to opt into the clouds.yaml generation? I don't see much point in it because it will contain the same confidential data: user name and password, just in a different form.
/kind feature
/help
Let's update the credentials secret for Ironic with a new key
clouds.yamland value of the actual YAML that can be used with the baremetal CLI.The configuration should probably have two cloud records:
internalthat uses the service URL andexternalthat uses the host IP of Ironic. Make sure our client container image can work with this configuration if the secret is mounted at the appropriate location.Alternative: a new field to opt into the clouds.yaml generation? I don't see much point in it because it will contain the same confidential data: user name and password, just in a different form.
/kind feature
/help