CKS - Control and worker node service offerings are not populated when #14504

problem

CKS - Control and worker node service offerings are not populated when

versions

ACS 4.22.x and 4.23.0

The steps to reproduce the bug

1. Deploy a cks cluster with default settings > do not select anything in advance settings in the form

Check the database

mysql> select control_node_service_offering_id,worker_node_service_offering_id from kubernetes_cluster where id=16 \G;
*************************** 1. row ***************************
control_node_service_offering_id: NULL
 worker_node_service_offering_id: NULL
1 row in set (0.00 sec)

2. Deploy a cks cluster with default settings > select separate offering for control and worker node in advance settings

Check the database

mysql> select control_node_service_offering_id,worker_node_service_offering_id from kubernetes_cluster where id=15 \G;
*************************** 1. row ***************************
control_node_service_offering_id: 13
 worker_node_service_offering_id: 16
1 row in set (0.00 sec)

What to do about it?

There should be a record of the service offering in the database when a cks cluster has the default setting
compute offering

As this can lead to issues when scaling is performed on a cks cluster