SECURESIGN-1221 | SBJ Not reaching segment endpoint #108
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
JasonPowr
force-pushed
the
handle-both-internal-and-external-comms
branch
3 times, most recently
from
9f3fde3 to
c4a56f6
Compare
JasonPowr
force-pushed
the
handle-both-internal-and-external-comms
branch
from
c4a56f6 to
cb1bf4c
Compare
JasonPowr
force-pushed
the
handle-both-internal-and-external-comms
branch
from
cb1bf4c to
8eb6b77
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.
This pr makes sure that SBJ has the necessary certs to verify communications inside and outside of the cluster, This is part one of a two part fix for this issue, the second will be opened in the operator.