For reference this was the continuous deliver radar done a while back by the CNCF:https://radar.cncf.io/2020-06-continuous-delivery From: <cncf-sig-app-delivery@...> on behalf of "Lei Zhang via

Thanks Alois! The "podtato" is super awesome! Btw, based on today's discussion, the SIG app delivery is also thinking for CNCF Radar for application delivery and management. This should be a

Hello everyone, Just a quick update on today’s meeting: Demo Application. I created a first version codename podTato Head. You can find it

Hello everyone, Please add any agenda items for today’s meeting. I will provide an update on the app delivery demo project

I am using this list as it most likely reaches the widest audience in the CNCF. In recent discussions in the app delivery SIG we came to the conclusion that a reference application would make

Sounds good.

Alexis, As always this makes a lot of sense. Ideally, we can get somebody to donate as we will need active contributions and not just a “dead” fork. I will push the conversation to the TOC

That is great input. The use cases are collected here:https://docs.google.com/document/d/1ouCZ39Qoa7y7cykyK8dk4Y2mR8xFsWYQ2asZWYA_BOo/edit#heading=h.g4biroxrc9rm Currently we only have Cray in

I may be able to help with the airgap stuff. Where do you want that info put? Biggest challenge we have with is figuring out what images are used, modifying operator bundles/helm charts to use our

can I put out a call for sockshop, hipster shop, rocket shop and whatever else to be copied over to a CNCF GH org "demo apps" or something?

Hello everyone, I want to provide an update on our last call in a fast and easy-to-read way. Operator Definition We are getting back to the document again Working on overall clean-up of the

Hello! In yesterday's SIG Meeting we discussed about how to proceed with the Operator WG and found out that it would be useful to find out what the goal of the document is, but also to clean up the

VOTE: https://doodle.com/poll/7iek4zbgqm9zr388 Our current meeting time is on Friday's during an non-ideal time. We've seen a large reduction in attendance as we've moved into summer. So we've decided

Thanks Omer. How about: "An Operator is a subset of Controllers that provides an application or domain-specific knowledge to install or “operate” an application, using one or more CRDs". Regarding

Confirmed with Harry that there is room on the agenda for June 3rd, so I have added Crossplane Sandbox presentation to the agenda for that day. See you all there, should be a great

I'd certainly not limit to a single CRD. There are several existing operators that use multiple CRDs. There are also things people have built that don't use a CRD, but perhaps that should be

Hi, In the last WG meeting (27.5), we were only three people, and we felt that this is not enough people for a vote. Instead, we want to try to use the mailing list to get more opinions, and maybe

Hey there SIG-App-Delivery, I would love to get on the upcoming agenda/schedule to present a sandbox proposal for the Crossplane project. A PR to the TOC repo that has all the details should be opened

Hello everyone, In today’s call we discussed how to move the “app delivery landscape” forward. We have the great initial document [1] Harry wrote quite a while back. Discussing the doc

About 2, I think that there would be components that we know called controllers that would have to change there name to an operator. The deployment controller is a good example: - It extends the