chore: Bump version for automation-flavors#353

[rhacs-bot]

Auto-generated: Bump automation-flavors version for https://github.com/stackrox/automation-flavors/pull/353.

[coderabbitai]

📝 Walkthrough

Walkthrough

The infra-server Helm chart metadata updates automationFlavorsVersion from 0.15.3 to 0.15.5.

Changes

Infra-server chart metadata

Layer / File(s)	Summary
Automation flavors dependency version chart/infra-server/Chart.yaml	Updates automationFlavorsVersion from 0.15.3 to 0.15.5.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: porridge

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly matches the single change: bumping the automation-flavors dependency version.
Description check	✅ Passed	The description is directly related to the version bump and references the source automation-flavors PR.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bump-automation-flavors-versions-pr-353

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[rhacs-bot]

A single node development cluster (infra-pr-1891) was allocated in production infra for this PR.

CI will attempt to deploy quay.io/rhacs-eng/infra-server: to it.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-1891 --zone us-central1-a --project acs-team-temp-dev

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🔓 You must go to to export an . Your token from the prod infra instance will not work with dev environments.

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️ Any clusters that you start using your dev infra instance should have a lifespan shorter then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance ceases to exist when the development cluster is deleted. ⚠️

Further Development

☕ If you make changes, you can commit and push and CI will take care of updating the development cluster.

🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with:

make helm-deploy

Logs

Logs for the development infra depending on your @redhat.com authuser:

• authuser=0
• authuser=1
• authuser=2

Or:

kubectl -n infra logs -l app=infra-server --tail=1 -f

[davdhacs]

PR Verification: Cluster Creation Results

Tested all non-OSD, non-IBMROKS flavors on the dev infra instance (infra-pr-1891). All 11 flavors reached READY.

ID	Flavor	Status
dh-07-23-1	aks	✅ READY
dh-07-23-2	aro	❌ FAILED (retry succeeded, see below)
dh-07-23-3	demo	✅ READY
dh-07-23-4	gke-default	✅ READY
dh-07-23-5	openshift-4	✅ READY
dh-07-23-6	openshift-4-demo	✅ READY
dh-07-23-7	openshift-4-perf-scale	✅ READY
dh-07-23-8	rosa	✅ READY
dh-07-23-9	rosahcp	✅ READY
dh-07-23-11	qa-demo	✅ READY
dh-07-23-12	eks	✅ READY
dh-07-23-13	aro (retry)	✅ READY

ARO failure is pre-existing and unrelated to this change

The initial ARO attempt (dh-07-23-2) failed due to a Microsoft Graph API replication race in az aro create — the CLI creates an AAD application registration and immediately calls addPassword, which returns a 404 when the Graph replica hasn't yet replicated the new object. A retry (dh-07-23-13) succeeded, confirming the issue is probabilistic.

This same failure has caused 100% ARO nightly failure in stackrox/stackrox since June 18 (last success). It is completely unrelated to the automation-flavors version bump in this PR, which only touches EKS (EBS CSI driver addon).

A fix has been submitted: https://github.com/stackrox/automation-flavors/pull/354