-
Notifications
You must be signed in to change notification settings - Fork 413
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
MCC should have MCs Ignition validation #502
Comments
On it! |
Ok, so for this, I'm going to do #498 first because without an ignition version those mcs will fail any validation that I add. |
2 tasks
kikisdeliveryservice
added a commit
to kikisdeliveryservice/machine-config-operator
that referenced
this issue
Mar 12, 2019
Currently, ssh and registries machineconfigs do not have ignition versions. PR ensure that when those configs are generated, version is not empty (current value = 2.2.0) Also, created helper function in controller/common NewIgnConfig that returns an empty ignition config with version 2.2.0. Closes: openshift#498 Pre-req for: openshift#502
kikisdeliveryservice
added a commit
to kikisdeliveryservice/machine-config-operator
that referenced
this issue
Mar 15, 2019
Add check to render_controller.go to ensure that all machineconfigs merged by getRenderedMachineConfig() contain valid ignition configs. Closes: openshift#502
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Taken from: #481 (comment)
We should add ignition validation to the MCC as well (it's gonna be in MCD via #481 )
The text was updated successfully, but these errors were encountered: