Change hashringConfigmapName to hashringConfigMapName #279
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
michael-burt
force-pushed
the
configmap-typo
branch
from
bbbcb53 to
e5f9365
Compare
squat
reviewed
Jul 15, 2022
squat
reviewed
Jul 15, 2022
michael-burt
force-pushed
the
configmap-typo
branch
3 times, most recently
from
ebab730 to
7cbe3fe
Compare
Signed-off-by: Michael Burt <michaelpburt@gmail.com>
michael-burt
force-pushed
the
configmap-typo
branch
from
081892d to
f4ac50e
Compare
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.
Changes
This PR changes
hashringConfigmapNametohashringConfigMapNameto makes things consistent. This fixes an issue where the configmap name was not properly populated on the receive router pod.Verification
I tested this in a development cluster.