...
This entry will cause changes you make to configure NBI to be overwritten when the NBI pod is updated and that portion from config: and the succeeding lines must be removed.
path: oom/kubernetes/nbi/templates/deployment.yaml
...
# application configuration config: loglevel: INFO logstashServiceName: log-ls logstashPort: 5044 cloudOwner: k8scloudowner4 k8sCloudRegionId: k8sregionfour k8sCloudOwner: k8scloudowner4 ecompInstanceId: OOM openStackRegion: k8sregionfour openStackVNFTenantId: aaaa
Note: This will disable NBI being able to orchestrate in RegionOne on VM's and only deploy CNF's on default k8sregionfour. If you don't use your k8s info and keep openstack options, options, leaving the In the NBI clode, there is an if statement for a variable public_net_id null in your request will default to the openstack values, and if you give it something else, it will use k8s values which if null selects RegionOne/CloudOwner, and k8sregionfour/k8scloudowner if not null. Overwriting ClowdOwner adn openStackRegion to the k8s values ensures NBI will orchestrate on the k8s cloud.
To recap, update the values in the confg section of the NBI values..yaml.
...