rukpak

rukpak copied to clipboard

Add provisioner visibility API

8

See https://github.com/operator-framework/rukpak/pull/447#issuecomment-1191935915 for discussion and background. There may be a need for a new first-class API to reflect which rukpak provisioners are installed on-cluster and currently running, to make it...

exdx

refactor NewDefaultUnpacker due to growing parameter list

2

https://github.com/operator-framework/rukpak/blob/3b832db489499105211cda18f2217aad89e2bb8f/internal/source/unpacker.go#L103 ```golang // NewDefaultUnpacker returns a new composite Source that unpacks bundles using // a default source mapping with built-in implementations of all of the supported // source types. //...

github-actions[bot]

Remove shell from RukPak image

1

## User Story As a user of RukPak, I would like to have the most minimal image without an attached shell, So that I know the application is following best...

tylerslaton

Implement support for plain bundle metadata

3

Based off #178, there is an exploratory design for a minimal set of metadata plain bundles can expose. This issue involves implementing the handling of the metadata on the provisioner...

exdx

Improve the UX for Bundles that reference a non-existent unique provisioner ID

2

Summary: Bundles that reference an invalid, or a non-existent unique provisioner ID result in the Bundle resource not being reconciled by any of the provisioner(s) installed on-cluster, and there aren't...

timflannagan

Support transforming registry+v1 bundles to plain k8s bundles

6

The current operator ecosystem is built around the registry+v1 operator bundle format (which includes details like always including a CSV manifest under `/manifests`, bundle properties, additional installation information in the...

exdx

Packaging and lifecycling APIs and controllers separately

3

Recently, more and more [use cases](https://hackmd.io/xXkT1TZJREG-AscBxqnQHQ?view) have arisen where rukpak having an explicit de-coupling between APIs and controllers would be beneficial. What do folks think about this idea? What (if...

joelanford

Revisit whether the rukpakv1alpha1.HasValidBundle BI status condition should be removed

3

Follow-up to #293 which added support for dynamically created Bundles through the BI API. Goal: consolidate the Bundle's Unpacked phase with the BI's HasValidBundle status condition type.

timflannagan

Provisioner developer documentation for fallback loader

1

Need to add documentation that explains the fallback loader and its motivation for existing.

tylerslaton

Add documentation for provisioner developers

1

Add some documentation on how to write your own provisioner, to support alternate provisioner implementations. Part of #425

exdx