-
Notifications
You must be signed in to change notification settings - Fork 0
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
Stateful Proposal doc #1
Conversation
tolerationSeconds: 90 | ||
purgeMode: Graciously | ||
gracePeriodSeconds: 10 | ||
persistedFields.maxHistory: 5 |
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.
Check indenting. This should align with gracePeriodSeconds - we should also consider how this mechanism works with taint-based eviction.
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.
Hmm not sure why it shows up differently here but will check:
I am planning on adding at the application level so that it can be used for both cluster and application failure
apiVersion: policy.karmada.io/v1alpha1
kind: PropagationPolicy
metadata:
name: flinkdep-policy
spec:
failover:
application:
decisionConditions:
tolerationSeconds: 90
purgeMode: Graciously
gracePeriodSeconds: 10
persistedFields.maxHistory: 5
persistedFields.fields:
- LabelName: jobID
PersistedStatusItem: obj.status.jobStatus.jobID
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.
sounds good, thanks
What type of PR is this?
Proposal for stateful failover
What this PR does / why we need it:
Explained in the doc
Which issue(s) this PR fixes:
Fixes karmada-io#5006, karmada-io#4969
Special notes for your reviewer:
N/A
Does this PR introduce a user-facing change?:
NONE