Using Consul Connect and Envoy to build a service mesh

Kube-gateway is a best practice for managing massive kubernetes clusters within ByteDance.

It is a layer 7 load balancing proxy specifically designed and customized for HTTP2 flow for kube-apiserver.

The goal is to provide flexible and stable flow governance solutions for massive large-scale kubernetes clusters (more than 1,000 nodes).

Bridge to Kubernetes extends the Kubernetes perimeter to your development computer allowing you to write, test, and debug microservice code while connected to your Kubernetes cluster with the rest of your application or services. You can simply run your code natively on your development workstation while connected to the Kubernetes cluster, allowing you to test your code changes in the context of the larger application.

Kubegres is a Kubernetes operator allowing to deploy one or many clusters of PostgreSql pods with data replication and failover enabled out-of-the box. It brings simplicity when using PostgreSql considering how complex managing stateful-set's life-cycle and data replication could be with Kubernetes.

Redis Operator creates/configures/manages redis-failovers atop Kubernetes.

configmap-reload is a simple binary to trigger a reload when Kubernetes ConfigMaps or Secrets, mounted into pods, are updated. It watches mounted volume dirs and notifies the target process that the config map has been changed. It currently only supports sending an HTTP request, but in future it is expected to support sending OS (e.g. SIGHUP) once Kubernetes supports pod PID namespaces.

PostgreSQL operator for Kubernetes

Infisical is an open-source, end-to-end encrypted platform for secret management: sync secrets across your team/infrastructure and prevent secret leaks.

What is Terraform Drift? What problems does it cause? And how can we fix it?

When working locally with the AWS CLI or with Terraform or Terragrunt, you will require a valid AWS configuration to be authorised to communicate with AWS services.

It is recommended to leverage features such as Single Sign-On (SSO) and Role Based Access Controls (RBAC) when using your identity as the principal for interacting with AWS services.

Using SSO ensures that you are not storing a permanent access key and secret access key and that your sessions have a limited lifetime. Using permission sets (a form of RBAC) ensures that you create roles with only the minimum required permissions for relevant accounts and assume them when needed. This is one aspect of implmenting the principle of least privilege (PoLP).

In this guide it is assumed that you are making use of IAM Identity Center and that you are configured as a user. You should also have access to one or more accounts using permission sets. This guide will walk through accessing at least two accounts using the same login.

In this blog post, we’ll talk about two incident management structure models — distributed and centralized, including the pros and cons of each, and examples of what each structure looks like in our community.

PostgreSQL (Postgres), is a powerful relational database that can store a wide range of data types and data structures. When it comes to storing graph data structures we might reach for a database marketed for that use case like Neo4J or Dgraph. Hold your horses! While Postgres is not generally thought of when working with graph data structures, it is perfectly capable to store and query graph data efficiently.

Get sign off on the tools you need, by making a business case that resonates.

Typically, microservice-based applications distribute data widely, especially in cloud-based applications, resulting in distributed applications. This impacts the transactions within these applications. This white paper refreshes the concepts of classical and distributed transactions. Next, we explain how cloud-based applications are affected by distribution. Finally, we present compensation-based transactions as a reliable method for microservice-based application transactions, even in the cloud.