You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add imagePullSecrets to the tenant CR, .spec.podOptions.imagePullSecrets. These imagePullSecrets gets automatically appended to the pod spec when a pod in the tenant is deployed. This is great when a GlobalTenantResource with imagePullSecrets is used, so these imagePullSecrets are automatically added and the tenantUser/owner doesn't have to do a thing for it :)
What would the new user story look like?
How would the new interaction with Capsule look like? E.g.
Tenant owner creates a new Pod
The imagePullSecrets are added to the Pod
The tenant owner is happy and worryfree about these imagePullSecrets that we manage for him and he doesn't have to think about adding it to his podSpec.
Same here as with the annotations, we will add a new Hook system, Kyverno like, to apply such patches based on selected tenants or namespaces, decoupling it from tenants
In the meanwhile, since you're using Tenant Resources, you could update the default ServiceAccount on each Namespace where the secret is replicated to use the provided image pull secret.
Describe the feature
Add imagePullSecrets to the
tenant
CR,.spec.podOptions.imagePullSecrets
. These imagePullSecrets gets automatically appended to the pod spec when a pod in the tenant is deployed. This is great when aGlobalTenantResource
withimagePullSecrets
is used, so these imagePullSecrets are automatically added and the tenantUser/owner doesn't have to do a thing for it :)What would the new user story look like?
How would the new interaction with Capsule look like? E.g.
And just for reference, to get the global picture, the globaltenantresource:
Expected behavior
ImagePullSecrets are automatically added to all pods in a tenant.
The text was updated successfully, but these errors were encountered: