├── DISCLAIMER.md ├── README.md ├── cloud-drove-logo.jpg ├── kubezilla500.png ├── logo__on-white.svg └── sponsorship.md /DISCLAIMER.md: -------------------------------------------------------------------------------- 1 | 2 | ## Security Disclaimer: 3 | 4 | Participating in the project to build the largest Kubernetes Community Cluster entails certain risks and considerations. While we strive to create a safe and secure environment, it's important to be aware of potential security implications. Please carefully review and understand the following: 5 | 6 | - Data Privacy: By participating in this project, you may be working with sensitive or confidential information. Take utmost care to handle and store data securely. Avoid sharing sensitive information in public forums or channels, and follow applicable data protection regulations and organizational policies. 7 | 8 | - Access Controls: Ensure that appropriate access controls are in place to protect the Kubernetes cluster and associated resources. Use strong authentication methods, enforce least privilege principles, and regularly review and update access permissions. Limit access to authorized individuals and closely monitor cluster activity for any unauthorized access attempts. 9 | 10 | - Network Security: When setting up the Kubernetes cluster, pay careful attention to network security. Follow best practices for securing network communications, such as using encrypted connections, implementing network policies, and restricting external access to the cluster's control plane. Regularly review and update network security measures to address potential vulnerabilities. 11 | 12 | - Container Security: Containers running on the Kubernetes cluster should be built with security in mind. Ensure that container images are sourced from trusted repositories, regularly update containers with security patches, and employ security scanning tools to detect vulnerabilities. Follow container best practices to minimize the risk of container escape or privilege escalation. 13 | 14 | - Monitoring and Logging: Implement robust monitoring and logging mechanisms to detect and respond to potential security incidents. Set up logging of cluster events, monitor system and application logs, and establish alerts for suspicious activities or anomalies. Regularly review and analyze logs to identify and address security issues. 15 | 16 | - Regular Updates and Patching: Keep the Kubernetes cluster and associated components up to date with the latest security patches and updates. Stay informed about security advisories and vulnerability disclosures related to Kubernetes and promptly apply necessary patches to mitigate potential risks. 17 | 18 | - Third-Party Tools and Integrations: Be cautious when using third-party tools or integrations within the Kubernetes cluster. Review their security practices, ensure they are from trusted sources, and follow the recommended security guidelines provided by the respective vendors. 19 | 20 | - Continued Learning: Stay informed about security best practices, emerging threats, and industry trends related to Kubernetes and containerization. Regularly educate yourself and the community about security considerations, share knowledge, and foster a culture of security awareness. 21 | 22 | By participating in this project, you acknowledge and accept that the security of the Kubernetes Community Cluster is a shared responsibility. Exercise due diligence, adhere to security best practices, and promptly report any identified vulnerabilities or security concerns to the project organizers. 23 | 24 | 25 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Kubezilla500 - Building the largest Kubernetes Community Cluster 2 | 3 | 4 |
5 | Logo 6 |
7 | 8 | Kubezilla is an ambitious project that aims to provide community members with an immersive learning experience in Kubernetes and related technologies. By building the largest Kubernetes Community Cluster, we aim to demonstrate the scalability and power of Kubernetes, while fostering collaboration and knowledge sharing within the community.We are aiming to build a largest Kubernetes Community Cluster and target to showcase it during Docker Bangalore Meetup event. 9 | 10 | Ensure that you [read the security disclaimer](https://github.com/collabnix/kubezilla500/blob/main/DISCLAIMER.md) before you participate for KubeZilla effort 11 | 12 | 13 | ## Sponsorship Acknowledgment 14 | 15 | 16 | 17 |
18 | Logo 19 |
20 | 21 |
22 | Logo 23 |
24 | 25 |
26 | 27 | 28 | We would like to extend our deepest gratitude to [Vultr](https://vultr.com) and [Cloud Drove](https://clouddrove.com) for their generous sponsorship towards the setup of our Kubernetes Cluster. Their support has been instrumental in enabling us to create a robust and scalable infrastructure to power our Kubezilla community cluster. 29 | 30 | 31 | 32 | 33 | ## Why are we doing this? 34 | 35 | It's great opportunity for community members to learn, collaborate and contribute around Kubernetes and related technologies. As a team, we will learn how Kubernetes cluster is setup, how apps gets deployed over Cloud and what kind of microservices can be run possibly on these HUGE cluster nodes.Community members will learn how monitoring tools like Prometheus and Grafana can be deployed and fetch time-series metrics out of these HUGE cluster of nodes. In nutshell, it's a 1 day effort which will let every single individual to learn Kubernetes and understand its scalability. 36 | 37 | ## Sponsorship Opportunities 38 | 39 | - [Click here](https://github.com/collabnix/kubezilla500/blob/main/sponsorship.md) 40 | 41 | ## How it works? 42 | 43 | We invite contributors to help us build the largest Kubernetes Community Cluster by providing their FREE cloud instances or Raspberry Pi devices. Your contribution will help showcase the scalability and power of Kubernetes during the Docker Bangalore Meetup event. 44 | 45 | ## How to add my node? 46 | 47 | You need to run the following Docker command to join your worker nodes: 48 | 49 | ## For Cloud Instance [Ubuntu 20.04 LTS] 50 | 51 | ``` 52 | sudo docker run -d --privileged --restart=unless-stopped --net=host -v /etc/kubernetes:/etc/kubernetes -v /var/run:/var/run rancher/rancher-agent:v2.4.18 --server https://kubezilla.collabnix.com --token wlcj8nwx8ns92n69qbnk9f4kkmc7jkswcbgzpsm9hc4k6dxwjxdm8c --worker --label node=cloud --label name=kubezilla 53 | ``` 54 | 55 | ## For adding Laptop [Ubuntu 20.04 LTS] 56 | 57 | ``` 58 | sudo docker run -d --privileged --restart=unless-stopped --net=host -v /etc/kubernetes:/etc/kubernetes -v /var/run:/var/run rancher/rancher-agent:v2.4.18 --server https://kubezilla.collabnix.com --token wlcj8nwx8ns92n69qbnk9f4kkmc7jkswcbgzpsm9hc4k6dxwjxdm8c --worker --label node=laptop --label name=kubezilla 59 | ``` 60 | 61 | ## For adding Docker Desktop 62 | 63 | ``` 64 | sudo docker run -d --privileged --restart=unless-stopped --net=host -v /etc/kubernetes:/etc/kubernetes -v /var/run:/var/run rancher/rancher-agent:v2.4.18 --server https://kubezilla.collabnix.com --token wlcj8nwx8ns92n69qbnk9f4kkmc7jkswcbgzpsm9hc4k6dxwjxdm8c --worker --label node=dd --label name=kubezilla 65 | ``` 66 | 67 | ## For PWD 68 | 69 | We suggest you to add only one instance per session so that there is not much pressure on the overall platform 70 | 71 | ``` 72 | sudo docker run -d --privileged --restart=unless-stopped --net=host -v /etc/kubernetes:/etc/kubernetes -v /var/run:/var/run rancher/rancher-agent:v2.4.18 --server https://kubezilla.collabnix.com --token wlcj8nwx8ns92n69qbnk9f4kkmc7jkswcbgzpsm9hc4k6dxwjxdm8c --worker --label node=pwd --label name=kubezilla 73 | ``` 74 | 75 | ## For PWK 76 | 77 | We suggest you to add only one instance per session so that there is not much pressure on the overall platform 78 | 79 | ``` 80 | sudo docker run -d --privileged --restart=unless-stopped --net=host -v /etc/kubernetes:/etc/kubernetes -v /var/run:/var/run rancher/rancher-agent:v2.4.18 --server https://kubezilla.collabnix.com --token wlcj8nwx8ns92n69qbnk9f4kkmc7jkswcbgzpsm9hc4k6dxwjxdm8c --worker --label node=pwk --label name=kubezilla 81 | ``` 82 | 83 | ## For RaspberryPi/Jetson Nano 84 | 85 | 86 | ``` 87 | sudo docker run -d --privileged --restart=unless-stopped --net=host -v /etc/kubernetes:/etc/kubernetes -v /var/run:/var/run rancher/rancher-agent:v2.4.18 --server https://kubezilla.collabnix.com --token wlcj8nwx8ns92n69qbnk9f4kkmc7jkswcbgzpsm9hc4k6dxwjxdm8c --worker --label node=iot --label name=kubezilla 88 | ``` 89 | 90 | **Node Specification:** XGB of RAM with X vCore. Please note that 512MB will not be enough for our testing requirements. 91 | 92 | **Contribution Options:** 93 | 94 | 1. **Cloud Instance:** If you have a FREE cloud instance from AWS, Azure, GCP, or DigitalOcean, you can contribute it to our community cluster. By connecting your cloud instance to our cluster, you'll be part of this exciting initiative. 95 | 96 | 2. **Raspberry Pi:** If you are familiar with connecting Raspberry Pi devices to a Kubernetes cluster, you can contribute your Raspberry Pi to our cluster. Your expertise will be invaluable in expanding the reach of our community project. 97 | 98 | **How to Contribute:** 99 | 100 | 1. Fork this repository to your GitHub account. 101 | 2. Create a new branch with a descriptive name. 102 | 3. Add your cloud instance or Raspberry Pi contribution to the respective section in the README. 103 | 4. Submit a pull request to merge your changes into the main repository. 104 | 105 | **Contribution Guidelines:** 106 | 107 | - Please provide the specifications of your cloud instance or Raspberry Pi, including the RAM and vCore details. 108 | - Include your full name, Twitter handle, and company name in the pull request description. 109 | - Ensure that your contribution meets the node specification mentioned above. 110 | 111 | We appreciate your support and contributions to make this project a success. Let's showcase the capabilities of Kubernetes together! 112 | 113 | For any questions or assistance, please feel free to reach out to us. Thank you! 114 | 115 | 116 | 117 | ## When? 118 | 119 | > We are targeting 8th July starting 9:00 AM till 5:00 PM for Kubezilla. 120 | 121 | | Activity | Date | Time | 122 | | :-------: | :------------: | :----------------: | 123 | | Rehearsal | 5th July 2023 | 11:00 AM to 1:00 PM | 124 | | Live | 8th Jul 2023 | 9:00 AM to 4:00 PM | 125 | 126 | 127 | ## Contributors 128 | 129 | 130 | | S. No | Name | Company | Node Type | Node Count | 131 | | ---| ---------------------------|------------------------------|-----------------|------------| 132 | | 1| Ajeet Singh Raina | Docker | Cloud | 10+ | 133 | | 2 |Anmol Nagpal | Cloud Drove | Cloud | 50 | 134 | | 3 |Kasibhatla Avinash | Dexra solutions | Laptop | 5+ | 135 | | 4 |shubhendu | TCS | Cloud Instance | 1 | 136 | | 5 |Krishna Hrithik | Opentext | Laptop | 1 | 137 | | 6 |Sivakumar M | Standard Chartered Bank | Cloud Instance | 5+ | 138 | | 7 |Raji reddy K | Progressive | Laptop | 1 | 139 | | 8 |Sujit Neb | BMC Software | Laptop | 1 | 140 | | 9 |shubha banerjee | hdfc bank | Laptop | 1 | 141 | | 10 |OMID | Asan pardakht | Bare Metal | 10+ | 142 | | 11 |Varun Bhatia | | Laptop | 1 | 143 | | 12 | Sridhar keshab Senapati | Searce | Cloud Instance | 5+ | 144 | | 13 |Aniket Banerjee | Infosys | Cloud Instance | 5+ | 145 | | 14 | Gabriel Martins | ACM | Cloud Instance | 5+ | 146 | | 15 | Rohit Ghumare | Solo | Laptop | 10+ | 147 | | 16 | Kamlesh Rao | SPHood | Laptop | 10+ | 148 | | 17 | Aravindhan Anandhavel | Global Magnit | Laptop | 1 | 149 | | 18 | Neetu Mallan | EZOps Technologies | Laptop | 5+ | 150 | | 19 | Lal Krishna | Stickybit Technologies | Bare Metal | 5+ | 151 | | 20 | Rutwik Kinagi | Infosys Limited | Laptop | 5+ | 152 | | 21 | Yashvi Kothari | NA | Cloud Instance | 1 | 153 | | 22 | Gaganpreet Singh | VMware | Cloud Instance | 1 | 154 | | 23 | Harsha Vardhan | | Cloud Instance | 1 | 155 | | 24 | Sanaz Baniasadi | | Cloud Instance | 50+ | 156 | | 25 | Rajendra G | Self | Laptop | 1 | 157 | | 26 | Raseel Bhagat | Zymr | Cloud Instance | 5+ | 158 | | 27 | Unni P | Self | Laptop | 5+ | 159 | | 28 | Sangam Biradar | Deepfence | Cloud Instance | 10+ | 160 | | 29 | Geno Thomas | IBM | Cloud Instance | 3 | 161 | | 30 | Karan Singh | Scogo | Bare Metal | 1 | 162 | | 31 | Sajid Ali | IMS | Cloud Instance | 1 | 163 | | 32 | Saurav Kaveri | Self | Cloud Instance | 1 | 164 | | 33 | Marvellous Ezemba | Self | Cloud Instance | 1 | 165 | | 34 | Raseel Bhagat | Zymer | Cloud Instance | 5+ | 166 | | 35 | Zachary Gonzales | Zargo | Laptop | 1 | 167 | | 36 | Vijay Reddy | Self | Laptop | 1 | 168 | | 37 | Vignesh k | Blackstraw | Laptop | 1 | 169 | | 38 | haruna rashid | worketyamo | Laptop | 1 | 170 | | 39 | Varun Gopal | Oracle | Laptop | 1 | 171 | | 40 | Samuel Bartels |Self | Cloud Instance | 5+ | 172 | | 41 | Ajay | TCS | Laptop | 50+ | 173 | | 42 | Ashutosh Mahajan | Cloud Drove | Laptop | 1 | 174 | | 43 | Dewan Shakil Akhtar | Scogo | Laptop | 1 | 175 | | 44 | Dipal parmar | Spekit | Laptop | 1 | 176 | | 45 | Swaroop Chirayinkil | Interplai | Cloud Instance | 1 | 177 | | 46 | Sujay Pillai | Self | Cloud Instance | 5 | 178 | | | | Total | | 302 | 179 | 180 | 181 | 182 | ## What's mininum requirements of a node? 183 | 184 | Nodes can either be physical, virtual, IoT or Desktop system. 185 | 186 | 187 | - 2 GB or more of RAM per machine (any less will leave little room for your apps) 188 | - 2 CPUs or more 189 | - Ubuntu 20.04 LTS as operating system 190 | - Full network connectivity between all machines in the cluster (public or private network is fine) 191 | - Unique hostname, MAC address, and product_uuid for every node. See here for more details. 192 | - Certain ports are open on your machines. See here for more details. 193 | - Swap disabled. You MUST disable swap in order for the kubelet to work properly. 194 | - TCP Inbound 10250 open for Kubelet API 195 | - TCP Inbound 30000-32767 open for NodePort Services 196 | 197 | ## Ports required to be open on Worker Nodes 198 | 199 | ``` 200 | TCP 10250 Kubelet API 201 | TCP 10255 Read-Only Kubelet API 202 | ``` 203 | 204 | ## List of application to be deployed 205 | 206 | | Name | Application Name | 207 | |---------------------------|------------------------------| 208 | | Ajeet Singh Raina | Kubeview | 209 | | Anmol | Grafana | 210 | 211 | 212 | 213 | ## FAQs 214 | 215 | ## 1. How shall I contribute? 216 | 217 | Assuming that you have Docker installed in your system, you can run the below command to get your node connected to our Cluster: 218 | 219 | ``` 220 | sudo docker run -d --privileged --restart=unless-stopped --net=host -v /etc/kubernetes:/etc/kubernetes -v /var/run:/var/run rancher/rancher-agent:v2.4.18 --server https://kubezilla.collabnix.com --token wlcj8nwx8ns92n69qbnk9f4kkmc7jkswcbgzpsm9hc4k6dxwjxdm8c --worker 221 | ``` 222 | 223 | ## 2. Do I need to pay? 224 | 225 | No, we recommend you to use Free Tier so that you don't need to pay anything from your pocket. 226 | You can even use [PWD](https://play-with-docker.com) or [PWK](https://play-with-k8s.com) instance(free) but do note that these instances are usually operational only for 4 hours time. 227 | 228 | ## 3. Can I use my AWS/GCP/Azure Credits to get the nodes added? 229 | 230 | Yes, you can use those free credits. It's a matter of choice 231 | 232 | ## 4. How many maximum nodes can I contribute? 233 | 234 | There is no restriction. You can add as many nodes as you can. 235 | 236 | ## 5. Which ports are required to be open on worker nodes? 237 | 238 | ``` 239 | TCP 10250 Kubelet API 240 | TCP 10255 Read-Only Kubelet API 241 | ``` 242 | 243 | ## 6. I have added nodes. How can I see the nodes added? 244 | 245 | We are currently working on a Visualization tool to allow you to visualize the overall Kubernetes Cluster. Stay tuned. 246 | 247 | ## 7. Which OS needs to use for setting up worker nodes? 248 | 249 | We recommend you to use Ubuntu 20.04 LTS as operating system because of cgroup driver issue. 250 | 251 | ## References 252 | 253 | - [List of curated Kubernetes Tools](https://kubetools.collabnix.com) 254 | - [Kubernetes Tutorials](https://kubelabs.collabnix.com) 255 | -------------------------------------------------------------------------------- /cloud-drove-logo.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/collabnix/kubezilla500/db70e65ad0f74441b3387509ad56319c6a7f9951/cloud-drove-logo.jpg -------------------------------------------------------------------------------- /kubezilla500.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/collabnix/kubezilla500/db70e65ad0f74441b3387509ad56319c6a7f9951/kubezilla500.png -------------------------------------------------------------------------------- /logo__on-white.svg: -------------------------------------------------------------------------------- 1 | logo__on-white -------------------------------------------------------------------------------- /sponsorship.md: -------------------------------------------------------------------------------- 1 | # Kubezilla Sponsorship Proposal 2 | 3 | ## Introduction 4 | 5 | We are excited to present the opportunity to sponsor the Kubezilla project, which aims to build the largest Kubernetes Community Cluster. This community-driven initiative will be showcased during the upcoming Docker Bangalore Meetup event. We invite you to support this project by sponsoring a 3-node Master Node Kubernetes Cluster. 6 | 7 | ## About Kubezilla 8 | 9 | Kubezilla is an ambitious project that aims to provide community members with an immersive learning experience in Kubernetes and related technologies. By building the largest Kubernetes Community Cluster, we aim to demonstrate the scalability and power of Kubernetes, while fostering collaboration and knowledge sharing within the community. 10 | 11 | ## Sponsorship Benefits 12 | 13 | As a sponsor of Kubezilla, your organization will receive the following benefits: 14 | 15 | - **Prominent Brand Exposure:** Your company logo will be prominently displayed on our event website, marketing materials, and during the Docker Bangalore Meetup event, ensuring valuable brand visibility. 16 | 17 | - **Recognition as a Technology Leader:** By supporting this innovative community project, your organization will be recognized as a leader in the Kubernetes and cloud computing space. 18 | 19 | - **Targeted Audience:** The Docker Bangalore Meetup event attracts a diverse audience of technology enthusiasts, professionals, and industry experts. This sponsorship provides an excellent opportunity to reach a targeted audience interested in Kubernetes and related technologies. 20 | 21 | - **Networking Opportunities:** As a sponsor, you will have the chance to engage with event attendees, including potential customers, partners, and talented professionals in the field. 22 | 23 | ## Sponsorship Details 24 | 25 | We are seeking sponsorship to host a 3-node Master Node Kubernetes Cluster, which will serve as the foundation for the Kubezilla project. The sponsorship will cover the necessary cloud infrastructure or physical hardware required for the cluster setup. The specifications for the Master Node Kubernetes Cluster are as follows: 26 | 27 | - 3 Master Nodes with XGB of RAM and X vCore each. 28 | - Full network connectivity between the Master Nodes and worker nodes. 29 | - Unique hostname, MAC address, and product_uuid for each Master Node. 30 | - Disabled swap on all Master Nodes. 31 | 32 | ## How to Become a Sponsor 33 | 34 | If you are interested in sponsoring the 3-node Master Node Kubernetes Cluster for Kubezilla, please reach out to us using the contact information provided below. We will be happy to discuss the sponsorship details, answer any questions you may have, and provide further information as needed. 35 | 36 | **Contact Information:** 37 | 38 | - Full Name: 39 | - Company Name: 40 | - Position/Title: 41 | - Email: 42 | - Phone Number: 43 | 44 | ## Conclusion 45 | 46 | By sponsoring the 3-node Master Node Kubernetes Cluster for Kubezilla, you will not only contribute to the success of this community-driven project but also showcase your organization's commitment to fostering learning, collaboration, and innovation in the Kubernetes ecosystem. 47 | 48 | We look forward to the opportunity to partner with you and make Kubezilla a memorable and impactful event. Thank you for considering our sponsorship proposal. 49 | 50 | --------------------------------------------------------------------------------