Feat: 🚀 use external-secret in multiple namespaces

[h1manshu98]

What

• Updated istio-ingress addon to use Internet-facing and Internal ingresses.
• Added feature to use externalSecret in other namespaces.
• To do so User need to create an TrustRelationship policy where user will pass information of other namespace.
• Then in their application's service-account.yaml, user have to pass IAMRole annotation as below -

apiVersion: v1
kind: ServiceAccount
metadata:
  name: 
  annotations:
    eks.amazonaws.com/role-arn: "arn:aws:iam::12345678912:role/external-secrets-CLUSTER_NAME"

Why

• Previously we were only able to use external-secret in the namespace where this addon is deployed [kube-system].
• To use this external-secret in different namespace-X we had to create a ServiceAccount in namespace-X with AWSSecretManager permission.

[nileshgadgi]

LGTM!

[themaniskshah]

LGTM!