Upstream sync #184

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 <timflannagan@gmail.com> 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 <bluddy@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 6ab5f1634093c91d7027b9245a88ede7b807088b

Signed-off-by: timflannagan <timflannagan@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 1e7e1cc81d5c3e0f2de2a06cb4315ea622371cbe

Update to containerd 1.4.8 Signed-off-by: Vu Dinh <vudinh@outlook.com> 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 <timflannagan@gmail.com> 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 <timflannagan@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 939bf94f834181d60a713191f78b13b80c7bec0f

Signed-off-by: Evan <cordell.evan@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 538b1315eace85e33df7b2893a85a000f8757349

Signed-off-by: Evan <cordell.evan@gmail.com> 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 <timflannagan@gmail.com> Upstream-repository: operator-registry Upstream-commit: 78f27b39dc098c2e56681d9a3d8e786aae95d4fe

Signed-off-by: Joe Lanford <joe.lanford@gmail.com> Upstream-repository: operator-registry Upstream-commit: a390f86b3ca429c9618a7c20a31406bc2bd6ed16

Signed-off-by: Ben Luddy <bluddy@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 3a565917233c72d098f3a60d9239f0e3c5b55f76

Signed-off-by: Daniel Messer <dmesser@redhat.com> 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 <timflannagan@gmail.com> Upstream-repository: operator-registry Upstream-commit: ff2c921e414926a013f82448b7241bc84fc95372

…penshift#734) Signed-off-by: Daniel Sover <dsover@redhat.com> 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 <ericstroczynski@gmail.com> Upstream-repository: operator-registry Upstream-commit: 6f1a54f7b7b4f5e4f062fde42cb477ae25d438f6

Signed-off-by: Daniel Messer <dmesser@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: c76e1cd8e24d555f59379f07faff538f6f5a4191

…t#750) Signed-off-by: Joe Lanford <joe.lanford@gmail.com> Upstream-repository: operator-registry Upstream-commit: 50b78e97a50f952a08c221678f5df7b9bfafc059

Signed-off-by: kevinrizza <krizza@redhat.com> 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 <bluddy@redhat.com> * 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 <bluddy@redhat.com> * 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 <bluddy@redhat.com> * 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 <bluddy@redhat.com> * 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 <bluddy@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 9b537bf1079d55244c0cd733fc55d12d02c31574

Signed-off-by: kevinrizza <krizza@redhat.com> 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 <krizza@redhat.com> 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 <krizza@redhat.com> Upstream-repository: operator-registry Upstream-commit: d487288d9a2ee9b8d68009a10a0541133ee1090f

…ip-deps (openshift#753) Signed-off-by: Eric Stroczynski <ericstroczynski@gmail.com> Upstream-repository: operator-registry Upstream-commit: 7fba6adb47680d28632f83b8418b75889af5cb3d

…om other projects (openshift#759) Signed-off-by: Joe Lanford <joe.lanford@gmail.com> Upstream-repository: operator-registry Upstream-commit: a0bb1e5b6d1ad34154fe205401dbd6ee6c4276bb

Signed-off-by: Josef Karasek <jkarasek@redhat.com> 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 <cordell.evan@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: c20784d3e2a372c2a6a03dbcfedf512ca84b1eca

…shift#148) Upstream-repository: api Upstream-commit: e4b9266c693b1443c33fff99aabd49c07232e6ba

* Fix 2327 Signed-off-by: Ying Mo <morningspace@yahoo.com> * Remove -o=jsonpath='{.spec}' Signed-off-by: Ying Mo <morningspace@yahoo.com> 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 <joe.lanford@gmail.com> Upstream-repository: operator-registry Upstream-commit: 0a190a8a95abd690062816b4f5b0dc2143cddf1c

…images (openshift#771) Signed-off-by: Joe Lanford <joe.lanford@gmail.com> Upstream-repository: operator-registry Upstream-commit: f5dcf40f01b8707194fdde07818c8b440ee010fa

…cle-manager. (#2337) * Remove resolver dependency on registry.CatalogKey. Signed-off-by: Ben Luddy <bluddy@redhat.com> * Remove hard resolver dependency on the gRPC registry client. The most significant change is the introduction of a new Source interface, which represents a single source of cache entries. In the existing implementation, the cache was hardcoded to fetch content from the operator-registry gRPC API on misses. This was a barrier to off-cluster tools and other applications that should be able to perform resolution without running a registry server. A number of test fixtures were affected (for the better) because it's now possible to directly configure the real Cache implementation to retrieve test content without using of test doubles. Signed-off-by: Ben Luddy <bluddy@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 9e4a778a44abb8705fb8ef95ad0bdaaebfa0ecfc

…338) Update the root go.mod and remove the replace pin for sigs.k8s.io/structured-merge-diff. It looks like the "// pinned because no tag supports 1.18 yet" message may have also been an artifact of removing the helm replace pin that was previously in place. Signed-off-by: timflannagan <timflannagan@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 3eb0d7be413d7c185441cb3fc81dadb2b67706e7

* add timestamp field Signed-off-by: Ish Shah <ishah@redhat.com> * Add timestamp to scorecard test result Signed-off-by: Ish Shah <ishah@redhat.com> * Change type and struct Signed-off-by: Ish Shah <ishah@redhat.com> * Update pkg/apis/scorecard/v1alpha3/test_types.go Co-authored-by: Joe Lanford <joe.lanford@gmail.com> * make manifests/generate; Signed-off-by: Ish Shah <ishah@redhat.com> * Update pkg/apis/scorecard/v1alpha3/test_types.go Co-authored-by: Joe Lanford <joe.lanford@gmail.com> Co-authored-by: Joe Lanford <joe.lanford@gmail.com> Upstream-repository: api Upstream-commit: 7d591fff8bd551160e51dedef17debbe52145019

* Add validation for Kind and APIVersion Signed-off-by: Josef Karasek <jkarasek@redhat.com> * Update pkg/validation/internal/csv.go Co-authored-by: Eric Stroczynski <ericstroczynski@gmail.com> Co-authored-by: Eric Stroczynski <ericstroczynski@gmail.com> Upstream-repository: api Upstream-commit: c9b1e7ef82b8081a3eb52c48d0ca9039f2e3a27e

Signed-off-by: Josef Karasek <jkarasek@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: de4bebe06ba076f804d28c594d7dc52dfd95ef20

…r packages. (#2340) * Stop using the registry's Bundle proto type for resolution. The resolver component does not care whether a given cache entry was populated by use of the registry gRPC API, so it should ultimately be possible to drop the "Bundle" field from cache entries altogether. For now, catalog-operator's "step resolver" still depends on a Bundle proto field in order to unpack inline (as opposed to image-based) packages. Signed-off-by: Ben Luddy <bluddy@redhat.com> * Remove exported resolver cache entry creation funcs. NewOperatorForBundle and NewOperatorFromV1Alpha1CSV couple the resolver cache package to the registry gRPC API and the operators/v1alpha1 CSV API, respectively. They're effectively used only by the resolver package, so they can be moved there and unexported. The remaining calls to NewOperatorFromV1Alpha1CSV can be extracted from core resolver logic into a Source implementation that is responsible for the conversion from ClusterServiceVersion to cache.Snapshot entry, and the remaining call to NewOperatorFromBundle is used only by the Source implementation based on the registry gRPC API. Signed-off-by: Ben Luddy <bluddy@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: b849eb79c6fbb1c445ed3e9945e1668f6066ea6e

…ift#154) * modified the controller-runtime and controller-tools versions * ran vendor command and added files * ran make manifests Upstream-repository: api Upstream-commit: a80624eab36b2005fa5d84c9b539bb4817e44daa

* .github/workflows: Separate out the e2e jobs into workflows Update the .github/workflows/test-scripts.yml GH action workflow and move all the jobs listed there into separate workflows. This allows us to retest a single workflow at a time as a workaround to GH not allowing you to retest individual jobs in a workflow. Signed-off-by: timflannagan <timflannagan@gmail.com> * .github/workflows: Add the 'ci' workflow name to all e2e-related jobs Signed-off-by: timflannagan <timflannagan@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 966ce43d5bde93848c45e1aaf4c6a5c110c37740

Add a badge that links to the olm-dev channel in the Kubernetes Slack instance. Signed-off-by: Nick Hale <njohnhale@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 94af95a7580f45f6a0b45bd12d5aa37649b74a47

Signed-off-by: timflannagan <timflannagan@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 864b58ddc63742b53ecdf21f463e13ac2ce9de7e

…file (openshift#773) Signed-off-by: Eric Stroczynski <ericstroczynski@gmail.com> Upstream-repository: operator-registry Upstream-commit: 1c8557637731bbe28166d854ea8a16fd86c2995e

* .github/workflows: Don't run CI checks for markdown-only updates Update the ci-prefixed workflows and ensure that CI isn't running when only markdown files are updated. Signed-off-by: timflannagan <timflannagan@gmail.com> * .github/workflows: Use paths-ignore instead of paths for ignoring certain files/paths Signed-off-by: timflannagan <timflannagan@gmail.com> * .github/workflows: Remove the need to ignore the root doc/ path The '**/*.md' filter pattern [1] should ignore _all_ markdown extension files anywhere in the repository. [1] https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#patterns-to-match-file-paths Signed-off-by: timflannagan <timflannagan@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 2fd014019ca8cc86ae859da797e814b72c299257

Signed-off-by: Eric Stroczynski <ericstroczynski@gmail.com> Upstream-repository: operator-registry Upstream-commit: a3253eb2fa97be52883af0a0c195d4a95500c04a

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Upstream sync #184

Upstream sync #184

Commits on Sep 9, 2021