Closed eyenx closed 10 months ago
Any Updates on this? @akshaysngupta
@eyenx can you share if you have tested this change ?
@akshaysngupta I added unittests for this explicit example.
=== RUN TestChart
=== RUN TestChart/sample-config-empty
=== RUN TestChart/sample-config-existing-secret
=== RUN TestChart/sample-config-prohibited-target
=== RUN TestChart/sample-config-workload-identity
=== RUN TestChart/sample-config
--- PASS: TestChart (0.24s)
--- PASS: TestChart/sample-config-empty (0.05s)
--- PASS: TestChart/sample-config-existing-secret (0.04s)
--- PASS: TestChart/sample-config-prohibited-target (0.05s)
--- PASS: TestChart/sample-config-workload-identity (0.05s)
--- PASS: TestChart/sample-config (0.05s)
PASS
ok github.com/Azure/application-gateway-kubernetes-ingress/helm/ingress-azure/tests (cached)
Any Update @akshaysngupta
Any Update @akshaysngupta ?
Any Update @akshaysngupta ?
Any Update @akshaysngupta ?
Hi @akshaysngupta, is there a chance to merge these changes in the near future? We're stuck at this point and would want to avoid coding a workaround.
Best Regards Wolfgang
Seems like Microsoft does not care about this. @akshaysngupta
Not even a reaction if it is in scope or not.
Really sad.
@eyenx sorry for delaying this PR so much. It looks perfectly fine. I have added a minor comment.
Checklist
Fixes
.Description
As of today, when using the
servicePrincipal
method for achieving authentication, thesecretJSON
needs to be added as value in the chart.With this change, the secret can already exist, which allows us to grab it from an external source like Azure Key Vault....
This way, the
secretJSON
value which is sensitive does not need to be added to the values and can be grabbed directly from an already existing Kubernetes Seecret.Fixes
Unable to deploy AGIC without exposing the
secretJSON
in the Helm values.Signed-off-by: Toni Tauro toni.tauro@adfinis.com