K8s powered Git push deployments

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

InfluxDB - Purpose built for real-time analytics at any scale.
InfluxDB Platform is powered by columnar analytics, optimized for cost-efficient storage, and built with open data standards.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
  • pipeline

    A cloud-native Pipeline resource.

    I've recently found this quote by Kelsey Hightower:

    "I'm convinced the majority of people managing infrastructure just want a PaaS. The only requirement: it has to be built by them."

    Source: https://twitter.com/kelseyhightower/status/85193508753294540...

    In the last few weeks, I've experimented a bit with Flux (https://fluxcd.io/), Tekton (https://tekton.dev/) and Cloud Native Buildpacks (https://buildpacks.io/) on how to provide K8s powered git push deployments without using a dedicated CI/CD server.

    My project is still in early alpha stage and just a proof of concept :-) My vision is to expand it into an Open Source PaaS in the future.

    Do you think the above quote is true? What does an open source PaaS need to be like in order to be accepted by software developers?

    Some other projects have been discontinued in the past (like Flynn or Deis) or were created before the Kubernetes era.

    Is it the right direction to provide a Heroku like solution based on K8s or is it better to provide an Open Source Infrastructure as Code library with building blocks to avoid everything from scratch?

  • InfluxDB

    Purpose built for real-time analytics at any scale. InfluxDB Platform is powered by columnar analytics, optimized for cost-efficient storage, and built with open data standards.

    InfluxDB logo
  • flux2

    Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.

    I've recently found this quote by Kelsey Hightower:

    "I'm convinced the majority of people managing infrastructure just want a PaaS. The only requirement: it has to be built by them."

    Source: https://twitter.com/kelseyhightower/status/85193508753294540...

    In the last few weeks, I've experimented a bit with Flux (https://fluxcd.io/), Tekton (https://tekton.dev/) and Cloud Native Buildpacks (https://buildpacks.io/) on how to provide K8s powered git push deployments without using a dedicated CI/CD server.

    My project is still in early alpha stage and just a proof of concept :-) My vision is to expand it into an Open Source PaaS in the future.

    Do you think the above quote is true? What does an open source PaaS need to be like in order to be accepted by software developers?

    Some other projects have been discontinued in the past (like Flynn or Deis) or were created before the Kubernetes era.

    Is it the right direction to provide a Heroku like solution based on K8s or is it better to provide an Open Source Infrastructure as Code library with building blocks to avoid everything from scratch?

  • pack

    CLI for building apps using Cloud Native Buildpacks

    I've recently found this quote by Kelsey Hightower:

    "I'm convinced the majority of people managing infrastructure just want a PaaS. The only requirement: it has to be built by them."

    Source: https://twitter.com/kelseyhightower/status/85193508753294540...

    In the last few weeks, I've experimented a bit with Flux (https://fluxcd.io/), Tekton (https://tekton.dev/) and Cloud Native Buildpacks (https://buildpacks.io/) on how to provide K8s powered git push deployments without using a dedicated CI/CD server.

    My project is still in early alpha stage and just a proof of concept :-) My vision is to expand it into an Open Source PaaS in the future.

    Do you think the above quote is true? What does an open source PaaS need to be like in order to be accepted by software developers?

    Some other projects have been discontinued in the past (like Flynn or Deis) or were created before the Kubernetes era.

    Is it the right direction to provide a Heroku like solution based on K8s or is it better to provide an Open Source Infrastructure as Code library with building blocks to avoid everything from scratch?

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • Does anyone else feel like this?

    3 projects | /r/kubernetes | 19 Jan 2023
  • Kubero : alternative à Heroku pour Kubernetes …

    5 projects | dev.to | 22 Dec 2022
  • Converting docker-compose files

    3 projects | /r/akashnetwork | 10 Jul 2022
  • Building functions with Knative and Tekton

    9 projects | dev.to | 17 Apr 2022
  • The best way to build docker images in go 1.17

    8 projects | /r/golang | 16 Oct 2021

Did you konow that Go is
the 4th most popular programming language
based on number of metions?