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

add codeready-containers (crc) extension #94

Open
snowdrop-bot opened this issue May 19, 2020 · 0 comments
Open

add codeready-containers (crc) extension #94

snowdrop-bot opened this issue May 19, 2020 · 0 comments

Comments

@snowdrop-bot
Copy link
Collaborator

Description
as discussed on list an openshift/CRC extension would be nice to handle the defaults to have container-image / deploy settings just working out of box.

from list:

Ok thanks for your help Max and I also got help from Red Hat DevEx team, I got it working, need to be careful with the repo for the push and the ServiceAccount chosen You could do policy changes too, but if you just match up the names, for dev trialing, it's easier not to have to mess with policy. Here's what finally yielded a working solution:

./mvnw clean package -Dquarkus.container-image.build=true -Dquarkus.container-image.registry=default-route-openshift-image-registry.apps-crc.testing -Dquarkus.container-image.group=default

There should always be a "default" NameSpace in CodeReadyContainers.

A deploy yaml like the above in this thread should work but with
 - image: image-registry.openshift-image-registry.svc:5000/default/operator-example:1.0-SNAPSHOT

I tried to fully document the process and provide working example for this simplest possible operator deploy to CRC in the Readme of this repo here:

https://github.com/bentito/operator-example

If someone wants to try it with a fresh CRC install and has any comments I'd be happy to fix up. I freshened my CRC install and ran through all the steps outlined in that section of the Readme, so I am pretty sure it's correct and sufficient.

It's very cool to be able to run the whole thing locally from the Quarkus tooling all the way to working pod.

quarkusio#9317


$upstream:9317$

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants