Configuration Forces Ingress upon us, let us use Gateway API

[MatthewKennedy]

Feature Request: Allow disabling Ingress to support external Gateway API management

Is your feature request related to a problem?

Yes. Currently, the operator automatically manages an Ingress resource. When trying to use the Gateway API, there is no clean way to prevent the operator from managing Ingress without potentially breaking the deployment or having the operator "reconcile" (overwrite) manual changes.

The Goal

I want to use the WordPress operator but I want to manage the external traffic routing myself using HTTPRoute resources.

Proposed Change

Add a toggle in the Custom Resource (CRD) to completely disable Ingress generation.

Example CRD Configuration:

spec:
  ingress:
    enabled: false  # This would tell the operator NOT to create an Ingress resource

Why this is better than the current workaround:

1. No Resource Conflict: Prevents the operator's reconciliation loop from recreating unwanted Ingress resources.
2. Gateway API Compatibility: Allows users to define an HTTPRoute that targets the Service created by the operator.
3. Separation of Concerns: The operator focuses on the WordPress lifecycle, while the cluster's Load Balancer/Gateway focuses on traffic.

Technical Requirement

For this to work effectively, the operator must ensure that the Service (ClusterIP) remains stable and predictable even when ingress.enabled is false, so that the manual HTTPRoute has a consistent backend ref to point to.