-
Notifications
You must be signed in to change notification settings - Fork 461
controller: Just sanity check templates, don't copy all of them #749
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
controller: Just sanity check templates, don't copy all of them #749
Conversation
We haven't changed how the renderer works in forever, but a lot of people keep changing the templates. This causes pointless churn in the test data and makes changing the templates unnecessarily painful. Further, I want to change how the rendering works to inherit from a common base, and having the unit test code also parsing the templates is problematic. Let's just sanity check that we have the pull secret and kubelet unit.
222bdda to
c3245b7
Compare
|
love this |
|
/test e2e-aws |
|
This makes a lot of sense to me! |
| foundPullSecretMaster := false | ||
| foundPullSecretWorker := false | ||
| foundKubeletUnitMaster := false | ||
| foundKubeletUnitWorker := false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is the most stupid nits every but declaring a boolean in Golang is the same as setting it to false so var found......, found .... , ..... bool is the same here (and this nit can live here for the time being, just wanted to point it out :D
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cgwalters, runcom The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
We haven't changed how the renderer works in forever, but a lot
of people keep changing the templates. This causes pointless churn
in the test data and makes changing the templates unnecessarily
painful.
Further, I want to change how the rendering works to inherit
from a common base, and having the unit test code also parsing
the templates is problematic.
Let's just sanity check that we have the pull secret and kubelet
unit.