Skip to content
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

As an user, I want to pull my application image from a private container registry #233

Open
jmesnil opened this issue Sep 19, 2022 · 1 comment
Labels
Basic Install (I) Features for Phase I of the Operator capability levels

Comments

@jmesnil
Copy link
Member

jmesnil commented Sep 19, 2022

When the statefulset is created, the container image must be pullable from the container platform.

Public images can be pulled without any issue.
On OpenShift, any image in the OpenShift image registry can be pulled.

But if my application image is in a private container registry, I don't have the ability to provide an imagePullSecret that would be used to pull my image when the pods are started.

To support this use case, the WildFlyServer CRD can be enhanced with a imagePullSecrets array that will be used to populate the pod template spec.imagePullSecrets field.

The use case would then be fulfilled with the CRD:

spec:
  applicationImage: quay.io/my-private-group/my-private-image
  imagePullSecrets:
    - name: my-private-pull-secret
@jmesnil jmesnil added the Basic Install (I) Features for Phase I of the Operator capability levels label Sep 19, 2022
@jmesnil
Copy link
Member Author

jmesnil commented Sep 19, 2022

This is related to the same feature for the Helm Chart for WildFly wildfly/wildfly-charts#82

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Basic Install (I) Features for Phase I of the Operator capability levels
Projects
None yet
Development

No branches or pull requests

1 participant