-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 Allow using different resource group and listener name with the in memory server #10096
🌱 Allow using different resource group and listener name with the in memory server #10096
Conversation
test/infrastructure/inmemory/api/v1alpha1/inmemorycluster_types.go
Outdated
Show resolved
Hide resolved
test/infrastructure/inmemory/internal/controllers/inmemorymachine_controller.go
Outdated
Show resolved
Hide resolved
/approve /assign @chrischdi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Jut two nits :-)
test/infrastructure/inmemory/api/v1alpha1/inmemorycluster_types.go
Outdated
Show resolved
Hide resolved
8a0f512
to
c05240e
Compare
Thx! /lgtm |
LGTM label has been added. Git tree hash: b57d6c6bcd1dd4ae76fb6e5fb5b7f9cd500ba177
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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 |
What this PR does / why we need it:
With this PR it is now possible to use different resource group and listener name with the in-memory server.
This will greatly simplify using the in-memory server in context where the control plane endpoint and the in-memory resources are managed separately or where the name of the cluster is not known in advance, e.g. E2E tests
Note: for convenience we will continue to use the same name for resource group and listener within the in-memory, but this is not required anymore for other consumers of the in-memory server
/area provider/infrastructure-in-memory