Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix and enable local_interactive feature by default #514

Conversation

ChristianZaccaria
Copy link
Contributor

@ChristianZaccaria ChristianZaccaria commented Apr 15, 2024

Rayclient Route to resolve its own ingress domain, and enable local_interactive by default

Issue link

Jira: https://issues.redhat.com/browse/RHOAIENG-5330

What changes have been made

  • Set local_interactive feature to be always enabled by default.
  • RayClient Route now resolves its own ingress domain based on the route's name and namespace.
  • Removed unused annotationBoolVal()
  • Add ingressDomain field to CFO configmap: This field has is empty by default and is used for the generation of the full rayclient client and dashboard ingress hosts. I.e., ray-dashboard-<clusterName>-<namespace>.fake.domain or rayclient-<clusterName>-<namespace>.fake.domain.

Verification steps

Checks

  • I've made sure the tests are passing.
  • Testing Strategy
    • Unit tests
    • Manual tests
    • Testing is not required for this change

main.go Outdated
@@ -115,6 +115,7 @@ func main() {
},
KubeRay: &config.KubeRayConfiguration{
RayDashboardOAuthEnabled: pointer.Bool(true),
IngressDomain: "kind",
Copy link
Contributor

@sutaakar sutaakar Apr 15, 2024

Choose a reason for hiding this comment

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

Is there a specific reason to set kind domain here?
I suppose it is already passed in config/e2e/config.yaml for tests

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You have an eagle eye, thanks for pointing that out. That was done for my own testing, changed back to fake.domain (or whichever other default domain name we prefer). Thanks!

Copy link
Contributor

Choose a reason for hiding this comment

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

Thinking why we should actually provide any default value?
Would it have more sense to keep it empty (not defined), failing operator with meaningful error message if customer won't provide it?

@ChristianZaccaria
Copy link
Contributor Author

/hold

Copy link
Contributor

@sutaakar sutaakar left a comment

Choose a reason for hiding this comment

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

/lgtm

@sutaakar
Copy link
Contributor

/approve

Copy link

openshift-ci bot commented Apr 15, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sutaakar

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 61c7bca into project-codeflare:main Apr 15, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants