rukpak

rukpak copied to clipboard

TEST="xxxx" make test-e2e doesn't filter tests

6

```TEST="kustomize" make test-e2e``` It should run just 6 specs but it ran 77. ``` root@akuroda-0310:~/go/src/operator-framework/rukpak# TEST="kustomize" make test-e2e /root/go/src/operator-framework/rukpak/hack/tools/bin/ginkgo --tags upstream "" -trace -progress -v -focus "kustomize" test/e2e Running Suite:...

akihikokuroda

Move Reference printcolumn back to regular output

4

#276 moved the new Reference field out of the default output of `kubectl get bundles` behind the `-o wide` flag while the limitations associated with displaying the contents of the...

exdx

Support out-of-tree provisioner implementations

16

Rukpak currently supports multiple provisioner implementations that are all housed in-tree. The tooling and documentation are geared towards this design. Furthermore, all the packages involved in building a provisioner are...

exdx

Rearrange e2e tests with "provisioner x source type"

3

Every provisioner should work with any source type in theory. Most of the source types are tested with the plain provisioner now. So the plain_provisioner_test.go is growing. It's probably better...

akihikokuroda

Support syncing git-based sources

3

Most implementations of deploying a git repository inside a cluster have the ability to keep the repository up to date with changes to the remote. It makes sense to expand...

exdx

Should the rukpakctl executable be removed from the core container image

2

Currently, the rukpakctl executable is packaged with the runtime components for rukpak which inflates the total size of the container image. We can investigate removing it, and releasing it as...

timflannagan

Add PSA configuration for image unpacker

3

Creating an issue from the follow-ups outlined here: https://github.com/operator-framework/rukpak/pull/539#issuecomment-1233371230 ## Summary In [a recent merge](https://github.com/operator-framework/rukpak/pull/539) we introduced the initial approach for adding PSA compliance to RukPak resources. In this approach,...

tylerslaton

CRD validation: block CRD deletion if CRs are still present

6

In Rukpak, when a bundle deployment exists that has installed CRDs and the cluster has CRs for that CRD, there is nothing currently preventing or warning a user that deletion...

joelanford

Use non-default service account for unpacker pods

3

The unpacker pods are using the `default` service account in the provisioner namespace (rukpak-system). It is not good practice from security point of view.

akihikokuroda

(tylerslaton): Check CRDValidator safe storage logic

2

This test is currently trying to simulate a situtation where an incoming CRD removes a stored version. However, it does not work as expected because something (potentially the apiserver) is...

github-actions[bot]