fying job startup decision-making
>> while following existing conventions.
>>
>> --
>> *From:* Yang Wang
>> *Sent:* Tuesday, May 3, 2022 7:22 AM
>> *To:* Őrhidi Mátyás
>> *Cc:* Francis Conroy ; user <
>> user@
--
> *From:* Yang Wang
> *Sent:* Tuesday, May 3, 2022 7:22 AM
> *To:* Őrhidi Mátyás
> *Cc:* Francis Conroy ; user <
> user@flink.apache.org>
> *Subject:* Re: Using the official flink operator and kubernetes secrets
>
> Flink could not sup
SSWORD)"
It would be a great addition, simplifying job startup decision-making while
following existing conventions.
From: Yang Wang
Sent: Tuesday, May 3, 2022 7:22 AM
To: Őrhidi Mátyás
Cc: Francis Conroy ; user
Subject: Re: Using the official flin
Flink could not support environment replacement in the args. I think you
could access the env via "*System.getenv()*" in the user main method.
It should work since the user main method is executed in the JobManager
side.
Best,
Yang
Őrhidi Mátyás 于2022年4月28日周四 19:27写道：
> Also,
>
> just
Also,
just declaring it in the flink configs should be sufficient, no need to
define it in the pod templates:
flinkConfiguration:
kubernetes.env.secretKeyRef:
"env:DJANGO_TOKEN,secret:switchdin-django-token,key:token"
Best,
Matyas
On Thu, Apr 28, 2022 at 1:17 PM Őrhidi Mátyás
wrote:
>
Hi Francis,
I suggest accessing the environment variables directly, no need to pass
them as command arguments I guess.
Best,
Matyas
On Thu, Apr 28, 2022 at 11:31 AM Francis Conroy <
francis.con...@switchdin.com> wrote:
> Hi all,
>
> I'm trying to use a kubernetes secret as a command line
Hi all,
I'm trying to use a kubernetes secret as a command line argument in my job
and the text replacement doesn't seem to be happening. I've verified
passing the custom args via the command line on my local flink cluster but
can't seem to get the environment var replacement to work.
