-
Notifications
You must be signed in to change notification settings - Fork 98
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
Add stubbed NginxProxy CRD and watcher #1216
Add stubbed NginxProxy CRD and watcher #1216
Conversation
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.
Shall we also enable pipeline on this branch?
We probably should, but as a separate PR into the main branch. |
Problem: We have two upcoming stories that require the new NginxProxy CRD in order to be worked on. Solution: To prevent one story from being blocked by the other, this work adds the new CRD with a blank spec, a controller that watches for it and triggers an update, and sets the status on the resource.
7a51762
to
ec4c46d
Compare
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.
looks good!
a few consistency issues + some suggestions.
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.
👍
Problem: We have two upcoming stories that require the new NginxProxy CRD in order to be worked on. Solution: To prevent one story from being blocked by the other, this work adds the new CRD with a blank spec, a controller that watches for it and triggers an update, and sets the status on the resource.
Problem: We have two upcoming stories that require the new NginxProxy CRD in order to be worked on.
Solution: To prevent one story from being blocked by the other, this work adds the new CRD with a blank spec, a controller that watches for it and triggers an update, and sets the status on the resource.
Testing: Manually verified that updates are properly handled and status is set.
Please focus on (optional): I left a TODO for whoever implements the CRD fields to add additional unit testing.