-
Notifications
You must be signed in to change notification settings - Fork 20
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
Put the openshift directory in the code repository #650
Comments
@serverhorror Thanks for the suggestion! I really really would like to enforce that everyone has to define their infrastructure as code. Relying on a magic export (release manager) is not a good way to develop your software. So yes, I totally agree. BUT putting the templates into the repo has the effect that suddenly everyone is forced to modify their resources in the repo, instead of clicking around in OpenShift. While technically this is fine, we need to ensure everyone who has a say in this is happy to force all users to do that. Maybe we can survey existing projects to see if many of them define the OpenShift templates? A middle ground would be to add an option to the prov app to allow people to "opt out" of templates maybe? Further, we could potentially wait a little longer, and once we have full support for Helm (if that turns out to be a good way going forward), to start with shipping Helm charts with new components. |
A provisioning app option would be nice especially if the default would be to use infrastructure as code. Without such an option, provisioning could enable infrastructure as code by generating the openshift folder. I would not find this too burdensome, but others may have a different opinion. |
Minor note: Of courses that poses a catch-22, how would one manually clean up after a fat-fingered deployment so I guess that the OpenShift UI will stay as RW for users. |
Excellent point! But since ODS w. helm still needs to support the "old ways" I'm not sure that waiting will provide huge benefit (that is if it means that the "org internal" rollouts will have to wait for ODS5 or even longer to get that feature) |
You're preaching to the choir :) |
Is your feature request related to a problem? Please describe.
Every project we are working has had to make modifications to
openshift/*.yaml
Modify the priviosing app to put the templates from the
openshift/*
directory directly in the code that is being provided as boilerplate.Describe the solution you'd like
We had t repeatedly explain the same situation to users:
Our perception is that abstracting/hiding the OpenShift templates to the point where they are now is a tad too much. People would like to see most of the code that is being used to deploy their applications.
Describe alternatives you've considered
none -- that's our only idea
Additional context
none
The text was updated successfully, but these errors were encountered: