vcluster
watchtower
Our great sponsors
vcluster | watchtower | |
---|---|---|
70 | 215 | |
5,577 | 16,821 | |
12.0% | 3.2% | |
9.7 | 8.4 | |
4 days ago | about 1 month 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.
vcluster
-
Amazon EC2 Enhances Defense in Depth with Default IMDSv2
Kubernetes? You mean the container orchestration system where they forgot to add Multi-tenancy? And no namespaces are not Multi-tenancy...
https://www.vcluster.com/
-
Mirantis Unveils K0smotron: An Open-Source Kubernetes Management Project
Whats the difference between this and vcluster (https://github.com/loft-sh/vcluster)?
-
Codespaces but open-source, client-only, and unopinionated
Yep, as we see it they compliment each other quite well. DevPod takes your workspace to the cloud and DevSpace let's you develop against your Kubernetes cluster - potentially the same one you used to start your workspace.
Internally we use both in our development setup, spinning up remote workspaces using DevPod, installing DevSpace and kind into the devcontainer, then using DevSpace to develop against the cluster. See the vcluster setup[1] as an example
[1]https://github.com/loft-sh/vcluster/tree/main/.devcontainer
-
Anyone using Kata Containers?
The tenants are internal dev teams so yeah maybe not. I was considering multi-tenanting different environments isolated at the kube layer with vCluster and have the vCluster pods running in Kata containers giving maximum isolation but still having a single management cluster. Ideally also avoiding the need to buy a second set of hardware for a dev environment
-
Multi-tenancy in Kubernetes
Vcluster
-
Kub'rin' a breeze: Developing on ephemeral cloud-based K8s clusters
Looks interesting. How does this solution compare to vcluster?
-
Same cluster for different development environments
sounds like the best option for you , is a tool called VCluster by loft ( https://www.vcluster.com/) , this way you can install as many k8s cluster as you want in the same k8s host cluster , those cluster share workers nodes and networking, but each has a separated "api server" , so it looks like you have a dedicated cluster with their own namespaces and tools . take a look at the docs to get a better understanding and how they work.
-
Is it a good idea to use k8s namespace-based multitenancy for delivering managed service of an application?
We're about to run a PoC with vcluster for isolated sandboxes, this might be relevant to you too
-
Questions for Heroku-like Project
I think namespaces, RBAC and network policies are sufficient to partition users from the same organisation. I would investigate the use of vcluster ig you want to give your users even more isolation and capability (such as installing CRDs)
-
Multiple Tenancy, Namespaces, Securing Workloads
Depends on the use case. Namespaces provides soft isolation (so it means they share same Apiserver, PV's and global resources such as CRD's), but can be restricted with network policies. So it means, there's still potential in breaking other namespaces if you change PV's or CRD's which are used by other namespaces. Multi-Cluster solution can provide full isolation, but its also really expensive in resource consumption and maintenance/management effort. If namespaced-isolation isnt enough for your use case, you can consider vclusters (https://www.vcluster.com/)
watchtower
-
My deployment platform is a shell script
Related: https://github.com/containrrr/watchtower
- PSA - Run "docker image prune" once in a while.
-
Roundcube Open-Source Webmail Software Merges with Nextcloud
> if you're using the docker image, upgrades are a breeze. Just bump the tag on the image, redeploy, and you're done.
Or you could just run Watchtower beside it and it will automatically update your docker containers. https://github.com/containrrr/watchtower If you are OK with automated updates.
-
The Curse of Docker
So i primarily use containers on my local machine walled off from the internet, so it's not a big concern for me. Watchtower [1] is popular among home server users too which automatically updates containers to the latest image.
For production uses I think companies generally build their own containers. They would have a common base linux container and build the other containers based off that with a typical CI/CD pipeline. So if glibc is patched, it's probably patched in the base container and the others are then rebuilt. You don't have to patch each container individually, just the base. Production also minimizes the scope of containers with nothing installed except what's necessary so they have few dependencies.
[1] https://github.com/containrrr/watchtower
-
Ask HN: If you were to build a web app today what tech stack would you choose?
You can use Watchtower (https://containrrr.dev/watchtower/) that solves problem of manual pulling on VPS.
-
Running watchtower weekly or whenever new image is available
I checked https://containrrr.dev/watchtower/ and Arguments, but I don't understand where to attach that using portainer.
-
Long Term Ownership of an Event-Driven System
Again, there are options to automate some of the burden here by using tools such as Watchtower.
-
Updating Docker Apps automagically with Watchtower✨🐳
Have you ever deployed a Docker app on a server, but everytime you push a new version of your image to a Docker registry you need to manually restart your app? If you want to automate this restarting, this blog post is for you! I am now going to show you how you can do this with literally 1 simple command using Watchtower!
- Plex Docker Saved me
- Watchtower updates
What are some alternatives?
capsule - Multi-tenancy and policy-based framework for Kubernetes.
ouroboros - Automatically update running docker containers with newest available image
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
Diun - Receive notifications when an image is updated on a Docker registry
kiosk - kiosk 🏢 Multi-Tenancy Extension For Kubernetes - Secure Cluster Sharing & Self-Service Namespace Provisioning
Portainer - Making Docker and Kubernetes management easy.
cluster-api-provider-nested - Cluster API Provider for Nested Clusters
docker-socket-proxy - Proxy over your Docker socket to restrict which requests it accepts
hierarchical-namespaces - Home of the Hierarchical Namespace Controller (HNC). Adds hierarchical policies and delegated creation to Kubernetes namespaces for improved in-cluster multitenancy.
shepherd - Docker swarm service for automatically updating your services whenever their image is refreshed
k3s - Lightweight Kubernetes
whats-up-docker - What's up Docker ( aka WUD ) gets you notified when a new version of your Docker Container is available.