microk8s
tilt
microk8s | tilt | |
---|---|---|
8 | 49 | |
6,539 | 7,319 | |
- | 1.1% | |
9.3 | 8.8 | |
almost 2 years ago | 6 days ago | |
Python | 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.
microk8s
-
How to enable startup probe on GKE 1.16?
FROM postgres:11CMD sleep 30 && postgres I'm reusing this example from the same issue with microk8s where I could solve it by changing the kubelet and kubeapi-server configuration files (see https://github.com/ubuntu/microk8s/issues/770 in case you're interested). I assume this is not possible with GKE clusters as they don't expose these files, probably for good reasons.
-
How to configure kubernetes (microk8s) to use local docker images?
$ kubectl get podsNAME READY STATUS RESTARTS AGEbackend-deployment-66cff7d4c6-gwbzf 0/1 ImagePullBackOff 0 18s Before that it was ErrImagePull. So, my question is, how to tell it to use local docker images? Somewhere on the internet I read that I need to build images using microk8s.docker but it seems to be removed.
-
I was so excited to join this community
There's a whole community of hobbyists building Raspberry Pi clusters, porting things to work on various Arm processors, exploring and contributing to minimalist distros like k0s and microk8s, etc.
-
no persistent volumes available for this claim and no storage class is set
same pvc worked fine on "GKE" (Google Kubernetes Engine) but failing in my local cluster using microk8s
-
Is Kubernetes Still Just an Ops Topic?
Local Kubernetes Clusters: It is now possible to run Kubernetes on local machines with tools such as Kubernetes in Docker (kind), minikube or MicroK8s. This allows developers to run their first experiments completely isolated from others and with low risk and low cost.
-
Kubernetes Development Environments – A Comparison
Local Kubernetes clusters are clusters that are running on the individual computer of the developer. There are many tools that provide such an environment, such as Minikube, microk8s, k3s, or kind. While they are not all the same, their use as a development environment is quite comparable.
-
Local Cluster vs. Remote Cluster for Kubernetes-Based Development
Since the developer is the only one who has to access this cluster for development, local clusters can be a feasible solution for this purpose. Over time, several solutions have emerged that are particularly made for running Kubernetes in local environments. The most important ones are Kubernetes in Docker (kind), MicroK8s, minikube and k3s. For a comparison of these local Kubernetes options, you can look at this post.
-
The Journey of Adopting Cloud-Native Development
Another very important distinction of this level is that developers have direct access to Kubernetes for the first time. While it is not strictly necessary, the standard case for the Kubernetes access with these tools is to use a local Kubernetes cluster, i.e. a Kubernetes cluster started with tools such as minikube, kind or MicroK8s on the local computer of the developer.
tilt
-
Ask HN: What to do with small units of time during the working day?
Could improve that crappy feedback loop :)
If the language runtimes are compiled you can't do this, but if not, in theory you shouldn't need such a stupidly long core development feedback loop.
I'm a huge fan of https://tilt.dev/ and the possibilities it unlocks for that pre-commit development.
-
Uber Migrates 4000 Microservices to a New Multi-Cloud Platform
Something like https://tilt.dev/ where you spin up a subset of the service graph in a cloud environment that hot-reloads based on local edits.
-
Simplifying preview environments for everyone
To get a similar experience of preevy up, first we’ll need to split the build and deploy using process or alternatively employ tools that orchestrate build-tag-push-update-sync flow like Skaffold/Tilt.
-
Codespaces but open-source, client-only, and unopinionated
It's not a direct competitor, but we use https://tilt.dev/ at my company for local and remote development.
-
Why I recommended ECS instead of Kubernetes to my latest customer
For local testing you use tilt that runs stateful services locally in a kind k8s cluster. That same config can deploy to a remote k8s server to easily share a preview of new features, which is useful for prototyping things that might not necessarily ever be merged.
-
Local development set up for microservices with Kubernetes - Skaffold
There are dedicated tools just for that. Apart from skaffold check also tilt.dev, garden.io, devspace.sh, okteto.com
-
First K8s project
You basically start by downloading kind, then tilt. Then create a kind cluster with the provided configuration in the tilt repo. Then run tilt up and that's it. You'll have a fully functional Kubernetes cluster and project running complete with deployments and services. Nothing too fancy, no RBAC, no network policies etc.. Just the bare minimum to get you up and running.
-
Devcontainers in k8s
I recommend also looking into tilt.
-
KubeProject: A distributed multi-service project on Kubernetes as a playground for beginners
Second, and perhaps the best of all is, that I created a tilt repository located here.
-
Throwaway preconfigured local kubernetes environments
But apart from the other "k8s in a box" options (like minikube, k0s, ...) you could also have a look at tilt (https://tilt.dev/), it sounds like this might be a good fit for your use case as well.
What are some alternatives?
microshift - A small form factor OpenShift/Kubernetes optimized for edge computing
telepresence - Local development against a remote Kubernetes or OpenShift cluster
rancher - Complete container management platform
devspace - DevSpace - The Fastest Developer Tool for Kubernetes ⚡ Automate your deployment workflow with DevSpace and develop software directly inside Kubernetes.
k3s - Lightweight Kubernetes
skaffold - Easy and Repeatable Kubernetes Development
docker - Moby Project - a collaborative project for the container ecosystem to assemble container-based systems [Moved to: https://github.com/moby/moby]
okteto - Develop your applications directly in your Kubernetes Cluster
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
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
liqo - Enable dynamic and seamless Kubernetes multi-cluster topologies
helm - The Kubernetes Package Manager