Home / Companies / HashiCorp / Blog / Post Details
Content Deep Dive

Secure Kubernetes ingress with HashiCorp Boundary

Blog post from HashiCorp

Post Details
Company
Date Published
Author
Ben Holmes
Word Count
3,803
Company Posts That Month
24
Language
English
Hacker News Points
-
Post removed?
No
Summary

Boundary` is a cloud-hosted identity-aware proxy that simplifies and secures least-privileged access to cloud infrastructure. It's an alternative to traditional Kubernetes Ingress Controllers, enabling secure external access to application content and components without compromising the security of either the platform or the application. By using `Boundary`, developers can create a Zero Trust architecture for their applications, ensuring that only authorized users have access to sensitive resources. The approach uses a self-managed deployment of Red Hat's OpenShift Container Platform as the Kubernetes platform, and HashiCorp Boundary to enable secure, controlled ingress to workloads hosted on Kubernetes. The `Boundary` worker is configured using a container image and a configuration file in the HashiCorp Configuration Language (HCL), which is presented to the running container in its Pod as a Kubernetes ConfigMap. This allows for easy deployment and management of `Boundary` workers within a Kubernetes cluster, improving the security posture of application content and components hosted within Kubernetes.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Kubernetes 54 1,704 191 78 +3%
Observability 1 1,174 230 78 +1%
Secrets Management 1 637 106 55 -28%
Zero Trust 1 101 10 7 -36%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.