Closed jaredstehler closed 3 years ago
Same here, @elanv @functicons any idea why did is happening?
status.job.id
has been changed to optional from required. Perhaps it will be solved by updating the CRD. It would be nice to check if the field has changed in the CRD.
But this isn't a user-specified field, so this would be a bug in the operator?
The CRD diffs actually show these two fields switching from required to optional?
type JobStatus struct {
// The name of the Kubernetes job resource.
- Name string `json:"name"`
+ Name string `json:"name,omitempty"`
// The ID of the Flink job.
- ID string `json:"id"`
+ ID string `json:"id,omitempty"`
On Wed, Dec 16, 2020 at 7:17 PM Eui Heo notifications@github.com wrote:
status.job.id has been changed to optional from required. Perhaps it will be solved by updating the CRD. It would be nice to check if the field has changed in the CRD.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/GoogleCloudPlatform/flink-on-k8s-operator/issues/385#issuecomment-747118505, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPNWSQPFBTDGWTZUD7TUPDSVFE3LANCNFSM4U6UEN2A .
You can find if the CRD is updated like:
$ kubectl get crd flinkclusters.flinkoperator.k8s.io -o jsonpath='{.spec.versions[?(@.name=="v1beta1")].schema.openAPIV3Schema.properties.status.properties.components.properties.job}'
{"properties":{"fromSavepoint":{"type":"string"},"id":{"type":"string"},"lastSavepointTime":{"type":"string"},"lastSavepointTriggerID":{"type":"string"},"name":{"type":"string"},"restartCount":{"format":"int32","type":"integer"},"savepointGeneration":{"format":"int32","type":"integer"},"savepointLocation":{"type":"string"},"state":{"type":"string"}},"required":["state"],"type":"object"}
If updated, required should look:
"required":["state"]
If the CRD was not updated yet, you could update your CRD like:
make install
Found the problem I think, you forgot to update the crd in the helm chart
Can you take a look there and update the crd please? @elanv
Found the problem I think, you forgot to update the crd in the helm chart Can you take a look there and update the crd please? @elanv
@shashken I missed it. Thanks. I made the PR #386.
Seeing jobs fail to start from the operator, with following in operator logs (below). Seems related to PR #379