Weave is a simple, portable and reliable way to network and manage containers and microservices. It provides a simple and resilient network for your application that is portable across data centers and public clouds. Weave Net creates a virtual network that connects Docker containers across multiple hosts and enables their automatic discovery. Applications use the network just as if the containers were all plugged into the same network switch, without having to configure port mappings, ambassadors or links.
 
Services provided by application containers on the Weave network can be exposed to the outside world, regardless of where they are running. Similarly, existing internal systems can be opened to accept connections from application containers irrespective of their location.

Weave is a simple, portable and reliable way to network and manage containers and microservices. It provides a simple and resilient network for your application that is portable across data centers and public clouds. Weave Net creates a virtual network that connects Docker containers across multiple hosts and enables their automatic discovery. 

Weave - Simple, Resilient Multi-host Docker Networking

OpenEBS is containerized block storage written in Go for cloud native and other environments w/ per container (or pod) QoS SLAs, tiering and replica policies across AZs and environments, and predictable and scalable performance.
 
OpenEBS allows you to treat your persistent workload containers, such as DBs on containers, just like other containers. OpenEBS itself is deployed as just another container on your host, and enables storage services that can be designated on a per pod, application, cluster or container level, including:
<ul>
<li>Data persistence across nodes, dramatically reducing time spent rebuilding Cassandra rings for example</li>
<li>Synchronization of data across availability zones and cloud providers</li>
<li>Use of commodity hardware plus a container engine to deliver seriously scale out block storage</li>
<li>Integration with orchestrators, so that developer and application intent flows into OpenEBS configurations automatically</li>
<li>Management of tiering to and from S3 and other targets</li>
<li>Plus we are bringing our experience from BSD based containerization and delivering QoS for customers from our CloudByte experience over to OpenEBS - expect to see more intelligence and manageability</li>
</ul>

OpenEBS is containerized block storage written in Go for cloud native and other environments w/ per container (or pod) QoS SLAs, tiering and replica policies across AZs and environments, and predictable and scalable performance. 


OpenEBS - Containerized Storage for Containers

MicroK8s is the smallest, fastest Kubernetes, Single-package fully conformant lightweight Kubernetes that works on 42 flavours of Linux. It is suitable for Developer workstations, IoT, CI/CD, Edge. MicroK8s is small, with sensible defaults that ‘just work’. A quick install, easy upgrades and great security make it perfect for micro clouds and edge computing.


MicroK8s - The smallest, fastest Kubernetes

Litmus is a toolset to do cloud-native chaos engineering. Litmus provides tools to orchestrate chaos on Kubernetes to help SREs find weaknesses in their deployments. SREs use Litmus to run chaos experiments initially in the staging environment and eventually in production to find bugs, vulnerabilities. Fixing the weaknesses leads to increased resilience of the system.
 
Chaos experiments are hosted on hub.litmuschaos.io. It is a central hub where the application developers or vendors share their chaos experiments so that their users can use them to increase the resilience of the applications in production.

Litmus is a toolset to do cloud-native chaos engineering. Litmus provides tools to orchestrate chaos on Kubernetes to help SREs find weaknesses in their deployments. SREs use Litmus to run chaos experiments initially in the staging environment and eventually in production to find bugs, vulnerabilities. Fixing the weaknesses leads to increased resilience of the system.

Litmus - Cloud-Native Chaos Engineering

CRI-O is an OCI-based implementation of Kubernetes Container Runtime Interface. CRI-O is meant to provide an integration path between OCI conformant runtimes and the kubelet. Specifically, it implements the Kubelet Container Runtime Interface (CRI) using OCI conformant runtimes. The scope of CRI-O is tied to the scope of the CRI.

CRI-O - OCI-based implementation of Kubernetes Container Runtime Interface

Apache APISIX is a dynamic, real-time, high-performance API gateway. APISIX provides rich traffic management features such as load balancing, dynamic upstream, canary release, circuit breaking, authentication, observability, and more. You can use Apache APISIX to handle traditional north-south traffic, as well as east-west traffic between services. It can also be used as a k8s ingress controller.
 
You can use Apache APISIX as a traffic entrance to process all business data, including dynamic routing, dynamic upstream, dynamic certificates, A/B testing, canary release, blue-green deployment, limit rate, defense against malicious attacks, metrics, monitoring alarms, service observability, service governance, etc.

