-
Notifications
You must be signed in to change notification settings - Fork 38
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
Specifiy Apicurio Registry Image (or version) #176
Comments
hi, you can try to specify an image using |
|
same issue here, maybe we can build and deploy the operator manually instead of using operatorhub.io? We can edit the version to be used under the install/.yaml? Any advice or pointers on this? |
Sorry, but the documentation is absolutely terrible. It would be so nice when someone decides to open source a project that documentation is a key point. To override the image you should do: apiVersion: registry.apicur.io/v1
kind: ApicurioRegistry
metadata:
name: des-apicurioregistry-mem
spec:
configuration:
persistence: "mem" # Optional (default value)
# NOTE: No additional configuration required for *dev* deployment
# ui:
# readOnly: true
env:
- name: AUTH_ENABLED
value: "true"
- name: AUTHZ_ENABLED
value: "true"
...
deployment:
image: quay.io/apicurio/apicurio-registry-mem:2.5.11.Final
... |
Is there a way to do this? I need to upgrade the Apicurio Registry to a version >=
2.1.4.Final
due to this issue.EDIT: Is it possible to specify other parameters such as deployment's readiness and liveness probes initial delay?
The text was updated successfully, but these errors were encountered: