Skip to content

Support flag in ray plugin config to optionally disable ingress for Ray cluster#6905

Merged
EngHabu merged 2 commits intoflyteorg:masterfrom
mickjermsurawong-openai:dev/mickj-support-disable-ingress
Feb 9, 2026
Merged

Support flag in ray plugin config to optionally disable ingress for Ray cluster#6905
EngHabu merged 2 commits intoflyteorg:masterfrom
mickjermsurawong-openai:dev/mickj-support-disable-ingress

Conversation

@mickjermsurawong-openai
Copy link
Contributor

@mickjermsurawong-openai mickjermsurawong-openai commented Feb 9, 2026

Tracking issue

  • Allow disabling ingress for KubeRay according to spec.
  • Default of this flag changes no behavior of existing Ray cluster creation

Why are the changes needed?

  • Nginx ingress is now official retired , and some organizations now banned its usage
  • Disabling this mean that the dashboard won't work, but running of Rayjob itself isn't affected

What changes were proposed in this pull request?

How was this patch tested?

Labels

  • Added unit test
  • Built locally and tested that rayplugin still launch job, created ephemeral cluster, head and workers correctly.

Setup process

Screenshots

Check all the applicable boxes

  • I updated the documentation accordingly.
  • All new and existing tests passed.
  • All commits are signed-off.

Related PRs

Docs link

Signed-off-by: mickjermsurawong <mickjermsurawong@openai.com>
@mickjermsurawong-openai mickjermsurawong-openai force-pushed the dev/mickj-support-disable-ingress branch from 88e8d13 to 58dda2d Compare February 9, 2026 00:34
TTLSecondsAfterFinished: 3600,
ServiceType: "NodePort",
IncludeDashboard: true,
EnableIngress: true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like booleans to default to false... So I think this should be DisableIngress

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed thank you for fast response!

Signed-off-by: mickjermsurawong <mickjermsurawong@openai.com>
@mickjermsurawong-openai mickjermsurawong-openai force-pushed the dev/mickj-support-disable-ingress branch from 91ee01c to fbfd6b8 Compare February 9, 2026 00:44
@EngHabu EngHabu enabled auto-merge (squash) February 9, 2026 02:08
@codecov
Copy link

codecov bot commented Feb 9, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.95%. Comparing base (00eea86) to head (fbfd6b8).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #6905   +/-   ##
=======================================
  Coverage   56.95%   56.95%           
=======================================
  Files         929      929           
  Lines       58151    58152    +1     
=======================================
+ Hits        33120    33121    +1     
  Misses      21989    21989           
  Partials     3042     3042           
Flag Coverage Δ
unittests-datacatalog 53.51% <ø> (ø)
unittests-flyteadmin 53.10% <ø> (ø)
unittests-flytecopilot 43.06% <ø> (ø)
unittests-flytectl 64.02% <ø> (ø)
unittests-flyteidl 75.71% <ø> (ø)
unittests-flyteplugins 60.14% <100.00%> (+<0.01%) ⬆️
unittests-flytepropeller 53.63% <ø> (ø)
unittests-flytestdlib 63.29% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@EngHabu EngHabu merged commit 14b6bbf into flyteorg:master Feb 9, 2026
48 of 49 checks passed
@welcome
Copy link

welcome bot commented Feb 9, 2026

Congrats on merging your first pull request! 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants