Fetching the latest programs, projects, and workspace data.
Templated configuration management for Kubernetes, Terraform and other things
Showing 2 of 2 projects. Click any project card for scope, mentors, and proposal studio.
Mentors: Student: Arindaam Roy
<h4>This proposal consists of 3 sub tasks of kapitan which is elaborated below.</h4> <h3>Task1 : Remote Inventory Federation</h3> <p>This work would add the ability to Kapitan to fetch parts of the Inventory from remote locations (https/git). This would allow users to combine different inventories from different sources and build modular infrastructure reusable across various repos.</p> <h3>Task2 : Support for Helm binding in OSX</h3> <p>This project can be subdivided into the following three tasks:</p> <ul> <li>Complete the Helm binding pipeline so that continuous integration (travis) also builds binding for osx and releases them to GitHub release.</li> <li>Packaging the binding to the pypi release.</li> <li>Add a brew manifest for osx so that users there can install Kapitan in a simpler way.</li> </ul> <h3>Task3 (bonus): Modularize kapitan</h3> <p>This project would modularize kaitan into core dependencies and extra modules.</p> <h3>Documentation and tutorial</h3> <p>Along with all the other tasks, documentation of all new and existing features will be done and displayed to kapitan.dev and walkthroughs will be made for the examples given in the documentation.</p>
Mentors: Student: Yoshiaki Nishimura
<p>This proposal consists of a few tasks that implement new features for Kapitan which I believe will add value to the software. Task 1: dependency management With this feature, kapitan users will be able to fetch sources via HTTP[S] and/or git during compilation into specific targets. This will allow them to manage online dependencies much more easily.</p> <p>Task 2: support for Helm chart import This will allow existing Helm users to import their charts into kapitan projects and render the charts together with the values set in the kapitan inventory to compile into a target. This integration will make it easy for users to switch to kapitan from Helm.</p> <p>Task 3: kapitan binary Kapitan exists as a pip package to be used in CLI and as a Docker image. Users have pointed out that having a portable binary for Kapitan would be very helpful. This task aims to meet such needs by packaging kapitan into a static binary with the use of third-party build tools.</p> <p>Task 4: json schema validation for k8s Kapitan, just as it has its own channel in k8s slack community, is used by a large number of k8s users. This feature enables pre-checking of compilation output of k8s configuration files.</p>