swarmkit
rancher
swarmkit | rancher | |
---|---|---|
14 | 89 | |
3,250 | 22,546 | |
0.6% | 0.5% | |
8.0 | 9.9 | |
19 days ago | 5 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.
swarmkit
-
Questions about Swarm mode
It's supported, though the development pace is rather slow. The are new features (the latest release brought support for the Container Storage Interface) and bugs and issues are worked on by the few maintainers the project has. You can check the repo here: https://github.com/moby/swarmkit
-
K8s vs Docker Swarm
So the thing is support for Swarm was delegated to Mirantis, https://www.mirantis.com/blog/mirantis-will-continue-to-support-and-develop-docker-swarm/ since it was delegated very little was done to move forward swarm _> https://github.com/moby/swarmkit/commits/master , docker swarm itself (docker the company) is deprecated https://github.com/docker-archive/classicswarm . I think because there's no way to monetize swarm there's no real push for new features hence my assumption of deprecation.
-
Feature request: Enable "--device" in "stack deploy" for Confidential Computing
Feature request: Enable "--device" in "stack deploy" for Confidential Computing
-
Swarmlet: A self-hosted, open-source Platform as a Service
This doesn't look that abandoned? https://github.com/moby/swarmkit
Or are you talking about swarm the product (versus docker swarm mode)
-
Docker 23.0.0 is out
I don’t feel a momentum in Docker Swarm development, seeing pull requests like #3072 sitting idle for half a year, originally from 2016.
-
Looking to containerize a large production scale nodejs app
privileged not being supported is problematic, but there are PRs for it on swarmkit, see https://github.com/moby/swarmkit/pull/3072 - let's see if that gets in.
-
high availability
swarm ha placement
-
Is docker still the solution for On-Premesis containerization?
It is already in a different repo: moby/swarmkit
-
Help convincing IT/IS department to use Kubernetes
Docker Swarm is dead. It should not be used for new projects because the competitive products are much better and more optimal. Check their repo bro - last commit 3months ago. https://github.com/docker/swarmkit https://www.reddit.com/r/docker/comments/ituysl/why_people_are_saying_docker_swarm_is_in_life/ Why would you start a project with a tool which got no future? Let's then use Silverlight or any shit like that.
-
Why docker swarm is not popular as Kubernetes?
Mostly it just needs resource defaults merged and some abstract type support so load balancer config doesn't have to be entirely by labels and I would never shift from it.
rancher
-
OpenTF Announces Fork of Terraform
Did something happen to the Apache 2 rancher? https://github.com/rancher/rancher/blob/v2.7.5/LICENSE RKE2 is similarly Apache 2: https://github.com/rancher/rke2/blob/v1.26.7%2Brke2r1/LICENS...
-
Kubernetes / Rancher 2, mongo-replicaset with Local Storage Volume deployment
I follow the 4 ABCD steps bellow, but the first pod deployment never ends. What's wrong in it? Logs and result screens are at the end. Detailed configuration can be found here.
- Trouble with RKE2 HA Setup: Part 2
-
Critical vulnerability (CVE-2023-22651) in Rancher 2.7.2 - Update to 2.7.3
CVE-2023-22651 is rated 9.9/10 : https://github.com/rancher/rancher/security/advisories/GHSA-6m9f-pj6w-w87g
-
What's your take if DevOps colleague always got new initiative / idea?
Depends. When I came into my last company I immediately noticed the lack of reproducible environments. Brought this up a few times and was met with some resistance because "we didn't have the capacity"... Until prod went down and it took us 23 hours to bring it back up due to spaghetti terraform.
-
Questions about Rancher Launched/imported AKS
For the latest releases of rancher: https://github.com/rancher/rancher/releases When is Rancher 2.7.1 going to be released? The Rancher support matrix for 2.7.1 shows k8s v1.24.6 as the highest supported version and Azure will drop AKS v1.24 in a few months... Should this be a concern for us? What could happen if we create our cluster with Rancher for an unsupported K8s version? 1.25 for example. - Rancher 2.7.2 just got released including support for 1.25. I have however tested running unsupported versions before, unless there is major deprecations in the kubernetes API it is fine in my experience. If we move to AKS imported clusters, in case we add node pools, and upgrade the cluster, will those changes be reflected in the Rancher Platform? - Yep! If we face some issues by running an unsupported K8s version on Rancher Launched K8s clusters, is it possible to remove it from Rancher, do the stuff we need, and then import it into the platform? - Yes, however be careful and do testing before doing in prod. From top of mind: Remove cluster from rancher (if imported), if rancher created you might want to revoke ranchers SA key for the cluster first (so it can't remove it). Delete the cattle-system namespace, and any other cattle-* namespaces you don't want to keep. And do your thing. It looks like AKS is faster than Rancher regarding supported Kubernetes versions... We would like to know if Rancher will always be on track with AKS regarding the removal of K8s version support and new versions. - In my experience yes. (Been using rancher on all three clouds for a 4 years now). What are exactly the big differences between imported AKS and Rancher-launched AKS? What should we look at, and what issues can we face when using one or another? - The main difference is that rancher will not be able to upgrade the cluster for you. You will have to do that yourself.
-
rancher2_bootstrap.admin resource fail after Kubernetes v1.23.15
variable "rancher" { type = object({ namespace = string version = string branch = string chart_set = list(object({ name = string value = string })) }) default = { namespace = "cattle-system" # There is a bug with destroying the cloud credentials in version 2.6.9 until 2.7.1 and will be fixed in next release 2.7.2. # See https://github.com/rancher/rancher/issues/39300 version = "2.7.0" branch = "stable" chart_set = [ { name = "replicas" value = 3 }, { name = "ingress.ingressClassName" value = "nginx-external" }, { name = "ingress.tls.source" value = "rancher" }, # There is a bug with the uninstallation of Rancher due to missing priorityClassName of rancher-webhook # The priorityClassName need to be set # See https://github.com/rancher/rancher/issues/40935 { name = "priorityClassName" value = "system-node-critical" } ] } description = "Rancher Helm chart properties." }
-
Google and Microsoft’s chatbots are already citing one another in a misinformation shitshow
When I searched DuckDuckGo instead, the 12th link actually had the real answer. It's in this issue on Rancher's GitHub. Turns out the Rancher admin needs to be in all of the Keycloak groups they want to have show up in the auto-populated picklist in Rancher. Being a Keycloak admin and even creating the groups isn't good enough. Frustratingly, the "caveat" note the Rancher guy is pointing to that says this is only present in the guide to setting up Keycloak for SAML, but apparently this is also true for OIDC.
-
How to enable TLS 1.3 protocol
Explicitly set TLS 1.3 in Rancher, though it could be a bug in Rancher: https://github.com/rancher/rancher/issues/35654
-
Rancher deployment, hanging on login and setup pages
Thanks. Yeah looks like this might work: https://github.com/rancher/rancher/releases/tag/v2.7.2-rc3
What are some alternatives?
roadmap - Welcome to the Public Roadmap for All Things Docker! We welcome your ideas.
podman - Podman: A tool for managing OCI containers and pods.
docker - Moby Project - a collaborative project for the container ecosystem to assemble container-based systems [Moved to: https://github.com/moby/moby]
lens - Lens - The way the world runs Kubernetes
Docker Compose - Define and run multi-container applications with Docker
microk8s - MicroK8s is a small, fast, single-package Kubernetes for datacenters and the edge.
kubespray - Deploy a Production Ready Kubernetes Cluster
kubesphere - The container platform tailored for Kubernetes multi-cloud, datacenter, and edge management ⎈ 🖥 ☁️
Nomad - Nomad is an easy-to-use, flexible, and performant workload orchestrator that can deploy a mix of microservice, batch, containerized, and non-containerized applications. Nomad is easy to operate and scale and has native Consul and Vault integrations.
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle
distribution-spec - OCI Distribution Specification