Ask Sendai

We are excited to announce the HashiCorp Terraform Enterprise Module Registry, a service catalog that provides organizations with a self-service workflow to provision any infrastructure. As organizations deploy more workloads in cloud, operations teams have to ensure that every team in the organization follows safe and efficient provisioning practices. This is best addressed with a service catalog with hardened infrastructure modules. This service catalog allows IT operators to codify, collaborate, and publish modular templates for provisioning cloud infrastructure that can be used by developers or other operators across large organizations.

It’s easy to run HashiCorp Terraform on your laptop and go wild managing your infrastructure. But what do you do when you start working on more complex arrangements in a large, complex organization? At that point, the problem is not scaling infrastructure, but scaling your working practices to support a large landscape of teams and applications as well as scalingyour workflows to enhance collaboration within your team and between teams.

Recently a question got asked on Hacker News that grabbed my attention. I wanted to know how others’ experience has been. At ACL, we have multiple Lambda functions that we heavily rely on, and we use Terraform to deploy them. It’s been working well for us, so I was curious to know how others have approached Lambda. However, it seemed that others were struggling: In short, I was left wondering “why don’t people simply use Terraform?

In this blog post, we’ll review some of the milestones achieved in latest etcd releases, and go over the future roadmap for etcd. Share your thoughts and feedback on features you consider important on the mailing list: [email protected]. In June 2014, Kubernetes was released with etcd as a backing storage for all master states. Kubernetes v0.4 used etcd v0.2 API, which was in an alpha stage at the time. As Kubernetes reached the v1.

Serverless is the latest innovation in cloud computing that promises to alter the cost-benefit equation for enterprises. As our CEO, Sid Sijbrandij says, ‘All roads lead to compute.’ There is a race among providers to acquire as many workloads from enterprises as possible, at the cheapest cost. The latter is where serverless comes in: serverless computing is an execution model in which the cloud provider acts as the server, dynamically managing the allocation of machine resources.

From the first .sketch file we created at Monzo, we’ve taken care to organise our design files very neatly. And as we’ve grown from a single designer to a team of 13, maintaining a sensible design environment has really paid off. It’s been helping us collaborate easily and stay organised, even as we’ve grown. Source: monzo.com

We come to you with a new Kublr release that brings more automation control for Kubernetes deployment and in multiple environments. Kublr 1.11 is here and we are about to take a closer look at all the new and shiny features. Kublris a Kubernetes ally that delivers an open, easy-to-use, enterprise-grade Kubernetes platform that’s not tied to a single cloud, PaaS or OS and today we welcome its new release.

Kubernetes is a remarkable success story: A container orchestration technology that made its first public appearance barely three years ago now plays a pivotal role at thousands of organizations that have adopted container-based application architectures. Perhaps the most amazing thing about Kubernetes, however, isn’t what it’s accomplishing today—it’s that we’re just getting started! If current trends hold, within a few more years we expect to see customers deploying container orchestration on a scale far surpassing how most organizations deploy it today.

The growth and innovation in the Kubernetes project, since it first launched just over four years ago, has been tremendous to see. In part 1 of my blog, I talked about how Red Hat has been a key contributor to Kubernetes since the launch of the project, detailed where we invested our resources and what drove those decisions. Today, that innovation continues and we are just as excited for what comes next.

Today, the Cloud Native Computing Foundation (CNCF) Technical Oversight Committee (TOC) voted to accept etcd as an incubation-level hosted project from KubeCon + CloudNativeCon Seattle. All Kubernetes clusters use etcd as their primary data store. As such, it handles storing and replicating data for Kubernetes cluster state and uses the Raft consensus algorithm to recover from hardware failure and network partitions. In addition to Kubernetes, Cloud Foundry also uses etcd as their distributed key-value store.