epinio
vcluster
epinio | vcluster | |
---|---|---|
10 | 70 | |
501 | 5,597 | |
1.8% | 5.1% | |
8.8 | 9.8 | |
about 1 month ago | 4 days 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.
epinio
-
I want to be able to deploy apps as quickly as possible to on-prem k8s. I was looking at Jenkins-x with their jx create command, looks pretty powerful, but it looks complicated to setup. Any easier alternatives?
You could have a look to https://epinio.io/. It is a PAAS that leverage build pack to deploy app on k8s cluster. Disclaimer: my team is working on it
-
Questions for Heroku-like Project
Epinion
- Epinio: Kubernetes PaaS from SuSE
-
A selfhosted Heroku clone on your Kubernetes cluster
Would have helped if I spent it right ๐ - https://github.com/epinio/epinio
-
Epinio: the open-source Application development engine for Kubernetes
Epinio can be installed using Helm onto any compliant Kubernetes Cluster. The latest CLI release can be found at [][https://github.com/epinio/epinio/releases]
-
How to manage access to a Kubernetes cluster for Dev Teams ?
We are building a product (Epinio) to avoid this. The idea is that devs don't need to access the cluster and to know the Kubernetes internals to deploy something. It's still in alpha/beta, with a lot of development ongoing. ๐
-
Moving to Kubernetes
For the Apache/php container portion and building the app itself, I'd suggest looking at buildpacks (Paketo buildpacks are easy). This can let you standardize on the code->container pipeline. (I'm biased since I'm working on Epinio which uses them to simplify the code->running application pipeline)
- Opinionated K8s platform to take you from Code to URL in one step
-
Should We Replace Docker Desktop With Rancher Desktop?
For dev work, we also are working on a project called Epinio which takes a bit of a different approach to developing on top of Kubernetes. (https://epinio.io)
-
Example of using Makefile for Kubernetes development
Your workflow describes the inner loop of development. Take a look at https://skaffold.dev that. If you canโt be bothered to learn how to write k8s manifests, epinio might be worth a shot. I tried it on some simple stuff and it worked but I doubt itโs usefulness in complex setups. https://github.com/epinio/epinio
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/)
What are some alternatives?
okteto - Develop your applications directly in your Kubernetes Cluster
capsule - Multi-tenancy and policy-based framework for Kubernetes.
space-cloud - Open source Firebase + Heroku to develop, scale and secure serverless apps on Kubernetes
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
lima - Linux virtual machines, with a focus on running containers
kiosk - kiosk ๐ข Multi-Tenancy Extension For Kubernetes - Secure Cluster Sharing & Self-Service Namespace Provisioning
skaffold - Easy and Repeatable Kubernetes Development
cluster-api-provider-nested - Cluster API Provider for Nested Clusters
OpenFaaS - OpenFaaS - Serverless Functions Made Simple
hierarchical-namespaces - Home of the Hierarchical Namespace Controller (HNC). Adds hierarchical policies and delegated creation to Kubernetes namespaces for improved in-cluster multitenancy.
kube-makefile - Makefile tooling to simplify local development for small Kubernetes projects.
k3s - Lightweight Kubernetes