KubeOps
Ingress
Gateway Management

Ingress & Gateway Management #

BuildPiper simplifies the management of Ingress by providing a dedicated UI. A key feature of BP is the ability to easily define the Access Level of your application during setup.

On This Page

▸Public Ingress
▸Protected Ingress
▸Ingress Configuration
▸Workflow Accessing Ingress

1. Public Ingress #

Area	Details
Definition	These are internet-facing entry points.
Use Case	Used for the frontend of your application or APIs that need to be reachable by users or external systems across the globe.
BP Implementation	When you select “Public” in the BP UI, the platform automatically configures the Ingress with a public-facing Ingress Controller (like NGINX or AWS ALB) that has a public IP address.

BP Snapshot: Public Ingress configuration

2. Protected Ingress #

Area	Details
Definition	These are entry points restricted to a specific network, such as a VPN, a corporate office, or internal VPC.
Use Case	Used for internal dashboards (like Grafana or Jenkins), staging environments, or microservices that should only be accessed by developers and internal tools.
BP Implementation	Selecting “Protected” in the UI ensures that the Ingress is tied to an internal Ingress Controller. BP helps manage the security rules and annotations required to keep this traffic off the open web while still providing a friendly URL for internal team members.

Ingress Configuration #

Field Name	Mandatory Status	Description
Name	Yes	A unique identifier for the Ingress resource within the cluster.
Url	Yes	The external hostname/domain used to access the application (e.g., ingress-public.buildpiper.io).
Ingress Type	Yes	Selection between Public Access (internet-facing) or Protected Access (internal).
Ingress Class	Yes	Specifies the controller that should implement the Ingress (e.g., public, nginx).
Select Namespace	Yes	The Kubernetes namespace where the Ingress and target services are located.
Choose Ingress Setup Strategy	Yes	Choice between Guided Form (UI-based) or Upload Custom Ingress file / GitOps.
Do you want Access Control Management	No	Toggle to enable or disable integrated authentication and authorization.
Select Protocol	Yes	The network protocol for the traffic, such as HTTP, HTTPS, or GRPC.
Add Annotations	No	Custom metadata used to configure specific Ingress controller features.
Add Labels	No	Key-value pairs used for organizing and identifying Kubernetes objects.
Resource Quota Apply	No	Toggle to apply specific resource constraints to the Ingress resource.
Want your Ingress to be auto scalable?	No	Enables Horizontal Pod Autoscaling (HPA) for the Ingress controller pods.
Desired Replica Count	Yes	The fixed number of pods to run (visible and required when auto-scaling is disabled).

Once the ingress is deployed on the cluster, these ingress configurations will be visible to the user in the deployment configuration to use the required ingress to access the public and private services.

Workflow: Accessing Ingress #

Navigation Path
How to Access / Navigate

Final Step: Fill in the Ingress Creation Form → Hit Save.

Note: BP Ingress page is accessible only on the Admin Portal.

These ingress points decide if the application is exposed publicly or is available behind the VPN.

BuildPiper Documentation · Ingress & Gateway Management

Last updated: June 2026