Yusuke Kuoka

kanvas is a high-level, go-to tool for deploying your container-based applications along with the whole infrastructure. Tired of maintaining adhoc scripts or proprietary CI pipelines? kanvas's sole goal is to never require you to write an adhoc script to deploy your application. You write a kanvas configuration file once, and use it for various use-cases listed below...

prenv is a toolkit for creating and managing Per-Pull Request Environments for your projects. By saying a "toolkit", it means that it is a set of a CLI app and long-running apps that together gives you a handy way to manage PR envs. The CLI app is supposed to run locally and on CI, where the long-running apps are supposed to run locally(for testing) and remotely(for production). prenv is currently composed of the following tools: prenv: A CLI tool for creating and managing Per-Pull Request Environments. prenv-sqs-forwarder: A Go application that forwards messages from an SQS queue to the downstream, Per-Pull Request Environments' SQS queues. prenv-outgoing-webhook: A Go application that receives outgoing webhooks from the Per-Pull Request Environments and forwards them to the Slack channel of your choice.

kargo is a command-line application to deploy your Kubernetes application directly and indirectly. By "direct", it means kargo is able to deploy the app by directly calling popular commands like kubectl, kustomize, helm, kompose. By "indirect", it means kargo can let ArgoCD deploy your application using kustomize/helm/kompose by setting up ArgoCD on behalf of you. Everyone in your team is able to trigger deployments via kargo, no matter which Kubernetes deployment tool you or your teammate is using. That's the benefit of introducing kargo into your environment. If you're a part of the platform team, you'll probably want to encourage or enforce use of kargo, so that you can standardize deployments without forcing your team to use kubectl/kustomize/helm/argocd.

I have been co-maintaining helm-diff since 2019 and still keeping it. helm-diff has 1000+ stars and is used standalone or by other open source projects like helmwave and helmfile, supporting Kubernetes users who uses the famous Kubernetes package manager Helm world-wide.

Okra is a Kubernetes controller and a set of CRDs which provide advanced multi-cluster appilcation rollout capabilities, such as canary deployment of clusters. okra eases managing a lot of ephemeral Kubernetes clusters. If you've been using ephemeral Kubernetes clusters and employed blue-green or canary deployments for zero-downtime cluster updates, you might have suffered from a lot of manual steps required. okra is intended to automate all those steps.

I've been maintaining and leading the actions-runner-controller project for almost a year to help people leverage GitHub Actions self-hosted runners easily on their Kubernetes clusters. The project was started by the original author @summerwind. I've contributed a lot of fixes, documentation, features since then. I've led it to have a dedicated GitHub organization, one additional maintainer, too. We've succesfully made dozens of releases and apparently user base is still growing.

Helmfile is a tool to declaratively manage K8s resources. It has a lot of integrations for various secrets providers, clouds, and K8s deployment tools such as Kustomize and Helm. Many folks and companies have been using it in production as introduced in https://github.com/roboll/helmfile/blob/master/USERS.md. Although the repository is still owned by @roboll, I've been the primary maintainer of the project since 2018. I started contributing it even before I become the primary maintainer, and I'm still keeping it.