relativitydev/containership

Organizing CMO, RegistryConfig, Secrets and Namespaces

lenardchristopher opened this issue · 2 comments

lenardchristopher commented

Glossary

  • ContainerManagementObject (CMO): CRD. This is where images, their supported tags, and intended registry destinations are defined.
  • RegistryConfig: CRD that containers the list of regsitries the operator will push and pull from. It also references the secret with the authentication credentials for the registry

Issue
How should CMOs and RegistryConfigs to be organized in namespaces and secrets?

lenardchristopher commented

Multiple CMOs are intended to be deployed in a cluster in n namespaces. It is up to developers to decide how to organize them -- one per application, one per team, etc. Only one RegistryConfig should exist and it should be in the same namespace as containership operator. The dockerconfig.json secret(s) for the registries should also exist in the operator's namespace.

lenardchristopher commented

This issue is resolved here: #4