ksonnet is a framework for writing, sharing, and deploying Kubernetes application manifests. With its CLI, you can generate a complete application from scratch in only a few commands, or manage a complex system at scale.

Specifically, ksonnet allows you to:

Reuse common manifest patterns (within your app or from external libraries)
Customize manifests directly with powerful object concatenation syntax
Deploy app manifests to multiple environments
Diff across environments to compare two running versions of your app
Track the entire state of your app configuration in version controllable files

All of this results in a more iterative process for developing manifests, one that can be supplemented by continuous integration (CI).

Envoy is an L7 proxy and communication bus designed for large modern service oriented architectures. The project was born out of the belief that:

The network should be transparent to applications. When network and application problems do occur it should be easy to determine the source of the problem.

This is the last post in a 4-part series about Kubernetes monitoring. Part 1 discusses how Kubernetes changes your monitoring strategies, Part 2 explores Kubernetes metrics and events you should monitor, Part 3 covers the different ways to collect that data, and this post details how to monitor Kubernetes performance with Datadog.

This post is Part 3 of a 4-part series about Kubernetes monitoring. Part 1 discusses how Kubernetes changes your monitoring strategies, Part 2 explores Kubernetes metrics and events you should monitor, this post covers the different ways to collect that data, and Part 4 details how to monitor Kubernetes performance with Datadog.

This post is Part 2 of a 4-part series about Kubernetes monitoring. Part 1 discusses how Kubernetes changes your monitoring strategies, this post breaks down the key metrics to monitor, Part 3 covers the different ways to collect that data, and Part 4 details how to monitor Kubernetes performance with Datadog.

This post is Part 1 of a 4-part series about Kubernetes monitoring. Part 2 explores Kubernetes metrics and events you should monitor, Part 3 covers the different ways to collect that data, and Part 4 details how to monitor Kubernetes performance with Datadog.

These instructions will walk you through booting Container Linux via iPXE on real or virtual hardware. By default, this will run Container Linux completely out of RAM. Container Linux can also be installed to disk.

A mininum of 1024M of RAM is required to boot Container Linux via PXE.

Bootkube is a helper tool for launching self-hosted Kubernetes clusters.

When launched, bootkube will act as a temporary Kubernetes control-plane (api-server, scheduler, controller-manager), which operates long enough to bootstrap a replacement self-hosted control-plane.

Additionally, bootkube can be used to generate all of the necessary assets for use in bootstrapping a new cluster. These assets can then be modified to support any additional configuration options.

If you are interested in the design and details see the Kubernetes self-hosted design document which provides an architecture overview.

Tectonic is built on pure-upstream Kubernetes but has an opinion on the best way to install and run a Kubernetes cluster. This project helps you install a Kubernetes cluster the "Tectonic Way". It provides good defaults, enables install automation, and is customizable to meet your infrastructure needs.

Goals of the project:

Installation of Self-Hosted Kubernetes Cluster
Secure by default (use TLS, RBAC by default, OIDC AuthN, etcd)
Automatable install process for scripts and CI/CD
Deploy Tectonic on any infrastructure (Amazon, Azure, OpenStack, GCP, etc)
Runs Tectonic on any OS (Container Linux, RHEL, CentOS, etc)
Customizable and modular (change DNS providers, security settings, etc)
HA by default (deploy all Kubernetes components HA, use etcd Operator)

Note: This repo does not yet haveTectonic is built on pure-upstream Kubernetes but has an opinion on the best way to install and run a Kubernetes cluster. This project helps you install a Kubernetes cluster the "Tectonic Way". It provides good defaults, enables install automation, and is customizable to meet your infrastructure needs.

Goals of the project:

Installation of Self-Hosted Kubernetes Cluster
Secure by default (use TLS, RBAC by default, OIDC AuthN, etcd)
Automatable install process for scripts and CI/CD
Deploy Tectonic on any infrastructure (Amazon, Azure, OpenStack, GCP, etc)
Runs Tectonic on any OS (Container Linux, RHEL, CentOS, etc)
Customizable and modular (change DNS providers, security settings, etc)
HA by default (deploy all Kubernetes components HA, use etcd Operator)

Note: This repo does not yet have all Tectonic Installer features imported. This will happen over the coming weeks as we are able to make some of the surrounding infrastructure public as well. This notice will be removed once the AWS and Baremetal graphical installer code has been fully integrated.

Checkout the ROADMAP for details on where the project is headed. all Tectonic Installer features imported. This will happen over the coming weeks as we are able to make some of the surrounding infrastructure public as well. This notice will be removed once the AWS and Baremetal graphical installer code has been fully integrated.

Checkout the ROADMAP for details on where the project is headed.

This guide walks through a bare-metal installation of Tectonic utilizing PXE-based tools.

Simple, versatile, yours

Store, sync, and share your data just the way you want it.

So far, there are 1,082 pages in the MultimediaWiki. We would appreciate any knowledge you can contribute, for that is what the Wiki concept is all about. If you need help deciding what to write about, check the wanted pages for ideas.

Note that, due to spam and vandalism, you must have an account to edit this Wiki. Further -- again due to excessive automated spam and vandalism -- we have had to close general registration. If you would like to contribute, please contact Multimedia Mike for registration.

rkt (pronounced "rock-it") is a CLI for running app containers on Linux. rkt is designed to be composable, secure, and fast.

Some of rkt's key features and goals include:

• First-class integration with init systems (systemd, upstart) and cluster orchestration tools (fleet, Kubernetes)
• Compatibility with other container software (e.g. rkt can run Docker images)
• Modular and extensible architecture (network configuration plugins, swappable execution engines based on systemd or QEMU/KVM)

Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops.

Learn more about Rocket, CoreOS' new container runtime, and the first implementation of the App Container Specification. We will give you an overview of Rocket, show you a demo of Rocket live, provide more information on the App Container Specification and answer questions as they arise.