Update overview.md

docs/dev/features/netapp-mounting/overview.md

@@ -55,6 +55,11 @@ This works like all the other profiles controllers, and steps can be taken from
 It will need to change based on work done in the Manage Filers page in Central dashboard when users select what filer (and level of) that they have access to.
 Additionally the contents of the secret will also need additions, as when I was creating this controller I was not aware of the `BUCKET` itself needing to be a part of the secret (you could retrieve it from what populates the Manage Filers page but that is more complicated and another hoop to jump through).
 
+**Until the above works, you must manually create secrets**
+To do this, you need the following information; `namespace`, `S3_ACCESS`, `S3_BUCKET`, `S3_SECRET`, and `S3_URL`. The actual entries of the secret (S3) can be retrieved from the Netapp team, as when users are onboarded someone will send you their ACCESS and SECRET keys. The bucket name would match what the share name is in the request, for example in [this issue](https://jirab.statcan.ca/browse/ZPS-24?focusedId=3011155&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-3011155) the value for `S3_BUCKET` would be `istdim`, as the bucket names must be lowercased (another one to look out for is `_`'s get converted to `-`'s, if unsure ask Roham for the bucket name. 
+For the `S3_URL` this is constant and can view the respective URL from existing secrets
+Do not forget to do encode them when creating the secret, I have a utility that just does `echo -n $1 | base64` that I call so I can copy paste it easily.
+
 -----------------------
 
 ## [Mutating Webhook](https://github.com/StatCan/filer-sidecar-injector)