[
https://issues.apache.org/jira/browse/FLINK-22158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320762#comment-17320762
]
Yang Wang commented on FLINK-22158:
-----------------------------------
[~rmetzger] Thanks for testing this pod template feature. Currently, we allow
users to specify the pod template *without* "flink-main-container". For
example, they just want to set the sidecar container. So I am afraid we could
not do such a check and fail if it is not set.
Actually, I think this error message from K8s APIServer and is clear enough.
The required value "image" is not specified.
Moreover, I believe you could also find a log that states the main container is
not specified.
{code:java}
Could not find main container {} in pod template, using empty one to initialize.
{code}
> Test native Kubernetes pod template
> -----------------------------------
>
> Key: FLINK-22158
> URL: https://issues.apache.org/jira/browse/FLINK-22158
> Project: Flink
> Issue Type: Test
> Components: Deployment / Kubernetes
> Affects Versions: 1.13.0
> Reporter: Yang Wang
> Assignee: Robert Metzger
> Priority: Blocker
> Labels: release-testing
> Fix For: 1.13.0
>
>
> Flink allows users to define the JobManager and TaskManager pods via template
> files. This allows to support advanced features(e.g. init-container, sidecar
> container, volume mount, etc.) that are not supported by Flink Kubernetes
> config options directly. Use {{kubernetes.pod-template-file}} to specify a
> local file that contains the pod definition. It will be used to initialize
> the JobManager and TaskManager.
>
> The documentation about how to start a session/application cluster with pod
> template could be found here[1].
>
> [1].
> https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/resource-providers/native_kubernetes/#pod-template
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
