Closed jmontleon closed 1 year ago
@shawn-hurley @mhrivnak @fabianvf
Do we want to build AO base image with a RPM like other container images we created, or do we want to try the newer approach OLM and others are using and skip RPMs?
If we continue with using RPMs, do we want to submit this PR to operator-sdk upstream instead of water-hole? Unsure what is best for now, trying to see if there is value in adding rpm spec and tito configs to upstream or will this be cruft that isn't needed by community.
Thoughts?
FWIW, I don't think this is of much value upstream necessarily. I'm just at a loss for where else to place it. I'm still of the mind that it makes easier for downstream, but if the multi-stage builds prove easy enough I could be convinced otherwise. I'm also aware things may change drastically when this all moves.
Closing because this is not the correct location anymore.
Successful build demonstrated at https://copr.fedorainfracloud.org/coprs/g/ansible-service-broker/ansible-operator-nightly/build/830643/