Bug #57387
openBootstrapping with custom registry should set mgr config keys
0%
Description
Bootstrapping a cluster using a custom registry, with options --registry-url --registry-username --registry-password given to cephadm bootstrap should set the relevant mgr configuration keys mgr/cephadm/registry_url, mgr/cephadm/registry_username and mgr/cephadm/registry_password, respectively.
Currently using a custom registry is very cumbersome when neither cephadm bootstrap nor cephadm registry-login actually set these configuration keys, making deployment fail on any subsequent server with a registry pull error.
Updated by Voja Molani over 1 year ago
Not sure what would need to be done for the cephadm to correctly login to a container registry for all machines after the initial bootstrap. Setting the listed mgr config values didn't seem to help.
It should not be necessary to manually download images, or manually login to container registry with podman to get these deployed.
Updated by Redouane Kachach Elhichou 11 months ago
- Status changed from New to In Progress
- Assignee set to Redouane Kachach Elhichou
Updated by Redouane Kachach Elhichou 10 months ago
- Status changed from In Progress to New
- Assignee deleted (
Redouane Kachach Elhichou)