Skip to content

Allow ImagePullSecret Definition without ServiceAccount for Knative Deployment #32545

@richardbischof

Description

@richardbischof

Description

Hello,

I want to use Quarkus with the Kubernetes Extension to Deploy to IBM Cloud Code Engine, which is basically a managed Knative. Therefore I have to build the image, push it to my private registry and then build Knative-Deployment Descriptors.

Because my image is saved in a private registry, I have to provide an ImagePullSecret. I configured in my applications.properties
quarkus.knative.image-pull-secrets=ibm-container-registry

With this option I get an additional ServiceAccount generated, which is configured to use the secret.

But Knative (and IBM Cloud Code Engine) expect those from the Knative Services Types and don't support creation of own Service Accounts, see
https://github.com/knative/specs/blob/main/specs/serving/knative-api-specification-1.0.md#spec-3

If you point me in the right direction, I would love to solve this issue by myself and provide a patch.

Implementation ideas

If the Deployment Target is Knative, then don't create a new service account and instead set the image pull secret in the Service Object.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions