Re: Query about flink job manager dashboard

[Berkay Polat via user]

Hi Chesnay,

I have a similar question on this topic. Is there an option to disable the
frontend altogether but still use REST APIs?

Thanks

On Wed, Nov 30, 2022 at 1:37 AM Chesnay Schepler  wrote:

> There's no way to disable the jar submission in the UI but have it still
> work via the REST API.
>
> On 30/11/2022 06:16, naga sudhakar wrote:
>
> After disabling the cancel, submit flags facing issues with below api
> calls.
>
> 1) /jars giving 404
> 2) /jars/upload
> 3) /jars/{jarid}/run
>
> Is there any config changes needed to have these apis work?
>
>
> On Mon, 28 Nov, 2022, 7:00 PM naga sudhakar, 
> wrote:
>
>> Hi,
>> We are able to disable this cancela nd upload otpion in ui.
>> But this is having issues with endpoints for below.
>> Get call for /jars to list all uploaded jars and post call
>> /jars/{jarid}/run are giving 404 after disabling the two flags.
>> Is the process of uploading jars and running a jar with specific id
>> changes after this change?
>>
>> Please suggest.
>>
>> Thanks & Regards,
>> Nagasudhakar
>>
>> On Thu, 24 Nov, 2022, 2:07 PM Martijn Visser, 
>> wrote:
>>
>>> Hi,
>>>
>>> 1) No, that's currently not possible.
>>> 2) You could consider disabling to disallow uploading new JARs and/or
>>> cancelling jobs from the UI. See
>>> https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#advanced-options-for-flink-web-ui
>>> 
>>>
>>> Best regards,
>>>
>>> Martijn
>>>
>>> On Thu, Nov 24, 2022 at 3:44 AM naga sudhakar 
>>> wrote:
>>>
 Hi Team,
> Greetings!!!
> I am a software developer using apache flink and deploying flink jobs
> using the same. I have two queries about flink job manager dashboard. Can
> you please help with below?
>
> 1) is it possible to add login mechanism for the flink job manager
> dash board and have a role based mechanism for viewing running jobs,
> cancelling jobs, adding the jobs?
> 2) is it possible to disable to dash bord display but use api to do
> the same operations using API?
>
>
> Thanks,
> Nagasudhakar.
>

> --
*BERKAY POLAT*
Software Engineer SMTS | MuleSoft at Salesforce
Mobile: 443-710-7021

Fwd: Stand alone K8s HA mode with Static Tokens Used by Service Accounts

[Berkay Polat via user]

Hi team,

Bumping this up again, from the AWS docs, the suggested approach is to
simply upgrade the K8s java SDK client (
https://github.com/kubernetes-client/java/) being used. However, in Flink's
case with the io.fabric8 K8s client, I am not sure how to handle it. Any
help and guidance would be much appreciated.

Thanks,

-- Forwarded message -
From: Berkay Polat 
Date: Thu, Nov 17, 2022 at 12:36 PM
Subject: Stand alone K8s HA mode with Static Tokens Used by Service Accounts
To: 


Hi,

Our team has been using flink 1.15 and we have a stand alone K8s flink
setup that uses K8s HA services for its HA mode. Recently, our organization
is in the works of updating their EKS clusters' Kubernetes versions to 1.21
or later. We received a request from our support team that the service
accounts associated with our stand alone flink cluster have been using
static tokens, which is not permitted for newer K8s versions. Instead, they
requested us to switch to a refresh token approach (
https://docs.aws.amazon.com/eks/latest/userguide/service-accounts.html#identify-pods-using-stale-tokens
).

>From what I understand, in flink 1.15, HA mode is using version 5.5.0 of
io.fabric8's kubernetes client and it seems that it is compatible with K8s
1.21.1 and later (
https://github.com/fabric8io/kubernetes-client#compatibility-matrix) so I
am not sure what the underlying limitation/issue is here.

The AWS doc link I referred to earlier recommends upgrading versions for
Kubernetes Client SDKs but it refers to io.kubernetes's client SDKs, not
io.fabric8.

Could someone shed some light on it? Would it be worth it to request a
change to upgrade the io.fabric8 kubernetes client version to a newer
version?

Thanks,
-- 
*BERKAY POLAT*
Software Engineer SMTS | MuleSoft at Salesforce
Mobile: 443-710-7021




-- 
*BERKAY POLAT*
Software Engineer SMTS | MuleSoft at Salesforce
Mobile: 443-710-7021

Stand alone K8s HA mode with Static Tokens Used by Service Accounts

[Berkay Polat via user]

Hi,

Our team has been using flink 1.15 and we have a stand alone K8s flink
setup that uses K8s HA services for its HA mode. Recently, our organization
is in the works of updating their EKS clusters' Kubernetes versions to 1.21
or later. We received a request from our support team that the service
accounts associated with our stand alone flink cluster have been using
static tokens, which is not permitted for newer K8s versions. Instead, they
requested us to switch to a refresh token approach (
https://docs.aws.amazon.com/eks/latest/userguide/service-accounts.html#identify-pods-using-stale-tokens
).

>From what I understand, in flink 1.15, HA mode is using version 5.5.0 of
io.fabric8's kubernetes client and it seems that it is compatible with K8s
1.21.1 and later (
https://github.com/fabric8io/kubernetes-client#compatibility-matrix) so I
am not sure what the underlying limitation/issue is here.

The AWS doc link I referred to earlier recommends upgrading versions for
Kubernetes Client SDKs but it refers to io.kubernetes's client SDKs, not
io.fabric8.

Could someone shed some light on it? Would it be worth it to request a
change to upgrade the io.fabric8 kubernetes client version to a newer
version?

Thanks,
-- 
*BERKAY POLAT*
Software Engineer SMTS | MuleSoft at Salesforce
Mobile: 443-710-7021