The error only happens in cases when a podTemplate is not defined. The
checkpointing/HA examples run well.
Adding a simple (dummy) podtemplate to the basic.yaml makes it work:
podTemplate:
spec:
containers:
- name: flink-main-container
I suspect it could be related to some recent changes on the pod template
handling. This is definitely a blocker for now, I will work on this today.
Thank you!
Gyula
On Fri, May 12, 2023 at 8:57 AM Gyula Fóra <gyula.f...@gmail.com> wrote:
> Very strange, I also get an error when running the examples from the RC.
> It's different but could be related:
>
> Caused by: io.fabric8.kubernetes.client.KubernetesClientException: Failure
> executing: POST at: https://10.96.0.1/api/v1/namespaces/default/pods.
> Message: PodList in version "v1" cannot be handled as a Pod: converting
> (v1.PodList) to (core.Pod): unknown conversion. Received status:
> Status(apiVersion=v1, code=400, details=null, kind=Status, message=PodList
> in version "v1" cannot be handled as a Pod: converting (v1.PodList) to
> (core.Pod): unknown conversion, metadata=ListMeta(_continue=null,
> remainingItemCount=null, resourceVersion=null, selfLink=null,
> additionalProperties={}), reason=BadRequest, status=Failure,
> additionalProperties={}).
> at
> io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:684)
> ~[flink-dist-1.16.1.jar:1.16.1]
> at
> io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:664)
> ~[flink-dist-1.16.1.jar:1.16.1]
> at
> io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:615)
> ~[flink-dist-1.16.1.jar:1.16.1]
> at
> io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:558)
> ~[flink-dist-1.16.1.jar:1.16.1]
> at
> io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:521)
> ~[flink-dist-1.16.1.jar:1.16.1]
> at
> io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleCreate(OperationSupport.java:308)
> ~[flink-dist-1.16.1.jar:1.16.1]
> at
> io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleCreate(BaseOperation.java:644)
> ~[flink-dist-1.16.1.jar:1.16.1]
> at
> io.fabric8.kubernetes.client.dsl.base.BaseOperation.handleCreate(BaseOperation.java:83)
> ~[flink-dist-1.16.1.jar:1.16.1]
> at
> io.fabric8.kubernetes.client.dsl.base.CreateOnlyResourceOperation.create(CreateOnlyResourceOperation.java:61)
> ~[flink-dist-1.16.1.jar:1.16.1]
> at
> org.apache.flink.kubernetes.kubeclient.Fabric8FlinkKubeClient.lambda$createTaskManagerPod$1(Fabric8FlinkKubeClient.java:163)
> ~[flink-dist-1.16.1.jar:1.16.1]
> ... 4 more
>
> I haven't seen this so far. Will investigate today.
>
> Gyula
>
>
>
> On Fri, May 12, 2023 at 8:53 AM Márton Balassi <balassi.mar...@gmail.com>
> wrote:
>
>> Hi Jim and Ted,
>>
>> Thanks for the quick response. For Openshift issue I would assume that
>> adding the RBAC suggested here [1] would solve the problem, it seems fine
>> to me.
>>
>> For the missing taskmanager could you please share the relevant logs from
>> your jobmanager pod that is already show running? Thanks!
>>
>> [1]
>>
>> https://github.com/FairwindsOps/rbac-manager/issues/180#issuecomment-752706810
>>
>> On Fri, May 12, 2023 at 8:40 AM Hao t Chang <htch...@us.ibm.com> wrote:
>>
>> > Seems missing taskmanager pod. I tried the following:
>> > kubectl create -f
>> >
>> https://github.com/jetstack/cert-manager/releases/download/v1.8.2/cert-manager.yaml
>> > helm install 1.5rc1
>> >
>> https://dist.apache.org/repos/dist/dev/flink/flink-kubernetes-operator-1.5.0-rc1/flink-kubernetes-operator-1.5.0-helm.tgz
>> > kubectl create -f
>> >
>> https://raw.githubusercontent.com/apache/flink-kubernetes-operator/release-1.5/examples/basic.yaml
>> > kubectl get po
>> > NAME READY STATUS RESTARTS
>> > AGE
>> > basic-example-67bbc79dd9-blfn4 1/1 Running 0
>> > 2m28s
>> > flink-kubernetes-operator-7bd6dcdfd4-2rshp 2/2 Running 0
>> > 4m49s
>> >
>>
>
