Extend the Probe interface to support optional path, port and scheme properties #566
Conversation
This file contains hidden or 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
kabicin
force-pushed
the
probe-defaults
branch
from
b7a098e to
30c28af
Compare
…e-component-operator into probe-defaults
and fix manageTLS to true by default when setting scheme to HTTPS
…e-component-operator into probe-defaults
kabicin
changed the title
kabicin
changed the title
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.
BaseComponentProbesinterface so extending operators can override default settings for probes.BaseComponentProbewrapper tocorev1.ProbeOptionalHTTPGetActionswrapper toHTTPGetActionsto setpath,portandschemeas optional.Related issue OpenLiberty/open-liberty-operator#442