# Adding certificate secrets using Rancher CLI

**URL:** <https://forums.suse.com/t/adding-certificate-secrets-using-rancher-cli/18636>\
**Category:** SUSE Rancher Prime\
**Created:** [October 22, 2020, 11:24am UTC](https://forums.suse.com/t/adding-certificate-secrets-using-rancher-cli/18636 "2020-10-22T11:24:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![hutger](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/hutger/32/10631_2.png) [@hutger](https://forums.suse.com/u/hutger)\
**Post date:** [October 22, 2020, 11:24am UTC](https://forums.suse.com/t/adding-certificate-secrets-using-rancher-cli/18636/1 "2020-10-22T11:24:17Z")

</div>

Dear all,

I’m adding certificates using RancherCLI, using the syntax below:

`$ rancher kubectl create secret tls mycert --cert=cert.crt --key.key -n harbor`

The secret is added and can be seen on Rancher console. However, I need to make the secret available to all namespaces in the project, and the default setting always created as “Available to a single namespace”.

How can I change that in order the secrets are available for being referenced on Apps form for Harbor deployment?

Thanks in advance for any help.

Hutger
