What is Porter?
Take everything you need to do a deployment, the application itself and the entire process to deploy it: command-line tools, configuration files, secrets, and bash scripts to glue it all together. Package that into a versioned bundle distributed over standard Docker registries or plain tgz files.
Now anyone can install your application without deep knowledge of your deployment process, or following a step-by-step deployment doc, regardless of the tech stack.
Why Porter?
Single command to find and deploy any application, regardless of the tech stack. No knowledge of the deployment process necessary.
Secure handling of secrets and credentials, integrated with industry standard secret stores.
Share the operational load of managing your team's deployments.
Works with and improves existing tools, such as bash, cloud CLIs, terraform and helm. You don't rewrite your existing deployments to start using Porter.
Reliable deployments because the client environment: cli versions, installed commands, configuration... is dependable and consistent.Use our Helm charts to set up Elasticsearch and Kibana on a Kubernetes cluster, secured by Search Guard.
I started reading this book around a week ago.
Kubernetes is a container orchestration system that can manage containerized applications across a cluster of server nodes. Maintaining network connectivity between all the containers in a cluster requires some advanced networking techniques. In this
Ifyou go around and ask for a Kubernetes expert, whoever responds to your call is definitely lying. They probably are an expert in one of the many components that make a Kubernetes cluster, but I bet you there is a complete section of Kubernetes they have not touched or even heard about.
Not saying that Kubernetes is complex without reason, because it has its reasons, but it is a complex beast.
Network controllers seems to be one of those components that only very few people know how they truly work, or at least I couldn’t find many during my search for answers, and once you decide on one, and get yours up and running, you pretty much forget about it.
At Blend, we make extensive use of Kubernetes on AWS to power our infrastructure. Kubernetes has many moving parts, and most of these components are swappable, allowing us to customize clusters to our needs. An important component of any cluster is the Container Network Interface (CNI), which handles the networking for all pods running on the cluster. Choosing the right CNI for each use case is critically important and making changes, once serving production traffic, can be painful. Blend had several problems with the CNI we initially chose (Weave), leading us to explore alternatives. We eventually decided to switch and in this post, we describe the challenges and solutions to migrating without downtime.
Zero configuration or integration required — just launch and go.
Weave Scope automatically detects processes, containers, hosts. No kernel modules, no agents, no special libraries, no coding. Seamless integration with Docker, Kubernetes, DCOS and AWS ECS.
Weave Scope automatically generates a map of your application, enabling you to intuitively understand, monitor, and control your containerized, microservices-based application.
A kubectl plugin that utilize tcpdump and Wireshark to start a remote capture on any pod in your Kubernetes cluster.
You get the full power of Wireshark with minimal impact on your running pods
The next level of chaos engineering is here! Kill pods inside your Kubernetes cluster by shooting them in Doom!
This is a fork of the excellent gideonred/dockerdoomd using a slightly modified Doom, forked from https://github.com/gideonred/dockerdoom, which was forked from psdoom.
This article assumes a basic knowledge of Docker. This is the first article in a series of posts called “Simplified”, where I take a look at systems that I think aren’t adequately explained in their own “getting started” documentation. Today, I’m taking a look at one of the most complicated systems I’ve used to date.
