Merge branch 'beach-team' of https://github.com/external-secrets/external-secrets into beach-team

docs/eso-blogs.md

@@ -35,3 +35,7 @@ Tiexin Guo Writes about Kubernetes hardening in this series of blogs. He mention
 ## [Tutorial: How to manage secrets in OpenShift using Vault and External Secrets Operator](https://youtu.be/PgiXKBTel1E)
 
 Balkrishna Pandey published a video tutorial and a [blog post](https://goglides.io/how-to-manage-secrets-in-openshift-using-vault-and-external-secrets/1164/) on integrating HashiCorp Vault and External Secret Operator (ESO) to manage application secrets on OpenShift Cluster. In this blog, he demonstrates the strength of the `ClusterSecretStore` functionality, a cluster scoped SecretStore and is global to the Cluster that all `ExternalSecrets` can reference from all namespaces.
+
+## [Tutorial: Leverage AWS secrets stores from EKS Fargate with External Secrets Operator](https://aws.amazon.com/blogs/containers/leverage-aws-secrets-stores-from-eks-fargate-with-external-secrets-operator/)
+
+In this AWS Containers blog post, Ryan writes about how to leverage External Secret Operator with an EKS Fargate cluster using IAM Roles for Service Accounts (IRSA). This setup supports the requirements of Fargate based workloads. [Leverage AWS secrets stores from EKS Fargate with External Secrets Operator](https://aws.amazon.com/blogs/containers/leverage-aws-secrets-stores-from-eks-fargate-with-external-secrets-operator/)

docs/eso-demos.md

@@ -2,6 +2,12 @@
 
 A list of demos given by people going through simple setups with ESO. Feel free to let us know if you have a demo that you want to include here!
 
+## Manage Kubernetes Secrets With External Secrets Operator on DevOps Toolkit
+
+Viktor Farvik shows us how to use ESO with GCP provider and explores a simple workflow with the project.
+
+[![Manage Kubernetes Secrets With External Secrets Operator on DevOps Toolkit](https://img.youtube.com/vi/SyRZe5YVCVk/0.jpg)](https://www.youtube.com/watch?v=SyRZe5YVCVk)
+
 ## Managing Kubernetes Secrets: Comparing External Secrets Operator and Secrets Store CSI Driver
 
 Kim Schlesinger and Daniel Hix show us how to install and use both projects, comparing their features and limitations in different situations.

docs/guides-common-k8s-secret-types.md

@@ -19,6 +19,14 @@ Then create a ExternalSecret resource taking advantage of templating to populate
 {% include 'gcpsm-docker-config-externalsecret.yaml' %}
 ```
 
+For Helm users: since Helm interprets the template above, the ExternalSecret resource can be written this way:
+
+```yaml
+{% include 'gcpsm-docker-config-helm-externalsecret.yaml' %}
+```
+
+For more information, please see [this issue](https://github.com/helm/helm/issues/2798)
+
 This will generate a valid dockerconfigjson secret for you to use!
 
 You can get the final value with:
@@ -73,5 +81,5 @@ kubectl get secret secret-to-be-created -n <namespace> | -o jsonpath="{.data.ssh
 
 ## More examples
 
-!!! note "We need more examples here" 
-    Feel free to contribute with our docs and add more examples here!
+!!! note "We need more examples here"
+    Feel free to contribute with our docs and add more examples here!

docs/snippets/gcpsm-docker-config-helm-externalsecret.yaml

@@ -0,0 +1,23 @@
+{% raw %}
+apiVersion: external-secrets.io/v1beta1
+kind: ExternalSecret
+metadata:
+  name: dk-cfg-example
+spec:
+  refreshInterval: 1h
+  secretStoreRef:
+    name: example
+    kind: SecretStore
+  target:
+    template:
+      type: kubernetes.io/dockerconfigjson
+      engineVersion: v2
+      data:
+        .dockerconfigjson: "{{ `{{ .mysecret }}` }}"
+    name: secret-to-be-created
+    creationPolicy: Owner
+  data:
+  - secretKey: mysecret
+    remoteRef:
+      key: docker-config-example
+{% endraw %}