Operators want serverless virtual node pools for a summer camp registration API and also selected flannel as the cluster network type. What does official OKE behavior imply?
Select an answer to reveal the explanation.
Short Explanation
Virtual nodes and flannel do not mix on the create-cluster path. Official flow: virtual node pools show up only with VCN-native networking. Choosing flannel removes the serverless worker option—so pick VCN-native if you want virtual pools.
Full Explanation
Official OKE behavior ties virtual node pools to VCN-native cluster networking. If operators select flannel as the network type, virtual node pools are not offered for that cluster—so a summer camp registration API cannot get serverless virtual pools on a flannel cluster. The networking choice at create time gates the serverless worker option. Flannel does not automatically upgrade a cluster to enhanced virtual nodes. Overlay networking and virtual nodes are not a free combo pack; flannel selection removes rather than enables virtual pools. Virtual node pools do not appear for every flannel cluster regardless of CNI. The CNI/network type is exactly what matters: VCN-native enables the option; flannel does not. Self-managed nodes do not convert flannel into VCN-native without recreating (or otherwise re-platforming) the cluster networking model. Joining extra instances does not rewrite the cluster's CNI type from overlay to VCN-native. Exam caveat: plan network type before create—many virtual-node and workload features assume VCN-native, and changing CNI later is not a casual toggle. Operational check: in cluster create options, select VCN-native if virtual pools are required, confirm the virtual node pool choice appears, and reject flannel when serverless virtual workers are a hard requirement for the registration API.