-
Notifications
You must be signed in to change notification settings - Fork 23
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 kustomize files for 0.8.0 release #291
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.
@idlewis Thanks! Added a minor comment for the watch-own-namespace scenario. Have some questions about the watch-another-namespace scenario, let's chat tomorrow.
fieldRef: | ||
fieldPath: metadata.namespace | ||
- name: WATCH_NAMESPACE | ||
value: default |
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.
Value for WATCH_NAMESPACE can also be specified like OPERATOR_NAMESPACE. In that case the example for watching own namespace can be simplified I think.
fyi to avoid merge conflicts, Melissa has the change to update kustomize/daily/runtime-component-operator.yaml in her PR
Also update the kustomize CRDs to pickup the most recent changes
@leochr I've addressed the comments about the watch-own-namespace scenario |
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.
@idlewis Thanks for the update. One minor comment about the examples.
@@ -11,3 +11,4 @@ spec: | |||
env: | |||
- name: WATCH_NAMESPACE | |||
value: rco-watched-ns2 | |||
valueFrom: |
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.
Since this example builds upon overlay, which already removes the valueFrom
field, it doesn't need to be specified here again.
As the relevant field is already removed in the parent overlay
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. Thanks
Also update the kustomize CRDs to pickup the most
recent changes
As per the request in issue #177