-
Notifications
You must be signed in to change notification settings - Fork 70
Upstream sync #187
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
Upstream sync #187
Conversation
Update the .github/workflows/quickstart.yml github action and replace the usage of `kubectl wait ...` with a function that waits until the various OLM component deployment resources are present and reporting an available status. Using `kubectl wait ...` is potentially problematic as it doesn't support waiting until the creation of that resource, so in the case the PackageServer deployment doesn't exist yet as the catalog/olm operators are still being setup, this action will fail as `kubectl wait ...` will return a non-zero exit code. Signed-off-by: timflannagan <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: b98ff9d1601b41847fb47445a8366a1145c7cbe6
Failing to fetch catalog content should not silently return an empty cache. Instead, it should fail outright with an error that indicates which catalog(s) could not be fetched. Signed-off-by: Ben Luddy <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 6ab5f1634093c91d7027b9245a88ede7b807088b
Signed-off-by: timflannagan <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 1e7e1cc81d5c3e0f2de2a06cb4315ea622371cbe
Update to containerd 1.4.8 Signed-off-by: Vu Dinh <[email protected]> Upstream-repository: operator-registry Upstream-commit: aa44cbec0df254fb503a34384a85e197a7e68e6f
Update the doc/design/release.md documentation around how to generate the root CHANGELOG.md. Previously, when running into API rate limiting behaviors locally, the suggestion was to modify a variable in the Ruby gem package that no longer exists. Now, specify the --max-issues CLI flag to lower the number of API requests to the OLM repository. Signed-off-by: timflannagan <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 5c40752a9605669d34234bf18a93dba948b59439
…ull requests (#2299) Update the e2e-tests.yml github workflow and avoid running that action on PRs that only change the doc directory. Signed-off-by: timflannagan <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 939bf94f834181d60a713191f78b13b80c7bec0f
Signed-off-by: Evan <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 538b1315eace85e33df7b2893a85a000f8757349
Signed-off-by: Evan <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 44fc44daf778cd9d36d6b6eb8edf63ff5a202304
… the root fs (openshift#733) Update internal/declcfg/load.go and avoid processing any files that are named `.indexignore` when walking the declarative config index root filesystem. When validating declarative config directories, the .indexignore file was being processed and validated. Signed-off-by: timflannagan <[email protected]> Upstream-repository: operator-registry Upstream-commit: 78f27b39dc098c2e56681d9a3d8e786aae95d4fe
Signed-off-by: Joe Lanford <[email protected]> Upstream-repository: operator-registry Upstream-commit: a390f86b3ca429c9618a7c20a31406bc2bd6ed16
Signed-off-by: Ben Luddy <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 3a565917233c72d098f3a60d9239f0e3c5b55f76
Signed-off-by: Daniel Messer <[email protected]> Upstream-repository: operator-registry Upstream-commit: 70cec5728f5634fc696e13a0608dd7d01a170e12
… workflow (openshift#730) Update the test.yml test workflow and replace the `e2e-kind` job name with `e2e`. Before, the e2e test workflow had ran e2e tests against both kind and minikube clusters before the latter job was removed entirely. Signed-off-by: timflannagan <[email protected]> Upstream-repository: operator-registry Upstream-commit: ff2c921e414926a013f82448b7241bc84fc95372
…penshift#734) Signed-off-by: Daniel Sover <[email protected]> Upstream-repository: operator-registry Upstream-commit: b82684903f7af4e483efe5629d18c9a6db036dcb
build X.Y, X, and latest opm images but only latest if X.Y.Z is latest semver in HEAD and X.Y/X if the current HEAD commit is tagged. Signed-off-by: Eric Stroczynski <[email protected]> Upstream-repository: operator-registry Upstream-commit: 6f1a54f7b7b4f5e4f062fde42cb477ae25d438f6
Signed-off-by: Daniel Messer <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: c76e1cd8e24d555f59379f07faff538f6f5a4191
…t#750) Signed-off-by: Joe Lanford <[email protected]> Upstream-repository: operator-registry Upstream-commit: 50b78e97a50f952a08c221678f5df7b9bfafc059
Signed-off-by: kevinrizza <[email protected]> Upstream-repository: operator-registry Upstream-commit: 996010910c9ed57f7092fd2bc74e8506f6f4ace3
* Remove generated FakeAPIIntersectionReconciler. It's a test stub that has only one consumer. Generating a fake into pkg/fakes with counterfeiter and using it for tests in pkg/controller/operators/olm introduces a number of transitive package dependencies that make it difficult to unwind the resolver package from other runtime components. Signed-off-by: Ben Luddy <[email protected]> * Move OperatorGroup surface logic to the olm package. It has been living in the resolver package as a holdover from earlier generations of resolution, but is only consumed by olm-operator as part of OperatorGroup reconciliation. Signed-off-by: Ben Luddy <[email protected]> * Move API labeler from the resolver package to the olm package. The only user of the provided/required API labeling functionality is olm-operator, but it was still residing in the resolver package. Signed-off-by: Ben Luddy <[email protected]> * Remove OperatorSurface interface from resolver. This interface is used only by olm-operator and doesn't provide a useful abstraction on top of directly reading fields from Operator structs. Signed-off-by: Ben Luddy <[email protected]> * Extract SourceQuerier from the resolver package. SourceQuerier is a holdover from the previous resolution implementation. Now, it only gets minor usage in catalog-operator. Unused methods have been removed, and SourceQuerier has moved to pkg/controller/operators/catalog beside where it is used. Signed-off-by: Ben Luddy <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 9b537bf1079d55244c0cd733fc55d12d02c31574
Signed-off-by: kevinrizza <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: cf3b8a4ff857cd40092c8f21c70604abeb966332
The github.com/irifrance/gini package has been purged from github An existing version that preserved that history has been forked to the operator-framework org, and this commit updates that dependency to use the forked version. Signed-off-by: kevinrizza <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 51fe6da356c4e4658820031ffe0fe4117a2dcf59
Use mirrored base images as a temporary workaround for the docker.io rate limiting we are currently seeing in our builds Signed-off-by: kevinrizza <[email protected]> Upstream-repository: operator-registry Upstream-commit: d487288d9a2ee9b8d68009a10a0541133ee1090f
…ip-deps (openshift#753) Signed-off-by: Eric Stroczynski <[email protected]> Upstream-repository: operator-registry Upstream-commit: 7fba6adb47680d28632f83b8418b75889af5cb3d
…om other projects (openshift#759) Signed-off-by: Joe Lanford <[email protected]> Upstream-repository: operator-registry Upstream-commit: a0bb1e5b6d1ad34154fe205401dbd6ee6c4276bb
Signed-off-by: Josef Karasek <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 35deef283a7b0595d6213a66c395731fd0588cdd
new version has logic.C performance improvements that should help see: - go-air/gini#17 - go-air/gini@3a1a4d9 - go-air/gini@8dd6805 - go-air/gini#18 Signed-off-by: Evan <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: c20784d3e2a372c2a6a03dbcfedf512ca84b1eca
…shift#148) Upstream-repository: api Upstream-commit: e4b9266c693b1443c33fff99aabd49c07232e6ba
* Fix 2327 Signed-off-by: Ying Mo <[email protected]> * Remove -o=jsonpath='{.spec}' Signed-off-by: Ying Mo <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 03493b5e7178f3312f0220b0a2ee75db2b7c6459
- Change default base image scaffolded during `opm index` and `opm alpha generate dockerfile` to `quay.io/operator-framework/opm:latest` - update opm-example.Dockerfile to reflect this change (and to focus on file-based configs rather than sqlite databases) Signed-off-by: Joe Lanford <[email protected]> Upstream-repository: operator-registry Upstream-commit: 0a190a8a95abd690062816b4f5b0dc2143cddf1c
…images (openshift#771) Signed-off-by: Joe Lanford <[email protected]> Upstream-repository: operator-registry Upstream-commit: f5dcf40f01b8707194fdde07818c8b440ee010fa
/retest |
/retest |
2 similar comments
/retest |
/retest |
/retest |
/retest |
1 similar comment
/retest |
New changes are detected. LGTM label has been removed. |
374508d
to
15bce7b
Compare
/retest |
e14ef50
to
2aa7a1b
Compare
/retest |
Signed-off-by: timflannagan <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: e48737c5fc30c867d7f3ea3ce471c86050aa9a89
…#2370) Currently, OLM only caches configmap with olm-managed label to reduce memory usage footprint. There is an automatic mechanism to inject this label to all configmaps that belong to catalogsource. However, for e2e test, this label should be added by default to avoid extra logic to be executed. Signed-off-by: Vu Dinh <[email protected]> Signed-off-by: timflannagan <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 8b0ac13809b5155e4b7f1415e2fb37a060c3fe07
Update the root Makefile and extend the e2e/olm target to explicitly configure the ginkgo options that gets filtered to the staging/operator-lifecycle-manager e2e target that was introduced in [1]. [1] operator-framework/operator-lifecycle-manager#2367 Signed-off-by: timflannagan <[email protected]>
Update the root Makefile and update the `e2e` target to use the ginkgo executable instead of `go test ...` as logs produce when running the e2e suite aren't captured until after the process has completed. This leads to situations where failing tests aren't immediately communicated back and loss of logs entirely in the case where the process was manually teminated. Signed-off-by: timflannagan <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 584e12a9819b8aea1205332c4eba72a46d609fad
Signed-off-by: timflannagan <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 396b5461555c2498507b1fff20fccc3e7ae15420 Signed-off-by: timflannagan <[email protected]>
8b73eaf
to
d399345
Compare
/retest |
@ankitathomas: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
@ankitathomas: PR needs rebase. 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. |
Splitting into more granular commit ranges. See #203 for more details. |
Without operator-framework/operator-lifecycle-manager#2216