# Create ImagePullSecrets for the Proxy Service in multiple namespaces

**URL:** <https://community.replicated.com/t/create-imagepullsecrets-for-the-proxy-service-in-multiple-namespaces/1295>\
**Category:** How do I?\
**Tags:** kots\
**Created:** [September 20, 2023, 2:53pm UTC](https://community.replicated.com/t/create-imagepullsecrets-for-the-proxy-service-in-multiple-namespaces/1295 "2023-09-20T14:53:14Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jdewinne](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/jdewinne/32/152_2.png) [@jdewinne](https://community.replicated.com/u/jdewinne)\
**Post date:** [September 20, 2023, 4:37pm UTC](https://community.replicated.com/t/create-imagepullsecrets-for-the-proxy-service-in-multiple-namespaces/1295/3 "2023-09-20T16:37:51Z")

</div>

Hi @Lukasz_Werenkowicz

Thanks for already partially answering your question. 🙏  
You are correct The [additionalNamespaces](https://docs.replicated.com/reference/custom-resource-application#additionalnamespaces) at this moment does not support go templating. This means that they have to be `static`, or you use `"*"`.

If you create namespaces in a dynamic way, you’ll have to also ensure the pull secret is created, which is very similar to using [operators](https://docs.replicated.com/vendor/operator-referencing-images#determining-the-imagepullsecret) with kots.

Additionally, you might want to check how to [manage namespaces in a secured environment](https://community.replicated.com/t/managing-custom-namespaces-in-a-secured-environment/922). In many situations you’re not allowed to create additional namespaces, and sometimes everything has to be deployed in a single namespace.

---

_[View the full topic](https://community.replicated.com/t/create-imagepullsecrets-for-the-proxy-service-in-multiple-namespaces/1295)._