-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Understand the Task
Description
Currently the openmcp-operator creates its own namespace for each ClusterProvider
, ServiceProvider
and SystemService
on the platform cluster. In these namespaces the Kubernetes resources for the deployment are being created/updated.
These deployments may need to have image pull secrets referenced. Image pull secrets can only be read from the same namespace as the deployment that is referencing it.
Since the namespace is created after the user has created the Provider
resource, it is not feasible for the user to create the image pull secret in conjunction with the Provider
resource.
Therefore the following change is being proposed:
Create all resources for Providers
in the openmcp-system
namespace with a prefix that avoids collision.
By that change, the user can create the image pull secret in the already existing openmcp-system
namespace.
It would then also be possible to share the same image pull secret for multiple/all Provider
resources.
Any further valuable resources.
No response
What is required to accept the Task as done.
Done Criteria
- ...
- Code has been reviewed by other team members
- Internal technical Documentation created/updated
- New / changed code is documented
- Unit Tests created for new code or existing Unit Tests updated
- Integration Test Suite updated
- Enduser Documentation updated (if applicable)
- Successful demonstration in Review