I am trying flink on k8s high availablily, start using flink application mode, k8s deployment pod-template-file, but when i want to update the jar in pod-template-file, i found i still run the old logic, the initial container download the jar, but it not execute, still use old logic, how to fix this.

I think I understand your problem. Have you updated your flink.conf configuration. Specifically have you updated the pipeline.classpaths? https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#pipeline-classpaths

no, i don't updatedpipeline.classpaths, my problem should not relate this config. i think it relate k8s high availablily feature. Even i download the new jars in initial container (in pod-template-file), flink on k8s with high availabilty still use the old jar( in k8s high availiablity storage), not use new jar.