t;>>>>>>>> metadata:
>>>>>>>>>>> name: flink-jobmanager
>>>>>>>>>>> spec:
>>>>>>>>>>> replicas: 1
>>>>>>>>>>> selector:
>>>>&g
> server: "my-nfs-server.my-org"
>>>>>>>>> path: "/my-shared-nfs-dir/flink/checkpoints"
>>>>>>>>> - name: flink-recovery
>>>>>>>>> nfs:
>>>>>>>>>
er"
>>>>>>> volumeMounts:
>>>>>>> - name: flink-config
>>>>>>> mountPath: /opt/flink/conf/flink-conf.yaml
>>>>>>> subPath: flink-conf.yaml
>>>>>>> # NF
i.apache.org/projects/flink/flink-docs-stable/deployment/resource-providers/standalone/kubernetes.html
>>>>> with some per-company configuration obviously, but still under the
>>>>> scope of this document..
>>>>>
>>>>> on a normal beaut
figmaps/flink-cluster-restserver-leader.
>>> Message: Forbidden!Configured service account doesn't have access. Service
>>> account may have been revoked. configmaps "flink-cluster-restserver-leader"
>>> is forbidden: User "system:serviceaccount:in
nk should be
>> aware of the namespace it resides in, it damages the modularity of upper
>> layers of configurations, regardless we added it and then got the the
>> following error:
>>
>> 2021-02-14 17:00:57,086 ERROR
>> io.fabric8.kubernetes.client.extended.le
One other thing: It looks like you've set high-availability.storageDir to a
local path file:///opt/flink/recovery. You should use a storage path that
is accessible from all Flink cluster components (e.g. using S3). Only
references are stored in Kubernetes ConfigMaps [1].
Best,
Matthias
[1]
https:
Hi Daniel,
what's the exact configuration you used? Did you use the resource
definitions provided in the Standalone Flink on Kubernetes docs [1]? Did
you do certain things differently in comparison to the documentation?
Best,
Matthias
[1]
https://ci.apache.org/projects/flink/flink-docs-release-1.
