FlinkApplication CRD Update not being applied
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 581
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
Hi there,
I have an application that after updating the CRD get's into state:
```
NAME PHASE CLUSTER HEALTH JOB HEALTH JOB RESTARTS AGE
validation-app-cisco-validation-event SubmittingJob Red 23h
validation-app-cisco-validation-process SubmittingJob Red 23h
```
and never terminates any Pod and restart with the new Spec. In [here](https://github.com/lyft/flinkk8soperator/issues/154#issuecomment-574858672) states that the phase must be `Running` or `Deployed Failed` in order to allow the Flink Operator to redeploy. Is that the case?
If so I'd like to add that our application get's into that state only after the CRD get's updated. Seems to me it tries to _checkpointing_ before terminate any Pods. Does this make sense to you?
Thank you in advance
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing an update to the FlinkApplication CRD and observe the reported SubmittingJob phase, checkpointing behavior, and pod lifecycle. Compare the updated specification with the operator's redeployment conditions; done means the new spec is applied and the old pods are terminated and restarted, with the resulting phase documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100