Apache APISIX is a dynamic, real-time, high-performance API gateway. APISIX provides rich traffic management features such as load balancing, dynamic upstream, canary release, circuit breaking, authentication, observability, and more. You can use Apache APISIX to handle traditional north-south traffic, as well as east-west traffic between services. It can also be used as a k8s ingress controller.

Apache APISIX - Dynamic, real-time, high-performance API gateway

Kafdrop is a web UI for viewing Kafka topics and browsing consumer groups. The tool displays information such as brokers, topics, partitions, consumers, and lets you view messages.

Kafdrop – Kafka Web UI

Deepfence ThreatMapper helps you to monitor and secure your running applications, in Cloud, Kubernetes, Docker, and Fargate Serverless. ThreatMapper scans your platforms and identifies pods, containers, applications, and infrastructure. Use ThreatMapper to discover the topology of your applications and attack surface. It obtains manifests of dependencies from running pods and containers, serverless apps, applications, and operating system. ThreatMapper matches these against vulnerability feeds to identify vulnerable components.
 
ThreatMapper discovers, annotates and displays the topology of your applications across multiple cloud environments. It ranks discovered vulnerabilities against CVSS and other severity scores, exploit method and proximity to attack surface, in order to identify which issues pose the greatest risk of exploit.

Deepfence ThreatMapper helps you to monitor and secure your running applications, in Cloud, Kubernetes, Docker, and Fargate Serverless. ThreatMapper scans your platforms and identifies pods, containers, applications, and infrastructure. Use ThreatMapper to discover the topology of your applications and attack surface. It obtains manifests of dependencies from running pods and containers, serverless apps, applications, and operating system. ThreatMapper matches these against vulnerability feeds to identify vulnerable components.

DeepFence - Identify vulnerabilities in running containers, images, hosts and repositories

KEDA is a Kubernetes-based Event Driven Autoscaler. With KEDA, you can drive the scaling of any container in Kubernetes based on the number of events needing to be processed. KEDA works alongside standard Kubernetes components like the Horizontal Pod Autoscaler and can extend functionality without overwriting or duplication. 
 
With KEDA you can explicitly map the apps you want to use event-driven scale, with other apps continuing to function. This makes KEDA a flexible and safe option to run alongside any number of any other Kubernetes applications or frameworks.

KEDA is a Kubernetes-based Event Driven Autoscaler. With KEDA, you can drive the scaling of any container in Kubernetes based on the number of events needing to be processed. KEDA works alongside standard Kubernetes components like the Horizontal Pod Autoscaler and can extend functionality without overwriting or duplication. 

KEDA - Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes 

Kyverno is a policy engine designed for Kubernetes. With Kyverno, policies are managed as Kubernetes resources and no new language is required to write policies. This allows using familiar tools such as kubectl, git, and kustomize to manage policies. Kyverno policies can validate, mutate, and generate Kubernetes resources. The Kyverno CLI can be used to test policies and validate resources as part of a CI/CD pipeline.
 
Kyverno allows cluster administrators to manage environment specific configurations independently of workload configurations and enforce configuration best practices for their clusters. Kyverno can be used to scan existing workloads for best practices, or can be used to enforce best practices by blocking or mutating API requests.

Kyverno is a policy engine designed for Kubernetes. With Kyverno, policies are managed as Kubernetes resources and no new language is required to write policies. This allows using familiar tools such as kubectl, git, and kustomize to manage policies. Kyverno policies can validate, mutate, and generate Kubernetes resources. The Kyverno CLI can be used to test policies and validate resources as part of a CI/CD pipeline.



Kyverno - Kubernetes Native Policy Management



Karpenter simplifies Kubernetes infrastructure with the right nodes at the right time. It automatically launches just the right compute resources to handle your cluster's applications. It is designed to let you take full advantage of the cloud with fast and simple compute provisioning for Kubernetes clusters. Its main job is to add nodes to handle unschedulable pods, schedule pods on those nodes, and remove the nodes when they are not needed.
 
It responds quickly and automatically to changes in application load, scheduling, and resource requirements, placing new workloads onto a variety of available compute resource capacity. It comes with a set of opinionated defaults in a single, declarative Provisioner resource which can easily be customized. No additional configuration required.

