[
https://issues.apache.org/jira/browse/FLINK-28829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-28829:
-----------------------------------
Labels: pull-request-available stale-assigned (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> [2] Need the ability of preparing K8S resource before JobManager creation
> -------------------------------------------------------------------------
>
> Key: FLINK-28829
> URL: https://issues.apache.org/jira/browse/FLINK-28829
> Project: Flink
> Issue Type: Sub-task
> Components: Deployment / Kubernetes
> Reporter: bo zhao
> Assignee: bo zhao
> Priority: Major
> Labels: pull-request-available, stale-assigned
>
> For applying the customized schedulers functionality or making Flink K8S more
> flexible, we need to make Flink to provide an ability to prepare the K8S
> resource before we actually set up the Flink components.
> In current Flink K8S design, it provides buildAccompanyingKubernetesResources
> interface to add the resources from decorators, the mentioned
> AccompanyingKubernetesResources will be created after the JobManager
> Deployment creation. But some K8S Pod-related customized schedulers might
> need an extension K8S resource to control the real scheduling before the
> target Pods setup. On the other hand, we only make an example about the
> customized scheduler which only worked before the Pod creation, we can not
> imagine all customized schedulers works like that, so we can make the
> existing JobManager deployment create processing more common.
>
> New interface should be provided, and the decorators can create the K8S
> resource for associate them with the following Flink Pods, then using
> buildAccompanyingKubernetesResources to refresh the owner reference for
> keeping the same behavior like other AccompanyingKubernetesResources.
> public interface KubernetesStepDecorator {
> FlinkPod decorateFlinkPod(FlinkPod flinkPod);
> List<HasMetadata> buildAccompanyingKubernetesResources() throws
> IOException;
> List<HasMetadata> [Pre K8S resource creation Interface]();
> }
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
