[jira] [Commented] (FLINK-25480) Create dashboard/monitoring to see resource usage per E2E test

[ https://issues.apache.org/jira/browse/FLINK-25480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17510448#comment-17510448 ] Aitozi commented on FLINK-25480: FYI, I encounter the same problem with 1.14.4

[jira] [Commented] (FLINK-26795) Fix the CI not fail fast after build failed

[ https://issues.apache.org/jira/browse/FLINK-26795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17510273#comment-17510273 ] Aitozi commented on FLINK-26795: [https://github.com/Aitozi/flink-kubernetes-oper

[jira] [Updated] (FLINK-26795) Fix the CI not fail fast after build failed

[ https://issues.apache.org/jira/browse/FLINK-26795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-26795: --- Attachment: image-2022-03-22-15-18-22-234.png > Fix the CI not fail fast after build fai

[jira] [Created] (FLINK-26795) Fix the CI not fail fast after build failed

Aitozi created FLINK-26795: -- Summary: Fix the CI not fail fast after build failed Key: FLINK-26795 URL: https://issues.apache.org/jira/browse/FLINK-26795 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-26787) Implement FlinkSessionJobController and Reconciler

Aitozi created FLINK-26787: -- Summary: Implement FlinkSessionJobController and Reconciler Key: FLINK-26787 URL: https://issues.apache.org/jira/browse/FLINK-26787 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-26785) Add FlinkSessionJob CRD

Aitozi created FLINK-26785: -- Summary: Add FlinkSessionJob CRD Key: FLINK-26785 URL: https://issues.apache.org/jira/browse/FLINK-26785 Project: Flink Issue Type: Sub-task Components

[jira] [Created] (FLINK-26784) FLIP-215: Introduce FlinkSessionJob CRD in the kubernetes operator

Aitozi created FLINK-26784: -- Summary: FLIP-215: Introduce FlinkSessionJob CRD in the kubernetes operator Key: FLINK-26784 URL: https://issues.apache.org/jira/browse/FLINK-26784 Project: Flink

[jira] [Updated] (FLINK-26776) The LocalBufferPoolDestroyTest#isInBlockingBufferRequest is fragile in different JDK environment

[ https://issues.apache.org/jira/browse/FLINK-26776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-26776: --- Affects Version/s: 1.14.4 (was: 1.15.0) > The LocalBufferPoolDestroyT

[jira] [Closed] (FLINK-26776) The LocalBufferPoolDestroyTest#isInBlockingBufferRequest is fragile in different JDK environment

[ https://issues.apache.org/jira/browse/FLINK-26776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi closed FLINK-26776. -- Resolution: Duplicate > The LocalBufferPoolDestroyTest#isInBlockingBufferRequest is fragile in > dif

[jira] [Commented] (FLINK-26776) The LocalBufferPoolDestroyTest#isInBlockingBufferRequest is fragile in different JDK environment

[ https://issues.apache.org/jira/browse/FLINK-26776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509806#comment-17509806 ] Aitozi commented on FLINK-26776: Then I found it has been solved by h

[jira] [Commented] (FLINK-26776) The LocalBufferPoolDestroyTest#isInBlockingBufferRequest is fragile in different JDK environment

[ https://issues.apache.org/jira/browse/FLINK-26776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509796#comment-17509796 ] Aitozi commented on FLINK-26776: An example that can not pass. !image-2022-03-21-1

[jira] [Commented] (FLINK-26776) The LocalBufferPoolDestroyTest#isInBlockingBufferRequest is fragile in different JDK environment

[ https://issues.apache.org/jira/browse/FLINK-26776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509797#comment-17509797 ] Aitozi commented on FLINK-26776: I will try to make a solution for it. &

[jira] [Updated] (FLINK-26776) The LocalBufferPoolDestroyTest#isInBlockingBufferRequest is fragile in different JDK environment

[ https://issues.apache.org/jira/browse/FLINK-26776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-26776: --- Attachment: image-2022-03-21-19-53-44-689.png > The LocalBufferPoolDestroyTest#isInBlockingBufferRequest

[jira] [Created] (FLINK-26776) The LocalBufferPoolDestroyTest#isInBlockingBufferRequest is fragile in different JDK environment

Aitozi created FLINK-26776: -- Summary: The LocalBufferPoolDestroyTest#isInBlockingBufferRequest is fragile in different JDK environment Key: FLINK-26776 URL: https://issues.apache.org/jira/browse/FLINK-26776

[jira] [Commented] (FLINK-26754) KafkaCommitterTest#testRetryCommittableOnRetriableError stuck

[ https://issues.apache.org/jira/browse/FLINK-26754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509606#comment-17509606 ] Aitozi commented on FLINK-26754: After checking the master branch, I found it has

[jira] [Closed] (FLINK-26754) KafkaCommitterTest#testRetryCommittableOnRetriableError stuck

[ https://issues.apache.org/jira/browse/FLINK-26754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi closed FLINK-26754. -- Resolution: Duplicate > KafkaCommitterTest#testRetryCommittableOnRetriableError st

[jira] (FLINK-26448) Disable tests in KafkaSourceLegacyITCase for test stability issues

[ https://issues.apache.org/jira/browse/FLINK-26448 ] Aitozi deleted comment on FLINK-26448: was (Author: aitozi): Hi [~jingge] ,  what's the problem with the kafka test env with 1 broker? Does the https://issues.apache.org/jira/browse/FLINK-

[jira] [Commented] (FLINK-26754) KafkaCommitterTest#testRetryCommittableOnRetriableError stuck

[ https://issues.apache.org/jira/browse/FLINK-26754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509592#comment-17509592 ] Aitozi commented on FLINK-26754: After looking into this, it's caused by

[jira] [Commented] (FLINK-26448) Disable tests in KafkaSourceLegacyITCase for test stability issues

[ https://issues.apache.org/jira/browse/FLINK-26448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509575#comment-17509575 ] Aitozi commented on FLINK-26448: Hi [~jingge] ,  what's the problem with the k

[jira] [Commented] (FLINK-26754) KafkaCommitterTest#testRetryCommittableOnRetriableError stuck

[ https://issues.apache.org/jira/browse/FLINK-26754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509570#comment-17509570 ] Aitozi commented on FLINK-26754: It seems have sth to do with

[jira] [Created] (FLINK-26754) KafkaCommitterTest#testRetryCommittableOnRetriableError stuck

Aitozi created FLINK-26754: -- Summary: KafkaCommitterTest#testRetryCommittableOnRetriableError stuck Key: FLINK-26754 URL: https://issues.apache.org/jira/browse/FLINK-26754 Project: Flink Issue

[jira] [Commented] (FLINK-26737) Add CRD management in development doc

[ https://issues.apache.org/jira/browse/FLINK-26737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509237#comment-17509237 ] Aitozi commented on FLINK-26737: I will work on it, Please help assign this t

[jira] [Updated] (FLINK-26737) Add CRD management in development doc

[ https://issues.apache.org/jira/browse/FLINK-26737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-26737: --- Description: Add the crd operation in the development doc, such as generate, upgrade and so on. (was: Add

[jira] [Created] (FLINK-26737) Add CRD management in development doc

Aitozi created FLINK-26737: -- Summary: Add CRD management in development doc Key: FLINK-26737 URL: https://issues.apache.org/jira/browse/FLINK-26737 Project: Flink Issue Type: Sub-task

[jira] [Comment Edited] (FLINK-26719) Rethink the default reschedule reconcile loop

[ https://issues.apache.org/jira/browse/FLINK-26719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509231#comment-17509231 ] Aitozi edited comment on FLINK-26719 at 3/19/22, 9:3

[jira] [Closed] (FLINK-26719) Rethink the default reschedule reconcile loop

[ https://issues.apache.org/jira/browse/FLINK-26719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi closed FLINK-26719. -- Resolution: Not A Problem > Rethink the default reschedule reconcile l

[jira] [Comment Edited] (FLINK-26719) Rethink the default reschedule reconcile loop

[ https://issues.apache.org/jira/browse/FLINK-26719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509231#comment-17509231 ] Aitozi edited comment on FLINK-26719 at 3/19/22, 9:3

[jira] [Comment Edited] (FLINK-26719) Rethink the default reschedule reconcile loop

[ https://issues.apache.org/jira/browse/FLINK-26719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509231#comment-17509231 ] Aitozi edited comment on FLINK-26719 at 3/19/22, 9:3

[jira] [Comment Edited] (FLINK-26719) Rethink the default reschedule reconcile loop

[ https://issues.apache.org/jira/browse/FLINK-26719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509231#comment-17509231 ] Aitozi edited comment on FLINK-26719 at 3/19/22, 9:3

[jira] [Commented] (FLINK-26719) Rethink the default reschedule reconcile loop

[ https://issues.apache.org/jira/browse/FLINK-26719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509231#comment-17509231 ] Aitozi commented on FLINK-26719: > If we do not want to provide stronger res

[jira] [Comment Edited] (FLINK-26719) Rethink the default reschedule reconcile loop

[ https://issues.apache.org/jira/browse/FLINK-26719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508658#comment-17508658 ] Aitozi edited comment on FLINK-26719 at 3/18/22, 8:5

[jira] [Commented] (FLINK-26719) Rethink the default reschedule reconcile loop

[ https://issues.apache.org/jira/browse/FLINK-26719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508658#comment-17508658 ] Aitozi commented on FLINK-26719: [~matyas] Thanks for your inputs, It seems we

[jira] [Commented] (FLINK-26719) Rethink the default reschedule reconcile loop

[ https://issues.apache.org/jira/browse/FLINK-26719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508597#comment-17508597 ] Aitozi commented on FLINK-26719: cc [~wangyang0918] [~gyfora]  > Rethink the

[jira] [Created] (FLINK-26719) Rethink the default reschedule reconcile loop

Aitozi created FLINK-26719: -- Summary: Rethink the default reschedule reconcile loop Key: FLINK-26719 URL: https://issues.apache.org/jira/browse/FLINK-26719 Project: Flink Issue Type: Sub-task

[jira] [Commented] (FLINK-26647) Can not add extra config files on native Kubernetes

[ https://issues.apache.org/jira/browse/FLINK-26647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17507026#comment-17507026 ] Aitozi commented on FLINK-26647: I think we may could provide the tool to ship

[jira] [Commented] (FLINK-26647) Can not add extra config files on native Kubernetes

[ https://issues.apache.org/jira/browse/FLINK-26647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17507022#comment-17507022 ] Aitozi commented on FLINK-26647: It looks like the way 2 can meet your requirem

[jira] [Commented] (FLINK-26538) Ability to restart deployment w/o spec change

[ https://issues.apache.org/jira/browse/FLINK-26538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17505983#comment-17505983 ] Aitozi commented on FLINK-26538: [~thw] Are you planning to work on this, If not, M

[jira] [Comment Edited] (FLINK-26528) Trigger the updateControl when the FlinkDeployment have changed

[ https://issues.apache.org/jira/browse/FLINK-26528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503631#comment-17503631 ] Aitozi edited comment on FLINK-26528 at 3/9/22, 3:07 PM: -

[jira] [Commented] (FLINK-26528) Trigger the updateControl when the FlinkDeployment have changed

[ https://issues.apache.org/jira/browse/FLINK-26528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503631#comment-17503631 ] Aitozi commented on FLINK-26528: Yes, my meaning is to eliminate the unchanged up

[jira] [Commented] (FLINK-26546) Extract Observer Interface

[ https://issues.apache.org/jira/browse/FLINK-26546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503535#comment-17503535 ] Aitozi commented on FLINK-26546: Get it. > Extract Observer In

[jira] [Commented] (FLINK-26528) Trigger the updateControl when the FlinkDeployment have changed

[ https://issues.apache.org/jira/browse/FLINK-26528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503534#comment-17503534 ] Aitozi commented on FLINK-26528: Yes, I can take this work, I have done some poc

[jira] [Commented] (FLINK-26546) Extract Observer Interface

[ https://issues.apache.org/jira/browse/FLINK-26546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503438#comment-17503438 ] Aitozi commented on FLINK-26546: +1. I'm willing to take the work > Extr

[jira] [Commented] (FLINK-26538) Ability to restart deployment w/o spec change

[ https://issues.apache.org/jira/browse/FLINK-26538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503428#comment-17503428 ] Aitozi commented on FLINK-26538: For the convenient purpose, I'm +1 for this. 

[jira] [Commented] (FLINK-26528) Trigger the updateControl when the FlinkDeployment have changed

[ https://issues.apache.org/jira/browse/FLINK-26528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503409#comment-17503409 ] Aitozi commented on FLINK-26528: It's not the same question, this ticket i

[jira] [Commented] (FLINK-26538) Ability to restart deployment w/o spec change

[ https://issues.apache.org/jira/browse/FLINK-26538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503228#comment-17503228 ] Aitozi commented on FLINK-26538: Can this achieved by setting JobState to {{SUSPE

[jira] [Commented] (FLINK-26528) Trigger the updateControl when the FlinkDeployment have changed

[ https://issues.apache.org/jira/browse/FLINK-26528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503027#comment-17503027 ] Aitozi commented on FLINK-26528: I proposal to provide a {{ReconcileResult}} which

[jira] [Updated] (FLINK-26528) Trigger the updateControl when the FlinkDeployment have changed

[ https://issues.apache.org/jira/browse/FLINK-26528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-26528: --- Description: If the CR has not changed since last reconcile, we could create a UpdateControl with

[jira] [Created] (FLINK-26528) Trigger the updateControl when the FlinkDeployment have changed

Aitozi created FLINK-26528: -- Summary: Trigger the updateControl when the FlinkDeployment have changed Key: FLINK-26528 URL: https://issues.apache.org/jira/browse/FLINK-26528 Project: Flink Issue

[jira] [Commented] (FLINK-26493) Use state machine based mechanism to simply the reconciler

[ https://issues.apache.org/jira/browse/FLINK-26493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501409#comment-17501409 ] Aitozi commented on FLINK-26493: Agree, I will try to capture the current s

[jira] [Commented] (FLINK-26493) Use state machine based mechanism to simply the reconciler

[ https://issues.apache.org/jira/browse/FLINK-26493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501381#comment-17501381 ] Aitozi commented on FLINK-26493: I will try to define a initial state machine tran

[jira] [Comment Edited] (FLINK-26493) Use state machine based mechanism to simply the reconciler

[ https://issues.apache.org/jira/browse/FLINK-26493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501379#comment-17501379 ] Aitozi edited comment on FLINK-26493 at 3/4/22, 3:22 PM: -

[jira] [Commented] (FLINK-26493) Use state machine based mechanism to simply the reconciler

[ https://issues.apache.org/jira/browse/FLINK-26493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501379#comment-17501379 ] Aitozi commented on FLINK-26493: Do you have some inputs for this [~gy

[jira] [Created] (FLINK-26493) Use state machine based mechanism to simply the reconciler

Aitozi created FLINK-26493: -- Summary: Use state machine based mechanism to simply the reconciler Key: FLINK-26493 URL: https://issues.apache.org/jira/browse/FLINK-26493 Project: Flink Issue Type

[jira] [Commented] (FLINK-26377) Extract Reconciler interface

[ https://issues.apache.org/jira/browse/FLINK-26377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501360#comment-17501360 ] Aitozi commented on FLINK-26377: [~gyfora] I have finished it, and just submit the

[jira] [Commented] (FLINK-26435) Provide the container name for CI debug log

[ https://issues.apache.org/jira/browse/FLINK-26435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500086#comment-17500086 ] Aitozi commented on FLINK-26435: Get it, Done.  > Provide the container name

[jira] [Updated] (FLINK-26435) Provide the container name for CI debug log

[ https://issues.apache.org/jira/browse/FLINK-26435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-26435: --- Parent: (was: FLINK-25963) Issue Type: Bug (was: Sub-task) > Provide the container name for

[jira] [Commented] (FLINK-26435) Provide the container name for CI debug log

[ https://issues.apache.org/jira/browse/FLINK-26435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500052#comment-17500052 ] Aitozi commented on FLINK-26435: Hmm.. It's come from the {{flink-kubernetes

[jira] [Updated] (FLINK-26435) Provide the container name for CI debug log

[ https://issues.apache.org/jira/browse/FLINK-26435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-26435: --- Description: Current kubectl log for the CI have not specified the container name as below   {code:java

[jira] [Created] (FLINK-26435) Provide the container name for CI debug log

Aitozi created FLINK-26435: -- Summary: Provide the container name for CI debug log Key: FLINK-26435 URL: https://issues.apache.org/jira/browse/FLINK-26435 Project: Flink Issue Type: Sub-task

[jira] [Created] (FLINK-26399) Make some option of operator configurable

Aitozi created FLINK-26399: -- Summary: Make some option of operator configurable Key: FLINK-26399 URL: https://issues.apache.org/jira/browse/FLINK-26399 Project: Flink Issue Type: Sub-task

[jira] [Commented] (FLINK-26377) Extract Reconciler interface

[ https://issues.apache.org/jira/browse/FLINK-26377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498687#comment-17498687 ] Aitozi commented on FLINK-26377: ok, i will take a look first before work o

[jira] [Commented] (FLINK-26377) Extract Reconciler interface

[ https://issues.apache.org/jira/browse/FLINK-26377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498408#comment-17498408 ] Aitozi commented on FLINK-26377: Get it ! > Extract Reconciler in

[jira] [Comment Edited] (FLINK-26377) Extract Reconciler interface

[ https://issues.apache.org/jira/browse/FLINK-26377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498393#comment-17498393 ] Aitozi edited comment on FLINK-26377 at 2/26/22, 7:01 AM: -

[jira] [Comment Edited] (FLINK-26377) Extract Reconciler interface

[ https://issues.apache.org/jira/browse/FLINK-26377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498393#comment-17498393 ] Aitozi edited comment on FLINK-26377 at 2/26/22, 7:01 AM: -

[jira] [Comment Edited] (FLINK-26377) Extract Reconciler interface

[ https://issues.apache.org/jira/browse/FLINK-26377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498393#comment-17498393 ] Aitozi edited comment on FLINK-26377 at 2/26/22, 6:35 AM: -

[jira] [Commented] (FLINK-26356) Revisit the create of RestClusterClient

[ https://issues.apache.org/jira/browse/FLINK-26356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498402#comment-17498402 ] Aitozi commented on FLINK-26356: I have some misunderstand before, since the oper

[jira] [Commented] (FLINK-26377) Extract Reconciler interface

[ https://issues.apache.org/jira/browse/FLINK-26377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498393#comment-17498393 ] Aitozi commented on FLINK-26377: I have the same sense to extract common reconc

[jira] [Updated] (FLINK-26356) Revisit the create of RestClusterClient

[ https://issues.apache.org/jira/browse/FLINK-26356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-26356: --- Description: The clusterClient is built as below. The config is mixed up with the FlinkDeploymentSpec and

[jira] [Commented] (FLINK-26356) Revisit the create of RestClusterClient

[ https://issues.apache.org/jira/browse/FLINK-26356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497848#comment-17497848 ] Aitozi commented on FLINK-26356: I have not make it very clear yet, I will do

[jira] [Created] (FLINK-26356) Revisit the create of RestClusterClient

Aitozi created FLINK-26356: -- Summary: Revisit the create of RestClusterClient Key: FLINK-26356 URL: https://issues.apache.org/jira/browse/FLINK-26356 Project: Flink Issue Type: Sub-task

[jira] [Commented] (FLINK-26136) Implement shared validation logic for FlinkDeployment objects

[ https://issues.apache.org/jira/browse/FLINK-26136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497202#comment-17497202 ] Aitozi commented on FLINK-26136: Got it, thanks. > Implement shared validatio

[jira] [Commented] (FLINK-26136) Implement shared validation logic for FlinkDeployment objects

[ https://issues.apache.org/jira/browse/FLINK-26136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497184#comment-17497184 ] Aitozi commented on FLINK-26136: Hi [~gyfora], I have a doubt for this issue. I t

[jira] [Closed] (FLINK-26339) Introduce the webhook config to free the environment options

[ https://issues.apache.org/jira/browse/FLINK-26339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi closed FLINK-26339. -- Resolution: Not A Problem > Introduce the webhook config to free the environment opti

[jira] [Commented] (FLINK-26339) Introduce the webhook config to free the environment options

[ https://issues.apache.org/jira/browse/FLINK-26339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497158#comment-17497158 ] Aitozi commented on FLINK-26339: I mixed it up, there is no need to do this now, s

[jira] [Updated] (FLINK-26337) Avoid load flink conf each reconcile loop

[ https://issues.apache.org/jira/browse/FLINK-26337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-26337: --- Component/s: Kubernetes Operator > Avoid load flink conf each reconcile l

[jira] [Commented] (FLINK-26339) Introduce the webhook config to free the environment options

[ https://issues.apache.org/jira/browse/FLINK-26339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496827#comment-17496827 ] Aitozi commented on FLINK-26339: cc [~gyfora]  [~wangyang0918], I can work on

[jira] [Created] (FLINK-26339) Introduce the webhook config to free the environment options

Aitozi created FLINK-26339: -- Summary: Introduce the webhook config to free the environment options Key: FLINK-26339 URL: https://issues.apache.org/jira/browse/FLINK-26339 Project: Flink Issue Type

[jira] [Commented] (FLINK-26337) Avoid load flink conf each reconcile loop

[ https://issues.apache.org/jira/browse/FLINK-26337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496813#comment-17496813 ] Aitozi commented on FLINK-26337: Yes, I can take this ticket.  > Avoid load fli

[jira] [Commented] (FLINK-26337) Avoid load flink conf each reconcile loop

[ https://issues.apache.org/jira/browse/FLINK-26337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496791#comment-17496791 ] Aitozi commented on FLINK-26337: cc [~gyfora]  [~wangyang0918]  > Avoid loa

[jira] [Created] (FLINK-26337) Avoid load flink conf each reconcile loop

Aitozi created FLINK-26337: -- Summary: Avoid load flink conf each reconcile loop Key: FLINK-26337 URL: https://issues.apache.org/jira/browse/FLINK-26337 Project: Flink Issue Type: Sub-task

[jira] [Commented] (FLINK-26332) Move the Operator Env to the common Utils

[ https://issues.apache.org/jira/browse/FLINK-26332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496680#comment-17496680 ] Aitozi commented on FLINK-26332: I want to work on this :D > Move the Operator

[jira] [Updated] (FLINK-26332) Move the Operator Env to the common Utils

[ https://issues.apache.org/jira/browse/FLINK-26332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-26332: --- Parent: FLINK-25963 Issue Type: Sub-task (was: Improvement) > Move the Operator Env to the com

[jira] [Commented] (FLINK-17232) Rethink the implicit behavior to use the Service externalIP as the address of the Endpoint

[ https://issues.apache.org/jira/browse/FLINK-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496678#comment-17496678 ] Aitozi commented on FLINK-17232: Get it, thanks  > Rethink the implicit beha

[jira] [Created] (FLINK-26332) Move the Operator Env to the common Utils

Aitozi created FLINK-26332: -- Summary: Move the Operator Env to the common Utils Key: FLINK-26332 URL: https://issues.apache.org/jira/browse/FLINK-26332 Project: Flink Issue Type: Improvement

[jira] [Commented] (FLINK-17232) Rethink the implicit behavior to use the Service externalIP as the address of the Endpoint

[ https://issues.apache.org/jira/browse/FLINK-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17495844#comment-17495844 ] Aitozi commented on FLINK-17232: [~wangyang0918] Could you help review [PR|h

[jira] [Commented] (FLINK-20830) Add a type of HEADLESS_CLUSTER_IP for rest service type

[ https://issues.apache.org/jira/browse/FLINK-20830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492366#comment-17492366 ] Aitozi commented on FLINK-20830: [~wangyang0918] OK, I will create a backport PR

[jira] [Comment Edited] (FLINK-17232) Rethink the implicit behavior to use the Service externalIP as the address of the Endpoint

[ https://issues.apache.org/jira/browse/FLINK-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492365#comment-17492365 ] Aitozi edited comment on FLINK-17232 at 2/15/22, 5:16 AM: --

[jira] [Comment Edited] (FLINK-17232) Rethink the implicit behavior to use the Service externalIP as the address of the Endpoint

[ https://issues.apache.org/jira/browse/FLINK-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492365#comment-17492365 ] Aitozi edited comment on FLINK-17232 at 2/15/22, 5:15 AM: --

[jira] [Commented] (FLINK-17232) Rethink the implicit behavior to use the Service externalIP as the address of the Endpoint

[ https://issues.apache.org/jira/browse/FLINK-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492365#comment-17492365 ] Aitozi commented on FLINK-17232: Let me make it more clear. There are two impl

[jira] [Updated] (FLINK-26112) Port getRestEndpoint method to the specific service type subclass

[ https://issues.apache.org/jira/browse/FLINK-26112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-26112: --- Summary: Port getRestEndpoint method to the specific service type subclass (was: Port getEndpoint method

[jira] [Commented] (FLINK-17232) Rethink the implicit behavior to use the Service externalIP as the address of the Endpoint

[ https://issues.apache.org/jira/browse/FLINK-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492049#comment-17492049 ] Aitozi commented on FLINK-17232: After some dig for the [external IPs|h

[jira] [Commented] (FLINK-16601) Correct the way to get Endpoint address for NodePort rest Service

[ https://issues.apache.org/jira/browse/FLINK-16601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492038#comment-17492038 ] Aitozi commented on FLINK-16601: Hi [~felixzheng], I think this issue have already

[jira] [Updated] (FLINK-26112) Port getEndpoint method to the specific service type subclass

[ https://issues.apache.org/jira/browse/FLINK-26112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-26112: --- Description: In the [FLINK-20830|https://issues.apache.org/jira/browse/FLINK-20830], we introduce serval

[jira] [Updated] (FLINK-26112) Port getEndpoint method to the specific service type subclass

[ https://issues.apache.org/jira/browse/FLINK-26112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-26112: --- Description: In the [FLINK-20830|https://issues.apache.org/jira/browse/FLINK-20830]we introduce serval

[jira] [Updated] (FLINK-26112) Port getEndpoint method to the specific service type subclass

[ https://issues.apache.org/jira/browse/FLINK-26112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-26112: --- Description: In the [FLINK-20830|https://issues.apache.org/jira/projects/FLINK/issues/FLINK-20830]we

[jira] [Commented] (FLINK-26112) Port getEndpoint method to the specific service type subclass

[ https://issues.apache.org/jira/browse/FLINK-26112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17491973#comment-17491973 ] Aitozi commented on FLINK-26112: I found it's also an improvement of the imple

[jira] [Updated] (FLINK-26112) Port getEndpoint method to the specific service type subclass

[ https://issues.apache.org/jira/browse/FLINK-26112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-26112: --- Parent: FLINK-17196 Issue Type: Sub-task (was: Improvement) > Port getEndpoint method to

[jira] [Commented] (FLINK-17232) Rethink the implicit behavior to use the Service externalIP as the address of the Endpoint

[ https://issues.apache.org/jira/browse/FLINK-17232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17491971#comment-17491971 ] Aitozi commented on FLINK-17232: Hi, when i do some work to refactor the cod

[jira] [Updated] (FLINK-26112) Port getEndpoint method to the specific service type subclass

[ https://issues.apache.org/jira/browse/FLINK-26112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aitozi updated FLINK-26112: --- Description: In the [FLINK-20830 |https://issues.apache.org/jira/projects/FLINK/issues/FLINK-20830]we

[jira] [Created] (FLINK-26112) Port getEndpoint method to the specific service type subclass

Aitozi created FLINK-26112: -- Summary: Port getEndpoint method to the specific service type subclass Key: FLINK-26112 URL: https://issues.apache.org/jira/browse/FLINK-26112 Project: Flink Issue

<    1   2   3   4   5   6   7   8   9   >