<#3826 [Housekeeping] Add templates to flyte-core ...
# flyte-github
a
#3826 [Housekeeping] Add templates to flyte-core to handle auth Issue created by davidmirror-ops Motivation: Why do you think this is important? When using the
flyte-core
chart with
auth
enabled, even with the internal auth server, a user needs to manually: 1. Edit the
flyte-admin-secrets
secret and add the
oidc_client_secret
2. Edit the
flyte-admin-base-config
configmap to add the required information for OIDC 3. Rollout the deployments to make Flyte components aware of the changes If using an External auth server, more manual edits to the configmap have to be done. Goal: What should the final outcome look like, ideally? Similar to how
flyte-binary
works, whenever a user enables
auth
, they should be able to provide the parameters in the values file and then Helm templates should do the work to update the secret and configmap without user intervention. Describe alternatives you've considered None Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte