-
Notifications
You must be signed in to change notification settings - Fork 67
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
[Doc] update examples/starrocks/deploy_a_starrocks_cluster_with_all_f… #278
[Doc] update examples/starrocks/deploy_a_starrocks_cluster_with_all_f… #278
Conversation
c73681d
to
d2142a8
Compare
…eatures.yaml Signed-off-by: yandongxiao <[email protected]>
d2142a8
to
09b9c66
Compare
Signed-off-by: yandongxiao <[email protected]>
e702f26
to
f60f5af
Compare
# Default failureThreshold is 60 and the periodSeconds is 5, this means the startup | ||
# will fail if the pod can't start in 300 seconds. Your StartupProbeFailureSeconds is | ||
# the total time of seconds before startupProbe give up and fail the container start. | ||
# If startupProbeFailureSeconds can't be divided by defaultPeriodSeconds, the failureThreshold |
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.
replace tab with spaces?
@@ -67,10 +67,6 @@ type StarRocksLoadSpec struct { | |||
// +optional | |||
Tolerations []corev1.Toleration `json:"tolerations,omitempty"` | |||
|
|||
// Probe defines the mode probe service in container is alive. |
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.
is this forgot to remove in last startuptime period PR?
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.
yes
…s.yaml Signed-off-by: yandongxiao <[email protected]>
…eatures.yaml