Karpenter simplifies Kubernetes infrastructure with the right nodes at the right time. It automatically launches just the right compute resources to handle your cluster's applications. It is designed to let you take full advantage of the cloud with fast and simple compute provisioning for Kubernetes clusters. Its main job is to add nodes to handle unschedulable pods, schedule pods on those nodes, and remove the nodes when they are not needed.

Karpenter - Kubernetes Node Autoscaling: built for flexibility, performance, and scalability

Dragonfly is an open source intelligent P2P based image and file distribution system. Its goal is to tackle all distribution problems in cloud native scenarios. It is efficient with P2P and CDN technology which reduces image distribution time significantly and expedite delivery. it supports large-scale file distribution with improved downloading speed and success rate and lower consumption of bandwidth, especially cross-IDC bandwidth.
 
Its features include: 
<ul>
<li>Implement P2P files distribution with various storage types
(HDFS, storage services from various cloud vendors, Maven, Yum, etc.)
through a unified back-to-source adapter layer.</li>
<li>Support more distribution modes:
active pull, active push, real-time synchronization,
remote replication, automatic warm-up,
cross-cloud transmission, etc.</li>
<li>Provide separation and decoupling between systems,
scheduling and plug-in CDN. Support on-demand deployment with
flexible types: light or heavy, inside or outside,
to meet the actual needs of different scenarios.</li>
<li>Newly designed P2P protocol framework based on
GRPC with improved efficiency and stability.</li>
<li>Perform encrypted transmission, account-based transmission
authentication and rate limit, and multi-tenant isolation mechanism.</li>
<li>Bear more efficient IO methods: multithreaded IO, memory mapping, DMA, etc.</li>
<li>Advocate dynamic compression, in-memory file systems,
and more efficient scheduling algorithms to improve distribution efficiency.</li>
<li>Client allows third-party software to
natively integrate Dragonfly’s P2P capabilities through C/S mode.</li>
<li>Productivity: Support file uploading, task management of
various distribution modes, data visualization, global control, etc.</li>
<li>Consistent internal and external versions, shared core features,
and individual extensions of non-generic features.</li>
<li>Enhanced integration with ecology:
Harbor, Nydus (on-demand image download),
warehouse services for various cloud vendors, etc.</li>
</ul>

Dragonfly is an open source intelligent P2P based image and file distribution system. Its goal is to tackle all distribution problems in cloud native scenarios. It is efficient with P2P and CDN technology which reduces image distribution time significantly and expedite delivery.  it supports large-scale file distribution with improved downloading speed and success rate and lower consumption of bandwidth, especially cross-IDC bandwidth.

Dragonfly - An Open-source P2P-based Image and File Distribution System

Helm is a tool for managing Kubernetes charts. Charts are packages of pre-configured Kubernetes resources. It is a tool that streamlines installing and managing Kubernetes applications. Think of it like apt/yum/homebrew for Kubernetes.

Helm - The Kubernetes Package Manager

Telepresence substitutes a two-way network proxy for your normal pod running in the Kubernetes cluster. This pod proxies data from your Kubernetes environment (e.g., TCP connections, environment variables, volumes) to the local process. The local process has its networking transparently overridden so that DNS calls and TCP connections are routed through the proxy to the remote Kubernetes cluster. 
Telepresence, in conjunction with a containerized development environment, gives the developer a fast development workflow in developing a multi-container application on Kubernetes. Telepresence lets you run a Docker container locally, while proxying it to your Kubernetes cluster.

Telepresence substitutes a two-way network proxy for your normal pod running in the Kubernetes cluster. This pod proxies data from your Kubernetes environment (e.g., TCP connections, environment variables, volumes) to the local process. The local process has its networking transparently overridden so that DNS calls and TCP connections are routed through the proxy to the remote Kubernetes cluster.

Telepresence - Local development against a remote Kubernetes or OpenShift cluster

Kubernetes tail. Streams logs from all containers of all matched pods. Match pods by service, replicaset, deployment, and others. Adjusts to a changing cluster - pods are added and removed from logging as they fall in or out of the selection.With no arguments, kail matches all pods in the cluster. You can control the matching pods with arguments which select pods based on various criteria.

kail - kubernetes log viewer

Discover open source projects across all platforms

Projects