BattaniNetworking and port forwarding
Inspect Services, Ingresses and network policies, and open temporary port-forwarding sessions.
How requests reach an application
Networking provides separate views for Services, Ingresses, Endpoints, IngressClasses and NetworkPolicies. Resource details and YAML tools help explain which services and Pods sit behind an external address.
- Inspect Service ports and targets, and Ingress host/path rules.
- Check the targets behind a Service through Endpoints.
- Review IngressClass and NetworkPolicy definitions.
- Create, list and close port-forwarding sessions.
Check an unreachable service
- Find the Service in its namespace and check its ports and selector.
- Verify that Endpoints contains the expected Pod targets.
- For external access, inspect the Ingress and IngressClass definitions.
- If needed, start an authorized temporary port forward and use the supplied connection details; close the session after testing.
The role of cluster components
Ingress rules need an appropriate Ingress controller, and network policies need a networking plugin that enforces them. Battani displays resources and submits authorized operations; installing those components is a separate infrastructure task.
Port forwarding is not a permanent publishing mechanism. Reachability depends on the Battani server’s network location and session configuration.