v0.10.0 doesn't create 'auth-secrets' secret when metadata_service_authentication is enabled in the helm chart

[nachiket-juneja]

Describe the bug
We've been trying to install the latest 0.10.0 version of DataHub and we feel there is a bug. We currently have enabled the metadata_service_authentication flag in the value.yaml in the helm installation. We are now moving to 0.10.0 using chart version 0.2.154.
When metadata_service_authentication value is true, the system-update job fails with the CreateConfigError since the 'datahub-auth-secrets' secret doesn't get created. On the other hand, if we put metadata_service_authentication as false, the system update job passes and the secret is also created successfully.
Maybe an issue with the helm templates which creates the secret. Unsure about the root cause, but I think this could be a potential problem.
Please let me know if this is the desired behavior or we are missing something.

To Reproduce
Steps to reproduce the behavior:

1. Enable metadata_service_authentication to true in the 'global' section in the values.yaml for the datahub helm chart
2. Set the datahub version to 0.10.0
3. Run the helm install command. The system-update-job throws an ContainerConfigError since the datahub-auth-secrets secret is not created.

Expected behavior
Datahub should have installed successfully without any errors

[matthijsvanderloos]

I created an issue for this in the DataHub Helm repo as well: acryldata/datahub-helm#265

[nachiket-juneja]

Any updates on this?

[jinlintt]

Any updates on this? We are seeing exactly same issue.

[github-actions]

This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io

[MadisLemsalu]

Same issue here

[github-actions]

This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io

[github-actions]

This issue was closed because it has been inactive for 30 days since being marked as stale.