Summary
The user encountered deployment issues with flyte-binary on a Kubernetes cluster after changing the release name from "flyte-backend" to "flyte-binary." This change led to workflow execution failures due to lingering references to the old service name. Despite uninstalling and reinstalling the deployment and deleting related namespaces and database tables, errors persisted, particularly with tasks requesting secrets. Reverting to the old release name did not fix the issue, as errors still referenced the new service name. The user confirmed that configuration files were correct, but the source of the old reference was unclear. The problem was resolved by deleting an old "MutatingWebhookConfigurations" resource that referenced the old service name, which Helm does not manage. The user also inquired about alternative methods for consuming secrets and expressed concerns about the uninstall process not removing all components, suggesting it might be a bug worth reporting. They mentioned they intended to open an issue but did not get around to it.