rossoctl / rossoctl/workload-harness
mlflow-oauth-secret name doesn't match cluster variants (--auth-mode secret)
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 5
- Forks
- 6
- Avg merge
- 11h 37m
- Merged PRs (30d)
- 1
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in analyze-run.sh and trace the secret lookup used by --auth-mode secret with --openshift. Reproduce the supplied command against a cluster using an mlflow-oauth-proxy-* name, then verify that an --mlflow-secret NAME override uses the provided name while the default remains mlflow-oauth-secret.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 74/100