nielsbasjes commented on a change in pull request #11245:
URL: https://github.com/apache/flink/pull/11245#discussion_r444033798



##########
File path: 
flink-kubernetes/src/main/java/org/apache/flink/kubernetes/configuration/KubernetesConfigOptions.java
##########
@@ -137,11 +138,17 @@
                .withDescription("The cluster-id, which should be no more than 
45 characters, is used for identifying " +
                        "a unique Flink cluster. If not set, the client will 
automatically generate it with a random ID.");
 
+       // The default container image that ties to the exact needed versions 
of both Flink and Scala.
+       public static final String DEFAULT_CONTAINER_IMAGE = "flink:" + 
EnvironmentInformation.getVersion() + "-scala_" + 
EnvironmentInformation.getScalaVersion();
+
        public static final ConfigOption<String> CONTAINER_IMAGE =
                key("kubernetes.container.image")
                .stringType()
-               .defaultValue("flink:latest")
-               .withDescription("Image to use for Flink containers.");
+               .defaultValue(DEFAULT_CONTAINER_IMAGE)
+               .withDescription("Image to use for Flink containers. " +
+                       "The specified image MUST be based upon Apache Flink " +
+                       EnvironmentInformation.getVersion() + " that uses Scala 
" + EnvironmentInformation.getScalaVersion() + " . " +

Review comment:
       @azagrebin I changed it to the "defaultValueForDocumentation" construct 
as I mentioned and now it all looks so much cleaner and easier to use.
   The documentation now shows a stable flink and scala version without 
"SNAPSHOT" and the actual default contains the exact value as is needed by the 
version at hand.
   
   I also did a rebase onto the latest master.




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to