The edge proxy, commonly known as an ingress controller in Kubernetes, is typically configured using ingress resources. However, it can also be configured through custom resource definitions (CRDs) or annotations. These methods provide flexibility in defining how the edge proxy handles incoming traffic.