A municipal GIS renderer needs GPU shapes that managed and virtual pools do not offer. Which enhanced-cluster node option joins custom Compute instances to OKE?
Select an answer to reveal the explanation.
Short Explanation
Self-managed nodes are the specialty tool drawer: you create the Compute instance (GPU, specialized networking) and join it because managed/virtual pools do not offer that hardware. Use them when the GIS workload needs it—not as the default web-service pool.
Full Explanation
Official enhanced-cluster feature: self-managed nodes are Compute instances you create and join to the cluster for shapes or images managed and virtual pools do not provide (for example GPU). They are for specialized hardware needs, not the default HTTP pool. Virtual nodes do not become GPUs via annotation, and Functions do not replace this OKE node option.