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
[deprecation]: Deprecate CatalogSourceConfig API #302
[deprecation]: Deprecate CatalogSourceConfig API #302
Conversation
/hold |
7b737bd
to
06b17cf
Compare
/retest |
/hold cancel |
/test e2e-aws |
pkg/operatorsource/configuring.go
Outdated
@@ -105,9 +105,9 @@ func (r *configuringReconciler) Reconcile(ctx context.Context, in *v1.OperatorSo | |||
} | |||
|
|||
// Now that we have updated the datastore, let's check if the opsrc is new. | |||
// If it is, let's force a resync for CatalogSourceConfig. | |||
// If it is, let's force a resync for CatalogSources. | |||
if isResyncNeeded { |
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.
This whole section of logic seems unnecessary now, right? I don't think this comment is correct, because the resyncer updates the cached app-registry info that the catalogsourceconfig controller uses to know about what metadata was pulled. Since they don't exist anymore, the whole cache sync just isn't needed anymore
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.
@kevinrizza that's what I thought too, but when I removed this the catalogsource that was being created from the opsrc was missing the packages it is supposed to have. I discovered that after this test failed when this logic was not there: https://github.com/operator-framework/operator-marketplace/blob/master/pkg/operatorsource/configuring_test.go#L27
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.
@kevinrizza turns out that was because of an Expect()
in the test, which I have removed, so the resync logic has been removed. FYI we still need to WriteMetaDataToDataStore()
.
Updated PR.
func testRestoreCscService(t *testing.T) { | ||
err := deleteCheckRestoreChild(t, "Service", v2.CatalogSourceConfigKind) | ||
assert.NoError(t, err, cscErrMsg) | ||
} |
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.
Not blocking, just had a comment about the cache sync that exists between the two controllers -- I think we can just rip out any reference to the cache. But if that is a non trivial amount of work, then let's at least update the comments to reflect that more accurately
023030f
to
8dfd36e
Compare
/lgtm |
/retest |
} | ||
migrator := migrator.New(clientGo) | ||
err = migrator.Migrate() | ||
if err != nil { |
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.
this can be a followup pr, but if the migration fails we should probably retry it a couple of times.
(failing to migrate is not the worst, the crd will just stick around)
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.
@ecordell till now I haven't seen any error that could be non-deterministic. If we fail once, we're most likely going to fail all the time. I'm not sure if blocking the operator because we're trying multiple times is better than failing fast and reporting the error.
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: anik120, ecordell 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 Please review the full test history for this PR and help us cut down flakes. |
7 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
bdbcd2d
to
44612e7
Compare
This PR removes the CatalogSourceConfig API in it's entirety.
/test e2e-aws |
return err | ||
} | ||
labels := catsrc.Labels | ||
delete(labels, builders.CscOwnerNameLabel) |
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.
This removes the labels, but I thought there were actual ownerrefs on the catalogsources? Is that not true?
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.
@ecordell looks like we just set the labels: https://github.com/operator-framework/operator-marketplace/blob/master/pkg/grpccatalog/grpccatalog.go#L116-L119
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.
We don't use ownerrefs because catalogsourceconfigs are created across namespaces
/lgtm |
The CatalogSourceConfig is being deprecated from Openshift 4.5. This PR removes the CSC related tests. Ref: operator-framework/operator-marketplace#302
The CatalogSourceConfig is being deprecated from Openshift 4.5. This PR removes the CSC related tests. Ref: operator-framework/operator-marketplace#302
The CatalogSourceConfig is being deprecated from Openshift 4.5. This PR removes the CSC related tests. Ref: operator-framework/operator-marketplace#302
The CatalogSourceConfig is being deprecated from Openshift 4.5. This PR removes the CSC related tests. Ref: operator-framework/operator-marketplace#302
The CatalogSourceConfig is being deprecated from Openshift 4.5. This PR removes the CSC related tests. Ref: operator-framework/operator-marketplace#302
The CatalogSourceConfig is being deprecated from Openshift 4.5. This PR removes the CSC related tests. Ref: operator-framework/operator-marketplace#302
The CatalogSourceConfig is being deprecated from Openshift 4.5. This PR removes the CSC related tests. Ref: operator-framework/operator-marketplace#302
The CatalogSourceConfig is being deprecated from Openshift 4.5. This PR removes the CSC related tests. Ref: operator-framework/operator-marketplace#302
The CatalogSourceConfig is being deprecated from Openshift 4.5. This PR removes the CSC related tests. Ref: operator-framework/operator-marketplace#302
The CatalogSourceConfig is being deprecated from Openshift 4.5. This PR removes the CSC related tests. Ref: operator-framework/operator-marketplace#302
The CatalogSourceConfig is being deprecated from Openshift 4.5. This PR removes the CSC related tests. Ref: operator-framework/operator-marketplace#302
CatalogSourceConfig has been removed (not deprecated) on OLM side with operator-framework/operator-marketplace#302 Avoid using it and use only OperatorSource in all the marketplace based deployment scripts. The OperatorSource will implicitly trigger the creation of a CatalogSource with the same name. Signed-off-by: Simone Tiraboschi <stirabos@redhat.com>
* Avoid CatalogSourceConfig CatalogSourceConfig has been removed (not deprecated) on OLM side with operator-framework/operator-marketplace#302 Avoid using it and use only OperatorSource in all the marketplace based deployment scripts. The OperatorSource will implicitly trigger the creation of a CatalogSource with the same name. Signed-off-by: Simone Tiraboschi <stirabos@redhat.com> * kustomize updates: 1. fix targetNamespace in OperatorGroup to reflect the desired namespace. 2. fix secret creation containing the quay token - quotes removed. 3. added deployment examples in readme file. Signed-off-by: orenc1 <ocohen@redhat.com> Co-authored-by: Simone Tiraboschi <stirabos@redhat.com>
The syncing of remote app-registry was removed by operator-framework#302 since it was tied to the syncing of the child CatalogSourceConfig which was removed in operator-framework#302. This PR puts the syncing of remote app-registry back in, minus the syncing of the non-existing child catalogSourceConfig.
The syncing of remote app-registry was removed by operator-framework#302 since it was tied to the syncing of the child CatalogSourceConfig which was removed in operator-framework#302. This PR puts the syncing of remote app-registry back in, minus the syncing of the non-existing child catalogSourceConfig.
Description of the change:
This PR removes the CatalogSourceConfig API in it's entirety.
Motivation for the change:
Reviewer Checklist
/docs