"kubectl -n flink-operator apply -f" does not work as expect

hi! i have a yaml like this

`apiVersion: flink.k8s.io/v1beta1
kind: FlinkApplication
metadata:
name: hotitems-dev
namespace: flink-operator
annotations:
labels:
environment: development
spec:
image: ***/hotitems:dev
imagePullPolicy: Always
imagePullSecrets:
- name: regcred
flinkConfig:
taskmanager.heap.size: "4096m"
state.backend.fs.checkpointdir: hdfs://***/checkpoints-backend
state.checkpoints.dir: hdfs://***/checkpoints
state.savepoints.dir: hdfs://***/savepoints
taskmanager.network.memory.min: "64mb"
taskmanager.network.memory.max: "1gb"
taskmanager.network.memory.fraction: 0.125
jobManagerConfig:
resources:
requests:
memory: "1Gi"
cpu: "4"
replicas: 1
nodeSelector:
attr: logic
taskManagerConfig:
taskSlots: 12
resources:
requests:
memory: "12Gi"
cpu: "4"
nodeSelector:
attr: logic
flinkVersion: "1.9.1"
jarName: "HotItems-1.0-SNAPSHOT.jar"
parallelism: 1
savepointPath: hdfs://***/savepoints
entryClass: "***.HotItems"
deleteMode: Savepoint`,

and when i execute the cmd like this "kubectl -n flink-operator apply -f ", it print "flinkapplication.flink.k8s.io/hotitems-dev configured" ,but the operator does not submits a new , what's happen?

thanks!

Start by examining the FlinkApplication status and Kubernetes events after running the reported apply command, then check the operator logs for its reconciliation of hotitems-dev. Determine why the resource is reported as configured without submitting a new application, and document or correct the behavior.

Written by the indexing model from the issue text.