-
Notifications
You must be signed in to change notification settings - Fork 105
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
[docs] Clarify community vs upstream-community OperatorSources #157
[docs] Clarify community vs upstream-community OperatorSources #157
Conversation
aravindhp
commented
Apr 4, 2019
•
edited
Loading
edited
- Add a note to call out to not install both community and upstream-community OperatorSources on the same cluster
- Move upstream-community-operators OperatorSource to deploy/upstream/
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.
/lgtm
/lgtm cancel |
/approve cancel |
3e87ae0
to
799993e
Compare
/lgtm |
/lgtm |
@aravindhp actually there is a typo in your commit message:
should be
|
Good catch @kevinrizza. Please request a change so that I don't forget to fix it. |
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.
Please fix typo in commit message.
/approve cancel |
06244ba
to
e4f6c95
Compare
@awgreene I have addressed your comments. Please review. @kevinrizza @tkashem please review. |
/test e2e-aws-operator |
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.
Please fix the upstream operator source path
e4f6c95
to
47d68bd
Compare
fc9f785
to
70a7713
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!
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 minus a bug in one of the example commands.
- Add a note to call out to not install both community and upstream-community OperatorSources on the same cluster - Move upstream-community-operators OperatorSource to deploy/upstream/
70a7713
to
b0c49e6
Compare
/lgtm |
Looks good @aravindhp |
/lgtm |
/approve |
Looks good! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aravindhp, galletti94, jeremylinlin, kevinrizza, SamiSousa The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |