What’s New?
Web Application Acceleration
Application performance is pivotal. A common approach to boosting http-based apps is to use a web application accelerator also known as a caching HTTP reverse proxy.
Varnish Cache is a very fast caching HTTP reverse proxy. It stands in front of any HTTP server and caches the contents, improving delivery speeds with a factor of 300 - 1000x, architecture dependent.
Now kube-httpcache brings Varnish to Kubernetes as an open-source controller that is intended to be used between your regular Ingress controller and your application’s service. One of the key features in addition to its performance, is the flexibility of Varnish Configuration Language (VCL) which enables you to write policies on how incoming requests should be handled.
Let's say we want to remove the cookie for all objects in the /images directory of our web server, using VCL :
sub vcl_recv { if (req.url ~ "^/images") { unset req.http.cookie; }}Now, when the request is handed to the backend server there will be no cookie header.
Sounds great but also complicated? This is what we love doing, let’s chat and see how we can help. Learn all about Varnish on Kubernetes here.
Kubernetes 1.22 Ingress-NGINX 0.47.0 Support
The upcoming Kubernetes 1.22 release will remove several deprecated networking APIs that may impact on your Ingress-NGINX:
The networking.k8s.io/v1beta1 API version of IngressClass
All beta versions of Ingress: extensions/v1beta1 and networking.k8s.io/v1beta1
The networking Special Interest Group will continue supporting Kubernetes versions older than 1.22 with Ingress-NGINX version 0.47.0. Support for Ingress-NGINX will continue for six months after Kubernetes 1.22 is released.
Ingress-NGINX will have separate branches and releases of Ingress-NGINX to support this model, mirroring the Kubernetes project process. Future releases of the Ingress-NGINX project will track and support the latest versions of Kubernetes.
The team is currently in the process of upgrading ingress-nginx to support the v1 migration. To ensure no compatibility issues, update to the latest version of Ingress-NGINX; currently v0.47.0, which supports the stable APIs for Ingress and IngressClass.
You can keep up to date with the Ingress-NGINX latest here.
SLO Adoption and Usage in SRE
Organizations need well-thought out reliability targets and service level objectives (SLOs) that are measured by service level indicators (SLIs) - a quantitative measure of an aspect of the service in order to better realize the full benefits of Site Reliability Engineering (SRE).
Eliminate the inherent conflicts in change management and event handling that slow innovation and cause business to suffer with measurable goals detailed by SLOs. Understanding how well service meets expectations gleans valuable business insight.
SLO compliance can inform whether you invest in making your systems faster, more available, or more resilient. If your system consistently meets SLOs, you may invest engineering time on other priorities, such as new products or features.
Find the complete report here.
Our Latest Blog Post
Why is it so hard to hire for DevOps?
Useful Reading
Kubernetes README
An excellent resource for learning more about Kubernetes.Google Workspace Terraform Provider
Learn how to manage users, groups, and domains with Terraform in your Google Workspace.