-
Notifications
You must be signed in to change notification settings - Fork 232
Fix duplicate InstallerSets in Pipeline Reconciler #588
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
Fix duplicate InstallerSets in Pipeline Reconciler #588
Conversation
fe9fa9f to
2502a9d
Compare
|
The following is the coverage report on the affected files.
|
d4d7f9e to
5c7e936
Compare
|
The following is the coverage report on the affected files.
|
5c7e936 to
f623c33
Compare
Fix occurrence of duplicate installerSets in pre, post and main recociler logic of TektonPipeline reconciler Adds a label based querying to identify InstallerSets instead of querying by there name Signed-off-by: Nikhil Thomas <nikthoma@redhat.com>
Use Operator version instead of Component versions while deciding whether to recreate deployments and other resources during upgrades Signed-off-by: Nikhil Thomas <nikthoma@redhat.com>
f623c33 to
cc89c23
Compare
|
The following is the coverage report on the affected files.
|
|
The following is the coverage report on the affected files.
|
Add mechanism in TektonTriggers reconciler to make sure that duplicate InstallerSets doesnot exist. Move label based InstallerSet querying mechanism to tektoninstallerset package Signed-off-by: Nikhil Thomas <nikthoma@redhat.com>
cc89c23 to
afe8d85
Compare
|
The following is the coverage report on the affected files.
|
|
most of the review comments already addressed 👍 |
savitaashture
left a comment
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.
Thank you 👍
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: savitaashture 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 |
| ReadOnly bool | ||
| } | ||
|
|
||
| func OperatorVersion(ctx context.Context) (string, error) { |
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.
Can't we read this from the config map ?
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.
yes but the version is already in the env of pod so easier that way
why to do an API call.. :)
also configmap is for other external tools to read the version of operator
|
Thank you ! |
DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |

Fix occurrence of duplicate installerSets in pre, post and main
recociler logic of TektonPipeline reconciler
Adds a label based querying to identify InstallerSets instead of
querying by there name
Use Operator version instead of Component versions while deciding whether to recreate deployments and other resources during upgrades
Signed-off-by: Nikhil Thomas nikthoma@redhat.com
Changes
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Release Notes