Hello community! We've been trying to install the latest 0.10.0 version of DataHub and we feel there is a bug. Please correct me if we are wrong. 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. Thanks in advance

Hi @best-umbrella-88325, could you submit an issue here with specific steps to reproduce?

Hey @astonishing-answer-96712 Raised issue https://github.com/datahub-project/datahub/issues/7508

Thank you! The team will take a look and get back to you 🙂

Sure, thanks

We are seeing the same issue. Is there a solution soon?

As a workaround for now, we've created the datahub-auth-secret separately..

Hey, working on getting this prioritized, thanks!