Firewall

A firewall profile is a reusable set of allow/deny rules you attach to public IP resources. Rules describe which traffic may enter or leave those addresses (TCP, UDP, or ICMP) so you can expose only the ports your applications need.
When to use it
- Restrict who can reach LoadBalancer VIPs or node public IPs
- Open specific application ports (for example 80/443 or a custom TCP port)
- Separate environments with different profiles (staging vs production)
Building blocks
- Profile: named collection of rules managed under Networking -> Firewalls
- Rules: direction (ingress/egress), protocol, ports, and source/destination
- Attachment: associate a profile with the public IPs that should enforce it
In the portal
- Open Networking -> Firewalls.
- Create a firewall profile with a clear name.
- Add rules that match your application traffic (prefer least privilege).
- Attach the profile to the relevant public IPs.
- Verify connectivity from your clients after changes propagate.
Avoid opening wide ranges of ports when a single service port is enough. Review profiles whenever you expose a new Service of type LoadBalancer.