You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 12, 2024. It is now read-only.
It would be great if we had a dockerhub new project wizard in the create new project UI.
A way to search and select images in dockerhub, then one click wrap any docker image with a f-m-p enabled java project. The new project which is used to generate the manifest is checked into version control along with a selected pipeline like any other new project we have today.
The f-m-p enabled project is an implementation detail that we can hide, in fact the console Source wiki need not show anything other than the contents of src/main/fabric8, just allow folks to edit a generated deployment.yml or svc.yml for example.
The advantage is developers can then select any dockerhub image and automatically have the basic kubernetes resources generated along with the fabric8 CI/CD features. A user need not know anything about the java project and just focus on extending the generated YAML to fit their needs.
If we really wanted to nail it then we could also have kubernetes YAML validation in the wiki but thats a separate issue I guess.
The text was updated successfully, but these errors were encountered:
We could even have a 'new this month' image or 'most stars this month' so folks can try out the trending images with 2 clicks, all backed by the existing CD features.
There is a a lot of images on dockerhub, so I guess some search would be required, and maybe online search against dockerhub. But yeah its a great idea.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be great if we had a dockerhub new project wizard in the create new project UI.
A way to search and select images in dockerhub, then one click wrap any docker image with a f-m-p enabled java project. The new project which is used to generate the manifest is checked into version control along with a selected pipeline like any other new project we have today.
The f-m-p enabled project is an implementation detail that we can hide, in fact the console Source wiki need not show anything other than the contents of
src/main/fabric8
, just allow folks to edit a generated deployment.yml or svc.yml for example.The advantage is developers can then select any dockerhub image and automatically have the basic kubernetes resources generated along with the fabric8 CI/CD features. A user need not know anything about the java project and just focus on extending the generated YAML to fit their needs.
If we really wanted to nail it then we could also have kubernetes YAML validation in the wiki but thats a separate issue I guess.
The text was updated successfully, but these errors were encountered: