Strimzi
-
|
I looked at [cluster-operator/src/main/java/io/strimzi/operator/cluster/model/KafkaConnectBuild.java]. It appears that this file is only required if using OpenShift. I am not using OpenShift and specified spec.build.output.type as "docker". Should my build try to mount a volume with this file included. It is causing the build to fail. This is my sanitized KafkaConnect yaml. apiVersion: kafka.strimzi.io/v1beta2 |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
|
No, it is required anytime you push to some container registry that requires authentication. Both on OpenShift but also outside of OpenShift. |
Beta Was this translation helpful? Give feedback.
-
|
OK. Are these for accessing our private repository or something else? The reason I ask is that we already supply that as "pushSecret:" |
Beta Was this translation helpful? Give feedback.
-
|
The secret in the Just to be clear -> both are optional, you need them only if authentication is needed to push the new container image in the first case or pull it in the second case. |
Beta Was this translation helpful? Give feedback.
-
|
Ok. I specified the key in both but still get the mount volume error.
MountVolume.SetUp failed for volume "docker-credentials" : references
non-existent secret key: .dockerconfigjson
…On Fri, Nov 17, 2023 at 5:24 PM Jakub Scholz ***@***.***> wrote:
The secret in the .spec.build section is used to push the newly built
image to the registry specified in .spec.build.image. The one in
.spec.template.pod is used for pulling the image in the Connect pods.
Just to be clear -> both are optional, you need them only if
authentication is needed to push the new container image in the first case
or pull it in the second case.
—
Reply to this email directly, view it on GitHub
<#9359 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2K43HVZSKILNF3FJM6IS5LYE7PZLAVCNFSM6AAAAAA7QAWFH6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TMMBTGYZTK>
.
You are receiving this because you authored the thread.Message ID:
<strimzi/strimzi-kafka-operator/repo-discussions/9359/comments/7603635@
github.com>
--
[image: Profile picture] Pat McNeace
DevSecOps Engineer
855.895.8951 [office] // 706.622.4263 [fax]
LinkedIn <https://www.linkedin.com/company/securegive> // Facebook
<https://www.facebook.com/securegive> // Website
<https://www.securegive.com?utm_source=signaturesatori&utm_medium=email&utm_campaign=signature>
[image: SecureGive]
------------------------------
|
Beta Was this translation helpful? Give feedback.
-
|
And does your secret contain that key? The |
Beta Was this translation helpful? Give feedback.
-
|
I transfer the repository creds to the cluster as username and key. I will
create a JSON file containing them as well.
…On Mon, Nov 20, 2023 at 9:41 AM Jakub Scholz ***@***.***> wrote:
And does your secret contain that key? The type:
kubernetes.io/dockerconfigjson secrets with Docker registry credentials
should normally have this key.
—
Reply to this email directly, view it on GitHub
<#9359 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2K43HQWRLC2WJ7255D6MKDYFNTYFAVCNFSM6AAAAAA7QAWFH6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TMMRQGI4TS>
.
You are receiving this because you authored the thread.Message ID:
<strimzi/strimzi-kafka-operator/repo-discussions/9359/comments/7620299@
github.com>
--
[image: Profile picture] Pat McNeace
DevSecOps Engineer
855.895.8951 [office] // 706.622.4263 [fax]
LinkedIn <https://www.linkedin.com/company/securegive> // Facebook
<https://www.facebook.com/securegive> // Website
<https://www.securegive.com?utm_source=signaturesatori&utm_medium=email&utm_campaign=signature>
[image: SecureGive]
------------------------------
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks, Jakub! We usually use type.opaque for secrets. Changed to
type.registry. The problem was fixed.
On Mon, Nov 20, 2023 at 10:00 AM Pat McNeace ***@***.***>
wrote:
… I transfer the repository creds to the cluster as username and key. I
will create a JSON file containing them as well.
On Mon, Nov 20, 2023 at 9:41 AM Jakub Scholz ***@***.***>
wrote:
> And does your secret contain that key? The type:
> kubernetes.io/dockerconfigjson secrets with Docker registry credentials
> should normally have this key.
>
> —
> Reply to this email directly, view it on GitHub
> <#9359 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A2K43HQWRLC2WJ7255D6MKDYFNTYFAVCNFSM6AAAAAA7QAWFH6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TMMRQGI4TS>
> .
> You are receiving this because you authored the thread.Message ID:
> <strimzi/strimzi-kafka-operator/repo-discussions/9359/comments/7620299@
> github.com>
>
--
[image: Profile picture] Pat McNeace
DevSecOps Engineer
855.895.8951 [office] // 706.622.4263 [fax]
LinkedIn <https://www.linkedin.com/company/securegive> // Facebook
<https://www.facebook.com/securegive> // Website
<https://www.securegive.com?utm_source=signaturesatori&utm_medium=email&utm_campaign=signature>
[image: SecureGive]
------------------------------
--
[image: Profile picture] Pat McNeace
DevSecOps Engineer
855.895.8951 [office] // 706.622.4263 [fax]
LinkedIn <https://www.linkedin.com/company/securegive> // Facebook
<https://www.facebook.com/securegive> // Website
<https://www.securegive.com?utm_source=signaturesatori&utm_medium=email&utm_campaign=signature>
[image: SecureGive]
------------------------------
|
Beta Was this translation helpful? Give feedback.
And does your secret contain that key? The
type: kubernetes.io/dockerconfigjsonsecrets with Docker registry credentials should normally have this key.