A Service is ClusterIP and you need a brief external test on node IPs without recreating the object from scratch. What change accomplishes that exposure style?
Select an answer to reveal the explanation.
Short Explanation
You can promote a ClusterIP Service to NodePort with a patch or edit—same object, new exposure style for that short external test. You’re flipping the type, not inventing a fake headless annotation or changing apiVersion theater.
Full Explanation
Service spec.type can be updated from ClusterIP to NodePort (or other types) so the same Service begins publishing a node port for external access. That is a normal field change via kubectl edit/patch/apply. Headless behavior uses clusterIP None, empty selectors do not publish node IPs as Endpoints, and apiVersion changes are not how NodePort exposure is enabled.