Search Results for "read"

A tool for converting Kubernetes API Objects (in YAML format) into HashiCorp's Terraform configuration language.

Making SLOs with Prometheus manageable, accessible, and easy to use for everyone. When running Pyrra outside of Kubernetes, the SLO object can be provided through a YAML file read from the file system. For this, one container or binary needs to be started with the API argument and the reconciler with the filesystem argument. Here, Pyrra will save the generated recording rules to disk where they can be picked up by a Prometheus instance. While running Pyrra on its own works, there won't be any SLO configured, nor will there be any data from Prometheus to work with. ...

A highly optimized, easy-to-use, auto-upgradable, HA-default & Load-Balanced, Kubernetes cluster powered by k3s-on-MicroOS and deployed for peanuts on Hetzner Cloud. Hetzner Cloud is a good cloud provider that offers very affordable prices for cloud instances, with data center locations in both Europe and the US. This project aims to create a highly optimized Kubernetes installation that is easy to maintain, secure, and automatically upgrades both the nodes and Kubernetes. We aimed for...

Maintainable configuration files. Navigate to each package's directory for their respective READMEs. You can download pre-built binaries for Windows, OS X and Linux on the release page. You can then click the "Help" button in the bottom right corner, which will show you a nix-env command that you can run to install the prebuilt executable. You will probably want to use the shared caches hosted at cache.dhall-lang.org and dhall.cachix.org when doing Nix development. This is not required, but...

...The system speaks registry protocols and understands layered image formats, resolving whiteouts and overlays so the mounted view matches what a container runtime would see. A FUSE (or platform-equivalent) frontend makes it trivial to integrate with existing tools: compilers, test runners, or debuggers can read files as if they were local. This lazy, verified access pattern is especially valuable in CI and developer workflows where you inspect or compile a few files from a massive base image. By treating registries as a read-only filesystem, CRFS turns image artifacts into first-class, quickly accessible build inputs.