-
Notifications
You must be signed in to change notification settings - Fork 44
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
fix: readiness probe on historical #98
fix: readiness probe on historical #98
Conversation
ef25a9d
to
5e33880
Compare
5e33880
to
aabe1b5
Compare
aabe1b5
to
02231f5
Compare
pr has been modified please take another look
apis/druid/v1alpha1/druid_types.go
Outdated
// DefaultProbes If set to true this will add default probes (liveness / readiness / startup) for all druid components | ||
// but it won't override existing probes | ||
// +optional | ||
// +kubebuilder:default:=false |
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.
I think it should be the default unless people want to disable it. Because it should work best "out of the box"
controllers/druid/handler.go
Outdated
@@ -1143,7 +1143,7 @@ func setLivenessProbe(nodeSpec *v1alpha1.DruidNodeSpec, m *v1alpha1.Druid) *v1.P | |||
livenessProbe := updateDefaultPortInProbe( | |||
firstNonNilValue(nodeSpec.LivenessProbe, m.Spec.LivenessProbe).(*v1.Probe), | |||
nodeSpec.DruidPort) | |||
if livenessProbe == nil { | |||
if livenessProbe == nil && m.Spec.DefaultProbes == true { |
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.
you don't need the "== true"
also on the below ones
Signed-off-by: Cyril Corbon <corboncyril@gmail.com>
02231f5
to
cc1018c
Compare
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.
Did you use the make api-docs
command for the API generation? If so great. If not, you should use it to generate the API specification.
Approved anyway :)
yes I used |
Fixes #97
Description
/druid/historical/v1/readiness
Both path has similar purpose. https://druid.apache.org/docs/latest/operations/api-reference/#historical
This PR has:
Key changed/added files in this PR
controllers/druid/handler.go
docs/features.md
chart/templates/crds/druid.apache.org_druids.yaml
config/crd/bases/druid.apache.org_druids.yaml