Skip to content

RFE: generate a secret with clouds.yaml #153

@dtantsur

Description

@dtantsur

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.triage/acceptedIndicates an issue is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions