Search Results for "two"
Sort By:
Showing 12 open source projects for "two"
View related business solutions-
Earn up to 16% annual interest with Nexo.Generate interest, access liquidity without selling, and execute trades seamlessly. All in one platform. Geographic restrictions, eligibility, and terms apply.
-
Error to trace to log to deploy. One click. No SSH.AppSignal links every error to the trace, the trace to the log, the log to the deploy that shipped it.
-
1
kube-vip
Kubernetes Control Plane Virtual IP and Load-Balancer
kube-vip provides Kubernetes clusters with a virtual IP and load balancer for both the control plane (for building a highly-available cluster) and Kubernetes Services of type LoadBalancer without relying on any external hardware or software. ARP is a layer 2 protocol that is used to inform the network of the location of a new address. When a new IP address is configured to a device, there needs to be a mechanism to inform the network of which piece of hardware is hosting this new address. ARP is the technology that is used to ensure that a network understands the link between the hardware address (MAC) and the logical address (IP). -
2
s6-overlay
s6 overlay for containers (includes execline, s6-linux-utils
s6-overlay is an easy-to-install (just extract a tarball or two!) set of scripts and utilities allowing you to use existing Docker images while using s6 as a pid 1 for your container and process supervisor for your services. -
3
MetalLB
A network load-balancer implementation for Kubernetes
...If you’re not running on a supported IaaS platform (GCP, AWS, Azure…), LoadBalancers will remain in the “pending” state indefinitely when created. Bare-metal cluster operators are left with two lesser tools to bring user traffic into their clusters, “NodePort” and “externalIPs” services. Both of these options have significant downsides for production use, which makes bare-metal clusters second-class citizens in the Kubernetes ecosystem. MetalLB aims to redress this imbalance by offering a network load balancer implementation that integrates with standard network equipment. -
4
Kubernetes Provider for Terraform
Terraform Kubernetes provider
The Kubernetes (K8S) provider is used to interact with the resources supported by Kubernetes. The provider needs to be configured with the proper credentials before it can be used. Both backward and forward compatibility with Kubernetes API is mostly defined by the official K8S Go library (prior to 1.1 release) and client Go library which we ship with Terraform. Terraform providers for various cloud providers feature resources to spin up managed Kubernetes clusters on services such as EKS,... -
$300 Free Credits for Your Google Cloud ProjectsLaunch your next project with $300 in free Google Cloud credits—no strings attached. Test, build, and deploy without risk. Use your credits across the entire Google Cloud platform to find what works best for your needs. After your credits are used, continue with always-free tier services. Only pay when you're ready to scale. Sign up in minutes and start exploring.
-
5
CRI-O
Open Container Initiative-based implementation of Kubernetes Container
...If a Kubernetes release goes End of Life, then the corresponding CRI-O version can be considered in the same way. This means that CRI-O also follows the Kubernetes n-2 release version skew policy when it comes to feature graduation, deprecation or removal. This also applies to features that are independent of Kubernetes. Nevertheless, feature backports to supported release branches, which are independent from Kubernetes or other tools like cri-tools, are still possible. This allows CRI-O to decouple from the Kubernetes release cycle and have enough flexibility when it comes to implementing new features. ... -
6
Pixie
Instant Kubernetes-Native Application Observability
...Pixie uses eBPF to automatically collect telemetry data such as full-body requests, resource and network metrics, application profiles, and more. Pixie collects, stores and queries all telemetry data locally in the cluster. Pixie uses less than 5% of cluster CPU and in most cases less than 2%. PxL, Pixie’s flexible Pythonic query language, can be used across Pixie’s UI, CLI, and client APIs. -
7
youki
A container runtime written in Rust
...However, the container runtime requires the use of system calls, which requires a bit of special handling when implemented in Go. This is too tricky (e.g. namespaces(7), fork(2)); with Rust, it's not that tricky. And, unlike in C, Rust provides the benefit of memory safety. While Rust is not yet a major player in the container field, it has the potential to contribute a lot: something this project attempts to exemplify. youki has the potential to be faster and use less memory than runc, and therefore works in environments with tight memory usage requirements. ... -
8
Kubero
A free and self-hosted Heroku PaaS alternative for Kubernetes
Kubero [pronounced: Kube Hero] is a fully self-hosted Internal Developer Platform (IDP) that brings the workflows of Heroku to your Kubernetes cluster. It enables you to deploy your applications with a few clicks. It has a built-in CI/CD pipeline and supports multiple staging environments. Kubero initiates two containers: one for cloning your repository and another for building your app. Once the build is complete, Kubero will launch the final container and make it accessible via the configured domain. -
9
Why & When
Exposing the JDK Flight Recorder as a Spring Boot Actuator Endpoint
This is a Spring Boot 2 Starter exposing the JDK Flight Recorder as a Spring Boot Actuator Endpoint. Normally the JDK Flight Recorder is available locally or by JMX remote. Depending on your deployment scenario shell or JMX access might not be available for the application server. Here comes this handy starter into play! This starter adds a new Spring Boot Actuator endpoint for JDK Flight Recorder remote control. -
Our Free Plans just got better! | Auth0You asked, we delivered! Auth0 is excited to expand our Free and Paid plans to include more options so you can focus on building, deploying, and scaling applications without having to worry about your security. Auth0 now, thank yourself later.
-
10
M3
Distributed TSDB, Aggregator and Query Engine, Prometheus Sidecar
M3 is a Prometheus-compatible, easy-to-adopt metrics engine that provides visibility for some of the world’s largest brands. M3 is the obvious choice for Cloud Native companies looking to scale up their Prometheus-based monitoring systems. M3 can be used as Prometheus Remote Storage and has 100% PromQL compatibility. M3 was originally developed at Uber in order to provide visibility into Uber’s business operations, microservices, and infrastructure. With its ability to horizontally scale... -
11
Runtime Kubernetes
Kata Containers version 1.x runtime (for version 2.x
kata-runtime, referred to as "the runtime", is the Command-Line Interface (CLI) part of the Kata Containers runtime component. It leverages the virtcontainers package to provide a high-performance standards-compliant runtime that creates hardware-virtualized Linux containers running on Linux hosts. The runtime is OCI-compatible, CRI-O-compatible, and Containerd-compatible, allowing it to work seamlessly with both Docker and Kubernetes respectively. -
12
Awesome-Kubernetes
A curated list for awesome kubernetes sources
...The first unified container-management system developed at Google was the system we internally call Borg. It was built to manage both long-running services and batch jobs, which had previously been handled by two separate systems: Babysitter and the Global Work Queue. The latter’s architecture strongly influenced Borg, but was focused on batch jobs; both predated Linux control groups. Kubernetes is known to be a descendant of Google's system BORG. The awesome-Kubernetes will now soon be available in the form of different releases and package bundles, It means that you can download the awesome Kubernetes release up to a certain period of time. ...
- Previous
- You're on page 1
- Next
