Skip to content

Conversation

Fluder-Paradyne
Copy link
Contributor

@Fluder-Paradyne Fluder-Paradyne commented Jul 1, 2025

Description

allow the Ingress backend to use a user-defined serviceName if specified, otherwise defaulting to the clusterName.

Issues Resolved

#1042

Check List

  • Commits are signed per the DCO using --signoff
  • Unittest added for the new/changed functionality and all unit tests are successful
  • Customer-visible features documented
  • No linter warnings (make lint)

If CRDs are changed:

  • CRD YAMLs updated (make manifests) and also copied into the helm chart
  • Changes to CRDs documented

Please refer to the PR guidelines before submitting this pull request.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Copy link
Contributor

@rootxrishabh rootxrishabh left a comment

Choose a reason for hiding this comment

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

LGTM 🚀
cc: @prudhvigodithi

@Fluder-Paradyne Fluder-Paradyne force-pushed the honor-serviceName-in-ingress branch from 8965d83 to 2263710 Compare August 11, 2025 05:17
@synhershko
Copy link

LGTM!

@prudhvigodithi prudhvigodithi merged commit f9fca7a into opensearch-project:main Sep 8, 2025
11 checks passed
@github-project-automation github-project-automation bot moved this from 👀 In Review to ✅ Done in Engineering Effectiveness Board Sep 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

4 participants