---
# System prepended metadata

title: Kadalu.IO Community Conversations

---

# Kadalu.IO Community Conversations


---


### Community Calendar - 

https://bit.ly/KadaluIOCommunityCalendar (please subscribe for event updates)

### Meeting of 30 June 2020

**Joining Info**

Join Zoom Meeting
https://us02web.zoom.us/j/86023414326?pwd=azBaa2FxVU5aMENLNEtoV25kTWZOdz09

Meeting ID: 860 2341 4326
Password: 864586

Meeting recording - https://us02web.zoom.us/rec/share/wZFlcOjLxEpJWYnv0FHCc6UIMrq6eaa80ygdq_Fbykot-AsXmkJVPU9crlJ1E7mh?startTime=1593528421000

### Participants
(*Please put in Name - Slack username - Affiliation [optional]*)

* Amar - amar - Kadalu.IO
* Aravinda - aravinda - Kadalu.IO
* Joe Julian - [D2iQ](https://d2iq.com/)
* John Strunk - Red Hat
* Billy O'Connell - 
* Sachidananda - 
* sankarshan - sankarshan

### Agenda

* [Aravinda & Amar] Update to the community about upcoming plans
* Seeking feedback on Kadalu.IO releases
    * Helm charts are important; the post install parts of a k8s cluster (logging, monitoring etc) are important to have in place. Helm charts allow the creation of an opinionated approach.
    * ARM support is important - there are existing clusters which require ARM builds
    * Upgrades - important to focus on ensuring that these are automated and nicely complete. Solid upgrade path gets a rock solid cluster with backup/restore coming up
    * Backup/restore allows you to handle the risks if something goes wrong. Enabling to go back to a point in time.
    * Stability - sometimes Gluster is not as stable as it is expected
    * k8s updates are structured around the notion of a rolling upgrade and be able to roll back. It is easier in the world of stateless.
* Other Business

---

### Meeting of 16 June 2020

**Meeting Time Converter :** [1415 IST (UTC+0530)](bit.ly/KadaluCommunityMeeting)

**Joining Info** 	

* Join with [Google Meet](https://meet.google.com/jmv-zxnv-qmn)				
* Join by phone 	+1 631-621-7145 (PIN: 398638454)
* [More phone numbers](https://meet.google.com/tel/jmv-zxnv-qmn?pin=8855917099769&hs=0) 

### Participants

(*Please put in Name - Slack username - Affiliation [optional]*)

* Amar - amar - Kadalu.IO
* Aravinda - aravinda - Kadalu.IO
* Sachidananda - sac - Kadalu.IO
* Adrian (Papanito)
* sankarshan 

### Agenda

* [Aravinda & Amar] Update to the community about upcoming plans (link to deck when available)
* Seeking feedback on Kadalu.IO releases around stability, performance and sizing
    * Storage delete handling (often run into problems where we run out of disk space)
    * PV delete issue will be fixed in the upcoming release; storage pool deletion in the backend
    * Performant solution for the enterprise
    * Backup and Restore support
    * Logging related topics have been observed recently by Adrian. Heavy logging could be a problem when systems such as a Splunk are being used (data volume economics).
    * General positive feedback - simple and good working solution.
    * Current state of documentation is sufficient. Kadalu.IO is straight forward to use. To troubleshoot quickly the documentation needs to be built for that.
* Other Business