Re: Native Kubernetes annotation parsing problem
Posted by
Yang Wang on
URL: http://deprecated-apache-flink-user-mailing-list-archive.369.s1.nabble.com/Native-Kubernetes-annotation-parsing-problem-tp41345p41374.html
> is there a way I can load my own ConfigMap and specify it via the dynamic argument?
Flink client will automatically ship the "flink-conf.yaml" and "log4j-console.properties" under FLINK_HOME/conf directory on the client side.
After the application is submitted successfully, you could find a ConfigMap named "flink-config-<cluster-id>".
If you want to mount your own ConfigMaps, it could not be supported now. We will get it done via pod template[1]. It is still in progress and
have a PR[2] waiting for review.
Best,
Yang
thank you Yang
but is there a way I can load my own ConfigMap and specify it via the dynamic argument?
I'd want to encapsulate all the my custom config (flink-conf.yaml, log4j-consle.yaml etc) and feed it into native K8S CLI
If you are setting the config options in flink-conf.yaml, then you could directly add the following example.
However, if you are using the dynamic properties in the CLI. Then the configuration value should also
be wrapped with a double quote. It just because we need to escape the value with single quote.
It seems that IAM is not a common feature in Kubernetes. But from the documentation of AWS[1],
I think it could be specified via service account[2]. Hope this helps.
Best,
Yang
I think it will be more generic question of how I inject IAM roles in Native Kubernetes pods
I'm using Kubeiam and seems the namespace annotation doesn't work
Hi team, I'm using Native Kubernetes annotation config
kubernetes.jobmanager.annotations
and I'm facing some problem with parsing.
I use annotation
but seems no matter what I do, the colon is getting parsed for key, value. can anyone help?