-
Notifications
You must be signed in to change notification settings - Fork 145
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
[feat] Make use of known-to-be-existent stuff on Openshift #196
Comments
@markusthoemmes I think this should be covered by our On Cluster Builds FT - potentially by TP. |
Checking on this, can this issue be closed? |
@omerbensaadon this is still not resolved |
Closing as a duplicate of #620 |
related to #620 |
Repository owner
moved this from Ready To Work
to In Design
in Func Roadmap
Dec 8, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the solution you'd like
I'd love if I wouldn't have to deal with the fact that we're building images when running on Openshift at all. Wouldn't it be cool if one could just do
kn faas deploy
on an Openshift cluster without additional setup (i.e. dockerhub accounts etc.).We discussed briefly how it's non trivial to talk to the Openshift internal-registry, but maybe we can salvage Openshift builds (and their binary input feature) to build images on the cluster and into the registry on the fly.
The text was updated successfully, but these errors were encountered: