pack
helm-static
Our great sponsors
pack | helm-static | |
---|---|---|
46 | 1 | |
2,373 | 2 | |
2.0% | - | |
9.5 | 1.8 | |
1 day ago | over 3 years ago | |
Go | HTML | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pack
- Différentes façons de déployer une application front faites en JS
-
K8s powered Git push deployments
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?
-
Crafting container images without Dockerfiles
Although Dockerfiles have the benefit of migrating existing workloads to containers without having to update your toolchain, I definitely prefer the container-first workflow. Cloud Native [Buildpacks](https://buildpacks.io/) are a CNCF incubating project but were proven at Heroku. Buildpacks support common languages, but working on a Go project I've also had a great experience with [ko](https://ko.build/). Free yourself from Dockerfile!
-
Kubero : alternative à Heroku pour Kubernetes …
Cloud Native Buildpacks
-
The world outside of WordPress
It's big and overwhelming and sometimes scary. But you know what? It's also fun, engaging, and very refreshing. Because I'm a DevRel, I don't have many chances to focus on something particular. Still, I'm having a lot of fun exploring different CMSs (like Statamic, Craft, or Sanity), new approaches (at last, I understood why the headless approach is so important), and diving into tech I never used before (hello Buildpacks).
- Does anyone use any alternatives to Dockerfile for creating containers? Something with nicer syntax?
- Jetstack Paranoia: A New Open-Source Tool for Container Image Security
-
YAML Buildpack: Auto Validate Configuration Repositories
[5] https://buildpacks.io/
-
Devbox 📦 : Instant, easy, and predictable shells and containers
Devbox analyzes your source code and instantly turns it into an OCI-compliant image that can be deployed to any cloud. The image is optimized for speed, size, security and caching ... and without needing to write a Dockerfile. And unlike buildpacks, it does it quickly.
-
A selfhosted Heroku clone on your Kubernetes cluster
I had a short look into buildpacks.io . So I don't have a firm opinion yet. But as much i understand now, it really builds Container images. Kubero goes a different approach. The buildstep only compiles the project to a mounted volume, which is mounted readonly to the running container. Further more is the detection step unnecessary, since the dev knows what he wants to build and selects the buildimage. How ever, I'm still looking into it, so see if my project can profit from the great work there in any other way.
helm-static
-
If you had one wish for a K8s-related tool, what would it be?
If you're fine with having a single file with all your systems in it you could use https://github.com/cetic/helm-static. But we'd rather have a file per system, for a better overview
What are some alternatives?
kaniko - Build Container Images In Kubernetes
helm-charts - Prometheus community Helm charts
jib - 🏗 Build container images for your Java applications.
coolify - An open-source & self-hostable Heroku / Netlify / Vercel alternative.
okteto - Develop your applications directly in your Kubernetes Cluster
kubefwd - Bulk port forwarding Kubernetes services for local development.
prometheus-operator - Prometheus Operator creates/configures/manages Prometheus clusters atop Kubernetes
porter - Kubernetes powered PaaS that runs in your own cloud.
garden - Automation for Kubernetes development and testing. Spin up production-like environments for development, testing, and CI on demand. Use the same configuration and workflows at every step of the process. Speed up your builds and test runs via shared result caching
ClojureDart - Clojure dialect for Flutter and Dart
shuttle - Build & ship backends without writing any infrastructure files.
distroless - 🥑 Language focused docker images, minus the operating system.