I have been working with the 1.17 version of the Apache Flink operator and have below questions.
As part of upgrading the application, is the application suspended, i.e. it is checkpointed, prior to doing an upgrade? Is there a concept of a hot update where I can update the application while it is running to avoid any downtime? I understand that the Flink operator has a new feature recently introduced called Autoscalar which allows the scaling of applications based on defined metrics. If a job is running as part of a Flink cluster and now more work nodes are introduced in the Kubernetes cluster, does the Flink operator automatically take advantage of the new resources or is any manual step required? How does the Autoscalar feature work if more instances of the Flink operator are added. Thanks in advance. --Vince
