Skip to content
EOL Watch
Search itemsOpen menu

OCIBreaking change

Kubernetes Engine: CreateCluster API requires endpointConfig.subnetId, new clusters must be VCN-native

From 30 Sep 2026, any call to the CreateCluster API that does not set the endpointConfig.subnetId attribute fails. The attribute, optional before, is now required, and new Kubernetes clusters must be VCN-native. Oracle's notice prints 28 Oct 2026 as the date in effect.

Breaking since , 30 Sep 2026

What breaks

The change impacts you if you have used the CreateCluster API to create clusters with public Kubernetes API endpoints that are not integrated into your VCN. Before this change, the CLI and the API could create such clusters because the endpointConfig.subnetId attribute was optional. After this change, the endpointConfig.subnetId attribute is required. As a result, you can only create Kubernetes clusters that are completely integrated with your VCN (VCN-native clusters). From 30 Sep 2026, any call to the CreateCluster API that does not set the endpointConfig.subnetId attribute fails because the required attribute is missing. The same notice prints 28 Oct 2026 in its "Date in Effect" field.

What to do

If you have custom scripts or Terraform scripts that use the CreateCluster API and do not set the endpointConfig.subnetId attribute, update these scripts to set the attribute. Scripts that set the attribute create VCN-native clusters. In a VCN-native cluster, worker nodes, load balancers, and the Kubernetes API endpoint are part of your VCN, and you can configure them as public or private.

Replacement

Not stated by vendor.

Sources

Last checked against this source on .

Found an error? Report it

The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published. How items are written

Last checked · Added · Changelog for this item