为HashiCorp产品提供一流的 Kubernetes 支持
admin
2023-04-11 06:22:51
0次

OCT 23 2018 ANTHONY DAVANZO

As a follow-up to the HashiCorp Consul plus Kubernetes blog series, this blog highlights our recent work to provide first-class support for Kubernetes across HashiCorp product line.

In addition to making our products easier and more natural to use within Kubernetes, these integrations allow users to better work in environments shared with non-Kubernetes workloads. While it is easy to start a pure-Kubernetes environment, most deployments have to interact with external services running in cloud computing environments, on-premises data centers, and more. HashiCorp products such as Consul are designed for these heterogeneous environments enabling non-Kubernetes applications to seamlessly interact with Kubernetes applications.

HashiCorp Consul with Kubernetes
Consul recently released a new set of features to support first-class integration with Kubernetes. The official Helm Chart simplifies the deployment of Consul on Kubernetes. The auto-join and service catalog sync capabilities solve important cross-cluster challenges between both multiple Kubernetes clusters and non-Kubernetes services interacting with Kubernetes services. The sidecar injection and native proxy integration with Envoy can automatically enable secure pod communication via the Consul Connect capability.

In addition to enhanced features, the integration extends the scalability and simplicity of Consul to Kubernetes. Consul is a universal service mesh that can securely connect services within and beyond Kubernetes, creating a seamless experience.

HashiCorp Terraform with Kubernetes
HashiCorp Terraform has an official Kubernetes provider, which supports a broad and growing set of Kubernetes features. HashiCorp has recently taken over maintaining the Terraform Kubernetes provider, and are rapidly iterating with plans for improvements in the near future. We also recently made the Terraform Helm provider official, which can be used for deploying software packages to Kubernetes clusters.

We are also focused on improving integrations with native and managed deployments on public cloud environments. We recently announced launch-day support for Amazon’s EKS Elastic Container Service for Kubernetes (see here for EKS provider and getting started guide) and we had launch-day support for Azure’s managed Kubernetes AKS service (see here for the AKS provider).

We’re excited to see the community embracing our support— the Terraform Kubernetes Provider has been downloaded over 500,000 times since its release, with over 100,000 downloads in the last month alone. The Getting Started guide for the Kubernetes provider can be found here.

HashiCorp Vault with Kubernetes
HashiCorp Vault protects secrets used by Kubernetes systems and allows Kubernetes-based applications to perform common security and cryptography workflows using Vault. The Kubernetes Auth Method allows Kubernetes-based applications to authenticate against Vault, thereby allowing applications running on those pods to freely use Vault to manage secrets, provision dynamic access, and perform cryptographic operations.

HashiCorp Nomad and Kubernetes
HashiCorp Nomad and Kubernetes have some overlapping functionality, but also have opportunities to be used together in environments. While Nomad provides the workload orchestration and scheduling component for the HashiCorp product suite, Kubernetes takes more of a platform-like approach. Circumstances typically dictate which approach makes sense for a given organization. Nomad powers critical production workloads for many large financial and other organizations today. These organizations typically benefit from Nomad's native integrations with Consul and Vault as well as the operational similarity across the HashiCorp runtime tools. Together, these characteristics enable them to easily insert Nomad into their existing operational architectures. Nomad users also tend to benefit from key differentiators including:

Native support for legacy and non-containerized workloads
Native container scheduling that composes with other infrastructure
High performance batch processing
A number of organizations have chosen to run Nomad side-by-side with Kubernetes to leverage the differentiating characteristics of both tools.

Conclusion
Kubernetes is an important platform that is being widely adopted across the industry. At HashiConf, we're showing our commitment to supporting our customers make the most out of their investment in new approaches, like Kubernetes, as well as their legacy, non-containerized infrastructure and systems. Watch for additional Kubernetes support from our product suite in the weeks and months following HashiConf.

相关内容

热门资讯

空调连续工作多久需要停机休息 空调连续工作的时间取决于多个因素,包括空调的型号、功率、使用环境和维护情况等。一般来说,空调可以连续...
空调哪个符号是除湿的 空调除湿功能通常用一个水滴形状的符号表示。不同品牌和型号的空调遥控器可能会有所差异,但一般来说,除湿...
格力空调多长时间加一次氟利昂 1、一般情况下,空调对氟利昂的使用量是非常小的,所以在空调使用了四年左右的时候再考虑加也没问题。2、...
空调用多长时间需要加氟一次 一般情况下是五年。当出现以下这几种情况时,空调才需要加氟。1、空调的室内机和室外机各有两个接口,当接...
格调生活·C标思享荟:卡萨帝在... 9月12日的郑州龙湖金融岛,夜风轻拂,灯光璀璨。“C标时刻共传奇——卡萨帝思享荟暨20周年品牌盛典郑...
品牌价值破千亿、高端份额持续领... 9月12日,“C标时刻共传奇——卡萨帝思享荟暨20周年品牌盛典郑州站”在郑州龙湖金融岛举办。2026...
空调主板坏了修800还是换新的 空调主板坏了是修还是换新,需要考虑多个因素,以下是一些建议:1. 维修成本:如果维修费用较低,比如 ...
空调开多久需要休息多长时间 问题:空调开多久需要休息多长时间回答:1、在使用空调的过程中,一般空调开7~8个小时左右需要休息2~...
中央空调多长时间清洗一次 1、一般空调开机前清洗一次即可,空调开机中间时段再清洗一次,空调关机时清洗一次,这样比较合理。2、空...
中央空调氟利昂多久加一次 看空调制热和制冷程度,很多人的观点认为氟利昂必须一年放一次,其实这个观点是错误的,理解上面有点偏差,...