I presume OLM is Operator Lifecycle Manager? https://github.com/operator-framework/operator-lifecycle-manager This sounds like OperatorHub requires Operators to use OLM? Are there any examples, or

Agree with that Jay. The connection comes more from the OLM side since this is where the metadata format is defined that drives the OperatorHub.io index.-- Daniel Messer He / Him / His Product

I agree that tying the Operator SDK and Operator Hub together is counterproductive. Is there a reason why they cannot be separated? In my mind, *how* a k8s application is built (Operator SDK) is

Hi, there were a bunch of questions in the last SIG call in regards to Operators that did not get answered - I am running through the ones from the chat log below. Feel free to chime in, if there was

Agreed. That's not the issue I'm flagging. My issue is forcing that decision on a user up-front, before they pick the workload. Irrespective of the implementation detail, the end user wants to run

There are lots of Operators that are not written with the SDK there. Every Operator on OperatorHub.io however is packaged for OLM to enable the visual display, versioning and install

Are there any examples of non-operator-framework operators on Operator Hub today? Thanks for the answers. I think it's fine for producers of applications to appreciate those technical different

Hi Gareth, sorry for the late reply - responding inline. Thanks for the questions - keep them coming! I think this definition is still valid. An Operator is a custom controller with its own CRDs

+1

Hi all! During a recent meeting, people proposed to move the app delivery meeting to the 1st and 3rd week of the month. Currently there is a lot of overlap with other meetings and people have

Thanks for the presentation, I had a few questions and thought I'd kick things off here. 1. Compatibility Terminology wise, checking this is still the canonical definition from a concept point of

Hi Sig App Delivery The Chairs of the Sig App Delivery have to postpone several presenting projects to next next meeting as there're 6 projects listed in the meeting notes agenda for next meeting

https://github.com/cncf/sig-app-delivery/issues is the issue queue for this SIG, that's probably a good next step to open an issue there for discussion. -- Amye Scavarda Perrin | Program Manager,

Got it, thanks! <alois.reitbauer@...> wrote:

You can find the agenda here: https://docs.google.com/document/d/1OykvqvhSG4AxEdmDMXilrupsX2n1qCSJUWwTc3I7AOs/edit#heading=h.r6tiyo9ld7hy We will finalize the details tomorrow. Can you please also

Hi all! We presented to the TOC in September about KUDO. It was suggested then that there would be further steps with SIG App Delivery - at the time the SIG was just forming and getting it's feet wet.

hi all, where is the agenda posted? if it is not posted, what is it?

Hello SIG-Apps! I would like to request to present the operator framework on Wednesday. https://github.com/cncf/toc/pull/303 Please let us know if there is time on the agenda. Thanks, Erin --

I agree, app packaging and distribution are indeed on the critical path of app delivery. The idea of layer 1.5 seems reasonable, i.e. it closely related to layer 1 rather than a independent layer. Lei

As Bryan suggested today, a lot going on in Zoom call so taking things to the mailing list. I brought this up in the comments. I think that there is a part of the dictionary diagram that is missing