-
Notifications
You must be signed in to change notification settings - Fork 70
✨ Add feature gate for registry+v1 bundle deploymentConfig #2527
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -500,3 +500,38 @@ Feature: Install ClusterExtension | |
| And ClusterExtension is available | ||
| And ClusterExtensionRevision "${NAME}-1" has label "olm.operatorframework.io/owner-kind" with value "ClusterExtension" | ||
| And ClusterExtensionRevision "${NAME}-1" has label "olm.operatorframework.io/owner-name" with value "${NAME}" | ||
|
|
||
| @DeploymentConfig | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we care about exercising each of the different deployment config options? (or maybe all of them at once?)
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think a subset of what's available is sufficient. I don't think we can test everything. As long as something gets there, we know it's working. Isn't this dependent on the bundle's JSON, so we really can't test everything? |
||
| Scenario: deploymentConfig nodeSelector is applied to the operator deployment | ||
| When ClusterExtension is applied | ||
| """ | ||
| apiVersion: olm.operatorframework.io/v1 | ||
| kind: ClusterExtension | ||
| metadata: | ||
| name: ${NAME} | ||
| spec: | ||
| namespace: ${TEST_NAMESPACE} | ||
| serviceAccount: | ||
| name: olm-sa | ||
| config: | ||
| configType: Inline | ||
| inline: | ||
| deploymentConfig: | ||
| nodeSelector: | ||
| kubernetes.io/os: linux | ||
| source: | ||
| sourceType: Catalog | ||
| catalog: | ||
| packageName: test | ||
| selector: | ||
| matchLabels: | ||
| "olm.operatorframework.io/metadata.name": test-catalog | ||
| """ | ||
| Then resource "deployment/test-operator" matches | ||
| """ | ||
| spec: | ||
| template: | ||
| spec: | ||
| nodeSelector: | ||
| kubernetes.io/os: linux | ||
| """ | ||
Uh oh!
There was an error while loading. Please reload this page.