Thanks Quinton and Alex! This is very helpful. Based on that, it seems to me like the responsibilities for this SIG are essentially to collect and disseminate storage related information in a

Love that you are volunteering, Saad. You've done a wonderful job with the Kube Storage-SIG and I can speak from person experience that we have a healthy, professional, productive group. :) Erin

I understand that any project can choose to apply or not apply to be part of the CNCF Sandbox. And while I realize the intent may not be to attempt to promote one project above another, per the CNCF

How does this relate to the established precedent of having multiple implementations of container runtimes be under the umbrella? (containerd, rkt, cri-o) Thanks, Kevin

Hi Saad Thanks for your questions. Answers inline below.

Hi CNCF Storage WG, Based on recent presentation and discussions in the CNCF Storage WG meeting, I understand that we are considering adopting OpenEBS as a new CNCF sandbox or incubator project? Is

Hi Saad Speaking personally, it would be great to have you as a TL on the CNCF Storage SIG. Regarding your other questions around SIG scope, have you read this

Hi CNCF Storage WG, Following up on the CNCF Storage WG meeting this morning: I'm considering throwing my hat in to the ring as a possible TL for the proposed CNCF Storage SIG. I'm currently

Hi Saad, Thanks for throwing your hat into the ring ! :-) (apologies for the long email, but the info will hopefully benefit the rest of the mailing list too) The CNCF SIGs are being setup

David Thanks. I would prioritise open governance over reducing your committers, but up to you. Re quotas. Any multi-tenant system that holds data for any length of time faces the question of how

Hi, Thank you for your comments and the opportunity to present Strimzi to the TOC yesterday. We are keen to work towards neutral open governance of the project and think that the link to the Cortex

Keycloak does indeed have built-in support for MFA, but it is currently limited to one-time passwords (HOTP or TOTP). It is possible to extend Keycloak to add additional custom MFA mechanisms and we

As this may come up I wanted to clarify the relationship between Keycloak and RH-SSO. Keycloak is the community project and is freely available for anyone to use. RH-SSO is built directly from

Actually, domain-mode is not relevant. Domain-mode is a feature of WildFly that allows creating and managing a group of servers, but this is not relevant in Kubernetes since it already has this

Greetings, Sorry I could not make the call today, but I did want to raise some concerns I have had over Keycloak. One is the fact that, at heart, it is still a login/password system. There is some

Thanks for the presentation. Very informative. The questions I (and Joe) had around HA and scalability are at least partially answered in the installation

I am a potential sponsor. for me to buy in: I'd like to see a neutral gov & roadmap plus plans from david on achieving unambiguous neutrality, plus thoughts on what would be useful as a 'spun out'

Hey all, we heard from the Strimzi project today: https://github.com/cncf/toc/issues/138 There were questions about if the ZK aspects of the operator could be pulled out as its own project. There

There is nothing RHT enterprise specific and it is backed fully by proven upstream technologies with active communities. Regarding clustering and concerns expressed in the chat there is a way to

The Keycloak project presented today: https://github.com/cncf/toc/pull/176 The TOC, especially Joe had some questions on how Keycloak was deployed on Wildfly (vs the RHT enterprise version of that).