added possibility to use an existing secret for deployment

README.md

@@ -9,8 +9,6 @@ Bitwarden CRD Operator is a kubernetes Operator based on [kopf](https://github.c
 
 ## Getting started
 
-For now a few secrets need to be passed to helm. I will change this in the future to give the option to also use a kubernetes secret for this.
-
 You will need a `ClientID` and `ClientSecret` ([where to get these](https://bitwarden.com/help/personal-api-key/)) as well as your password.
 Expose these to the operator as described in this example:
 
@@ -26,6 +24,16 @@ env:
     value: "YourSuperSecurePassword"
 ```
 
+you can also create a secret manually with these information and reference the existing secret like this in the `values.yaml`:
+
+```yaml
+externalConfigSecret:
+  enabled: true
+  name: "my-existing-secret"
+```
+
+the helm template will use all environment variables from this secret, so make sure to prepare this secret with the key value pairs as described above.
+
 `BW_HOST` can be omitted if you are using the Bitwarden SaaS offering.
 
 After that it is a basic helm deployment:
@@ -78,7 +86,7 @@ type: Opaque
 ## Short Term Roadmap
 
 - [ ] support more types
-- [ ] offer option to use a existing secret in helm chart
+- [x] offer option to use a existing secret in helm chart
 - [x] host chart on gh pages
 - [x] write release pipeline
 - [x] maybe extend spec to offer modification of keys as well