rukpak
rukpak copied to clipboard
RukPak runs in a Kubernetes cluster and defines APIs for installing cloud native content
Currently, we specify rukpak controller to have admin level permissions: https://github.com/operator-framework/rukpak/blob/1d284f91a3dfba176c1ff9e728e705681e885a25/internal/controllers/bundledeployment/bundledeployment.go#L162 This seems to be required to be able to manage the lifecycle of bundle resources effectively. This issue is...
In order to test against the same kubernetes cluster version that our dependencies align with, we should update `kind` and additionally update our `Makefile` configuration to derive a `kind` image...
There are Kustomize patches specified in the project which provide options to introduce additional validations in the CRD like: https://github.com/operator-framework/rukpak/tree/main/manifests/base/apis/crds/patches. If any changes are made to these files, `kustomize build`...
RukPak is currently a few minor versions behind on both our k8s and controller-runtime dependencies. Upgrading these dependencies will introduce a number of breaking api changes, it would be nice...
At present, rukpak exclusively supports SSH-based authentication, as indicated in the code here: https://github.com/operator-framework/rukpak/blob/05f3afd8eb38849c830fdcc213e44c4ce0065cd4/api/v1alpha1/bundle_types.go#L134. However, this limitation may prove restrictive, particularly for scenarios that require Git-based authentication. Expanding rukpak's capabilities...
The existing [CONTRIBUTING.md document](https://github.com/operator-framework/rukpak/blob/51ddc9f4ae273fb294f5ee2b6396f0994f6be9b5/CONTRIBUTING.md) has a few gaps that should be addressed in order to provide new users in the community with a better onboarding experience. Specifically, I would like...
This issue is to mimic the behaviour of OLM v0 in OCP. In OLM v0, admins can override the proxy settings for an operator inherited from cluster through "Subscription" API....
We currently indirectly depend on https://github.com/cloudflare/circl, which complicates ensuring FIPS compliance because it is outside of standard go crypto. We need to remove all custom crypto dependencies. ``` go mod...