feat: Rename service name for event streams in k8s #672
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hsong-rh
force-pushed
the
k8s_service_name
branch
from
93d2776 to
7d0d3c4
Compare
mkanoor
reviewed
Feb 13, 2024
mkanoor
approved these changes
Feb 13, 2024
hsong-rh
force-pushed
the
k8s_service_name
branch
from
7d0d3c4 to
30e675d
Compare
bzwei
approved these changes
Feb 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://issues.redhat.com/browse/AAP-20691
In K8S the resource prefixes are added to secret, service, job, and pod names to avoid conflicting resources for event streams and activations. They looks like: