Generate a default "DefaultNetworkOfferingforKubernetesService" for vpc networks

[kiranchavala]

The required feature described as a wish

Currently, when a user tries to launch a cks cluster with

vpc offering: Default VPC offering

Network offering: DefaultIsolatedNetworkOfferingForVpcNetworks

The following exception is thrown

logs

2025-11-06 05:17:38,627 WARN  [c.c.k.c.KubernetesClusterManagerImpl] (qtp170949260-462:[ctx-afc6786c, ctx-2824eb1b]) (logid:ee8299b1) Network offering: NetworkOffering {"id":13,"name":"DefaultIsolatedNetworkOfferingForVpcNetworks","trafficType":"Guest","uuid":"80ee050c-870a-4d15-ad8f-36784582dfa2"} has egress default policy turned off should be on to provision Kubernetes cluster
2025-11-06 05:17:38,650 INFO  [c.c.a.ApiServer] (qtp170949260-462:[ctx-afc6786c, ctx-2824eb1b]) (logid:ee8299b1) Kubernetes service has not been configured properly to provision Kubernetes clusters

Currently only the following default network offerings are present

Need to create a network offering for vpc which has egress rules allowed so that the cks deployment in a vpc works fine.

This can be helpful in automation

[weizhouapache]

@kiranchavala
I think the vpc tier does not support egress policy.
Even if there is a default vpc network offering for CKS, users still need to use default_allow ACL or so.

this seems more like a regression of #11528
the check on vpc network offering could be skipped, similar to #11735

quick workaround:

update network_offerings set egress_default_policy=1 where name='DefaultIsolatedNetworkOfferingForVpcNetworks';

[weizhouapache]

I can reproduce the issue on ACS 4.22.0.0
will create a fix