# Fleet not adding raw secret manifests

**URL:** <https://forums.suse.com/t/fleet-not-adding-raw-secret-manifests/19777>\
**Category:** General\
**Created:** [March 12, 2021, 10:31pm UTC](https://forums.suse.com/t/fleet-not-adding-raw-secret-manifests/19777 "2021-03-12T22:31:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![olds463](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/olds463/32/7318_2.png) [@olds463](https://forums.suse.com/u/olds463)\
**Post date:** [March 12, 2021, 10:31pm UTC](https://forums.suse.com/t/fleet-not-adding-raw-secret-manifests/19777/1 "2021-03-12T22:31:15Z")

</div>

I’m having trouble adding a simple secret via fleet to a cluster. So far i’ve added helm charts that work perfectly with fleet. However, I can not figure out how to add a raw yaml file to create a secret.

If I run kubectl apply -f secret.yaml the secret is added just fine. Fleet shows active, but the secret is not deployed.

My fleet.yaml is simply just

> defaultNamespace: testing  
> namespace: testing

And my folder structure is just fleet.yaml and secret.yaml in the same directory.

---

<div class="post-metadata">

**Author:** ![olds463](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/olds463/32/7318_2.png) [@olds463](https://forums.suse.com/u/olds463)\
**Post date:** [March 12, 2021, 10:37pm UTC](https://forums.suse.com/t/fleet-not-adding-raw-secret-manifests/19777/2 "2021-03-12T22:37:28Z")

</div>

The issue was I have a semi long folder name and the generated resource name by fleet exceeded some “53 character limit”