Skip to content
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

Merged
merged 3 commits into from
Dec 3, 2021
Merged

Add kustomize files for 0.8.0 release #291

merged 3 commits into from
Dec 3, 2021

Conversation

idlewis
Copy link
Collaborator

@idlewis idlewis commented Nov 30, 2021

Also update the kustomize CRDs to pickup the most
recent changes

As per the request in issue #177

Copy link
Member

@leochr leochr left a 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
Copy link
Member

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
@idlewis
Copy link
Collaborator Author

idlewis commented Dec 2, 2021

@leochr I've addressed the comments about the watch-own-namespace scenario

Copy link
Member

@leochr leochr left a 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:
Copy link
Member

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
Copy link
Member

@leochr leochr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Thanks

@leochr leochr merged commit 3573bea into main Dec 3, 2021
@idlewis idlewis deleted the kustom-0.8.0 branch December 6, 2021 11:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants