-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add mount of notification bearer secret in generated CR #315
Add mount of notification bearer secret in generated CR #315
Conversation
Signed-off-by: gabriel-farache <[email protected]>
fa38fa5
to
4153999
Compare
26410db
to
f3891fe
Compare
f3891fe
to
a2b3638
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm generally okay with this, still having doubts about secret.properties, but lets try that for now.
LGTM
scripts/gen_manifests.sh
Outdated
@@ -50,6 +45,11 @@ SONATAFLOW_CR=manifests/01-sonataflow_${workflow_id}.yaml | |||
yq --inplace eval '.metadata.annotations["sonataflow.org/profile"] = "prod"' "${SONATAFLOW_CR}" | |||
|
|||
yq --inplace ".spec.podTemplate.container.image=\"quay.io/orchestrator/serverless-workflow-${workflow_id}:latest\"" "${SONATAFLOW_CR}" | |||
yq --inplace ".spec.podTemplate.container.envFrom=[{\"secretRef\": { \"name\": \"${workflow_id}-creds\"}}]" "${SONATAFLOW_CR}" | |||
|
|||
if [ "$ENABLE_PERSISTENCE" = false ]; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm handling this as part of #313
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was hoping for your pr to be merged first and have the auto merge do its job
But I'll revert this change
We can push this binary into the tools container image and use it there.
Same for kn
…On Mon, 15 Jul 2024 at 19:06 gabriel-farache ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In scripts/gen_manifests.sh
<#315 (comment)>
:
> @@ -15,6 +15,15 @@ else
echo "kn cli already available"
fi
+if [ ! -f kubectl ]; then
Because it will not be in the image we are pulling and if we execute it
locally it will look into the bin path or next to the files, like for kn
—
Reply to this email directly, view it on GitHub
<#315 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGBYHCGVPRBEOQNWJSZEX3ZMPXPHAVCNFSM6AAAAABK4CR2AKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCNZYGEZTEOBQHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
On second thought perhaps using kubectl create just to create a secret is
an overkill
…On Mon, 15 Jul 2024 at 19:20 Roy Golan ***@***.***> wrote:
We can push this binary into the tools container image and use it there.
Same for kn
On Mon, 15 Jul 2024 at 19:06 gabriel-farache ***@***.***>
wrote:
> ***@***.**** commented on this pull request.
> ------------------------------
>
> In scripts/gen_manifests.sh
> <#315 (comment)>
> :
>
> > @@ -15,6 +15,15 @@ else
> echo "kn cli already available"
> fi
>
> +if [ ! -f kubectl ]; then
>
> Because it will not be in the image we are pulling and if we execute it
> locally it will look into the bin path or next to the files, like for kn
>
> —
> Reply to this email directly, view it on GitHub
> <#315 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABGBYHCGVPRBEOQNWJSZEX3ZMPXPHAVCNFSM6AAAAABK4CR2AKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCNZYGEZTEOBQHE>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Signed-off-by: gabriel-farache <[email protected]>
a2b3638
to
03d7d84
Compare
reopening => #317 |
Add mount of notification bearer secret in generated CR
Closes part of https://issues.redhat.com/browse/FLPATH-1498