k8s-config-connector
nixery
Our great sponsors
k8s-config-connector | nixery | |
---|---|---|
12 | 18 | |
824 | 1,685 | |
1.9% | - | |
9.8 | 4.8 | |
6 days ago | about 2 months ago | |
Go | Go | |
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.
k8s-config-connector
- Infrastructure as Code Tool Recommendation for GCP
-
It's worth apply the CFT (Cloud Foundation Toolkit) with terraform in an gcp org that is already running workloads?
If your company is k8s centric and the developers are most comfortable with k8s, you might want to focus more on something specific to k8s such as helm, or even if you don't get into helm you may want to use config connector in your yaml to manage GCP resources in an IaC compliant method. You can manage k8s resources with terraform, but if your developers are currently comfortable working directly with k8s you are going to see significant pushback getting them to add terraform as a middleware. You probably still want to manage your GKE clusters and VPCs with terraform since you can't really use config connector.
-
Ask HN: Have You Left Kubernetes?
Config Connector [1] is also an option in this space for GCP, it supports many GCP resources and thus far our experience with it has been largely positive.
[1] https://cloud.google.com/config-connector/docs/overview
-
As Argo CD momentum grows, Codefresh launches hosted GitOps
We use it heavily with GCP's Kubernetes Config Connector to provision architecture. It could similarly be used for Cloud Functions, etc. given a repo URL that GCP can access. GitOps + operator pattern is a pretty powerful mechanism to let k8s continuously seek state towards your ideal. https://cloud.google.com/config-connector/docs/overview
-
What should I learn to improve as a data engineer?
For K8s, we were using Cloud Composer to do it for us but wanted more fine control over CI/CD, so we decided to go with Airflow on K8s. That's all hosted in GKE now and deployed using ArgoCD with helm. This also led down the IaC rabbit hole which has been a ton of fun too. We use the GCP ConfigConnector resources for that which is a little challenging at first, but gets a lot easier as time goes on.
-
Best IaC platforms
Terraform is 90% of cloud IaC. But there are newer Kubernetes Operators like Config Connector that can create cloud specific resources.
- What is the story with Google Deployment Manager? Is Google going to abandon it at some point?
- Infra Provisioning, what do you guys use today?
-
K8s pods security in GCP
It works particularly well with Google Config Connector as then it's all just manifests.
- Weβre the engineers rethinking Kubernetes at Spotify. Ask us anything!
nixery
- Way to get NVM working in CI/CD systems
-
What's your favourite Docker Image, and why?
The ones from https://nixery.dev/
-
k8s docker image with basic troubleshooting tools
You can build your own with https://nixery.dev/
-
Crafting container images without Dockerfiles
I built a service for doing this ad-hoc via image names a few years ago and it enjoys some popularity with CI & debugging use-cases: https://nixery.dev/
-
Nixpacks takes a source directory and produces an OCI compliant image
name is eerily similar to `nixpkgs`, i.e. the monorepo that defines all packages and one of the underlying technologies here. i get the play on buildpacks, but still, as a nix user it makes me do a double take reading the name
this is neat though, and in political terms, the elevator pitch mentions nix itself as an implementation detail in passing. hopefully, if this catches on, it'll function as a non-threatening gateway drug to nix itself, when users inevitably go digging into the weeds
for anyone interested, prior art on the nix container front: https://nixery.dev
-
Ask HN: Have You Left Kubernetes?
Wow, this is excellent! At a previous job, we had been using k8s + knative to spin up containers on demand, and likewise were unhappy with the delays. Spawner seems excellent.
One question: have you had to do any custom container builds on demand, and if so, have you had to deal with large containers (e.g. a Python base image with a few larger packages installed from PyPI)? We would run up against extremely long build image times using tools like kaniko, and caching would typically have only a limited benefit.
I was experimenting using Nix to maybe solve some of these problems, but never got far enough to run a speed test, and then left the job before finishing. But it seems to me some sort of algorithm like Nixery uses (https://nixery.dev) to generate cacheable layers with completely repeatable builds and nothing extraneous would help.
Maybe that's not a problem you had to solve, but if it is, I'd love your thoughts.
-
Hacker News top posts: Apr 19, 2022
Nixery β Docker images on the fly with Nix\ (38 comments)
- Nixery β Docker images on the fly with Nix
What are some alternatives?
backstage - Backstage is an open platform for building developer portals
BirdNET-Pi - A realtime acoustic bird classification system for the Raspberry Pi 4B, 3B+, and 0W2 built on the TFLite version of BirdNET.
crossplane - The Cloud Native Control Plane
template-nix - The nix template, configured for Gitpod (www.gitpod.io) to give you pre-built, nix based ephemeral development environments in the cloud.
plural - Deploy open source software on Kubernetes in record time. π
niv - Easy dependency management for Nix projects
nydus - Nydus - the Dragonfly image service, providing fast, secure and easy access to container images.
jib - π Build container images for your Java applications.
community - Kubernetes community content
docker-volume-hetzner - Docker Volume Plugin for accessing Hetzner Cloud Volumes
Moby - The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems