Summary
analyze-run.sh --openshift --auth-mode secret looks for a secret named mlflow-oauth-secret in the redhat-ods-applications namespace, but on a tested RHOAI cluster the actual secrets are named mlflow-oauth-proxy-* variants — not mlflow-oauth-secret.
This may be a cluster-setup gap, or the script may need an --mlflow-secret override flag so callers can supply the correct name without patching the script.
Steps to reproduce
./analyze-run.sh --openshift <domain> --auth-mode secret --window 3h ...
Fails with secret-not-found if the cluster uses a different naming convention.
Possible fix
Add an --mlflow-secret NAME flag (defaulting to mlflow-oauth-secret) so the caller can specify the actual secret name.
Found in
PR #33 review by @kellyaa.
Summary
analyze-run.sh --openshift --auth-mode secretlooks for a secret namedmlflow-oauth-secretin theredhat-ods-applicationsnamespace, but on a tested RHOAI cluster the actual secrets are namedmlflow-oauth-proxy-*variants — notmlflow-oauth-secret.This may be a cluster-setup gap, or the script may need an
--mlflow-secretoverride flag so callers can supply the correct name without patching the script.Steps to reproduce
Fails with secret-not-found if the cluster uses a different naming convention.
Possible fix
Add an
--mlflow-secret NAMEflag (defaulting tomlflow-oauth-secret) so the caller can specify the actual secret name.Found in
PR #33 review by @kellyaa.