docs: remove redundant namespace from HTTPRoute, Ingress, and ApisixRoute examples in configure-routes.md

[fengqi-dev]

Type of change:

• Bugfix
• New feature provided
• Improve performance
• Backport patches
• Documentation
• Refactor
• Chore
• CI/CD or Tests

What this PR does / why we need it:

This pull request makes minor updates to the documentation in docs/en/latest/getting-started/configure-routes.md by removing the namespace: ingress-apisix field from several Kubernetes resource examples.

apisix-ingress-controller/examples/httpbin/deployment.yaml

Lines 60 to 63 in 878e501

	apiVersion: v1
	kind: Service
	metadata:
	name: httpbin

Pre-submission checklist:

• Did you explain what problem does this PR solve? Or what new features have been added?
• Have you added corresponding test cases?
• Have you modified the corresponding document?
• Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first

[Copilot]

Pull request overview

This PR updates the getting-started routing documentation to avoid repeating the ingress-apisix namespace in example manifests, aligning the examples with the earlier prerequisite step that sets the kubectl context namespace.

Changes:

• Removed metadata.namespace: ingress-apisix from the HTTPRoute example.
• Removed metadata.namespace: ingress-apisix from the Ingress example.
• Removed metadata.namespace: ingress-apisix from the ApisixRoute example.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[kayx23]

I don't think this change is safe as-is. Removing metadata.namespace here changes behavior, not just style.

For the HTTPRoute example, the doc defines the Gateway in ingress-apisix earlier in the same guide. If httpbin-route.yaml is applied without an explicit namespace, it will be created in the user's current namespace, so parentRefs: - name: apisix may no longer refer to the Gateway in ingress-apisix. That can break the Gateway API walkthrough.

The same issue applies to the Ingress and ApisixRoute examples: without metadata.namespace, the examples become dependent on the user's current kubectl context. The guide currently does not set a default namespace and does not use -n ingress-apisix when applying the route manifest.

I think we should either:

1. keep the explicit namespace: ingress-apisix in these examples, or
2. update the whole walkthrough to set/apply a namespace consistently (kubectl config set-context --current --namespace=ingress-apisix or kubectl apply -n ingress-apisix ...).

Right now this PR makes the docs less explicit and potentially incorrect for the Gateway API case.