1) -Dkubernetes.namespace
2) The -D syntax is actually just a way to specify configurations
options from the command-line. As such, the configuration page
<https://ci.apache.org/projects/flink/flink-docs-release-1.11/ops/config.html#kubernetes>
lists all options.
3) if the diff between the configurations isn't too big you could maybe
have a shared base config, and specify the special options on the
command-line (see 2)). But if you truly need a separate file, then I
don't think there is another way than the one you described.
4) yes, the configuration is stored as a config map.
On 11/3/2020 12:17 AM, Boris Lublinsky wrote:
Hi,
I was trying to follow instructions
https://ci.apache.org/projects/flink/flink-docs-stable/ops/deployment/native_kubernetes.html but
non e of them really worked.
For session I tried:
/Users/boris/Support/flink-1.11.2/bin/flink run-application -t
kubernetes-application \
-Dkubernetes.cluster-id=flink-native-k8s-application \
-Dtaskmanager.memory.process.size=4096m \
-Dkubernetes.taskmanager.cpu=2 \
-Dtaskmanager.numberOfTaskSlots=4 \
-Dkubernetes.container.image=flink:1.11.2-scala_2.12 \
local:///opt/flink/examples/batch/WordCount.jar
And for application
/Users/boris/Support/flink-1.11.2//bin/kubernetes-session.sh \
-Dkubernetes.cluster-id=flink-native-k8s-session \
-Dtaskmanager.memory.process.size=4096m \
-Dkubernetes.taskmanager.cpu=2 \
-Dtaskmanager.numberOfTaskSlots=4 \
-Dresourcemanager.taskmanager-timeout=3600000
Both were trying to create JM deployment, but in both cases the actual
container creation failed with no explanation
Thats the only log that I can see:
kubectl logs flink-native-k8s-application-5d686d5457-lnttw
Start command : /bin/bash -c $JAVA_HOME/bin/java -classpath
$FLINK_CLASSPATH -Xmx1073741824 -Xms1073741824
-XX:MaxMetaspaceSize=268435456
-Dlog.file=/opt/flink/log/jobmanager.log
-Dlogback.configurationFile=file:/opt/flink/conf/logback.xml
-Dlog4j.configurationFile=file:/opt/flink/conf/log4j.properties
org.apache.flink.kubernetes.entrypoint.KubernetesApplicationClusterEntrypoint
1> /opt/flink/log/jobmanager.out 2> /opt/flink/log/jobmanager.err
A couple of additional questions:
1. Is there a way to specify namespace where the deployment is created?
2. Is there a list of -D parameters that can be specified?
3. If I want a custom Flink-conf.yaml, for every invocation, do I have
to create it in separate location and then use something
like FLINK_CONF_DIR=/Users/boris/Support/flink-1.11.2/conf for every
run? Or there is a simpler way?
4. If I understand correctly, this creates a config-map that is
actually used.
