fix(orchestrator): add kube_vip group in inventory only when K8s functional groups are defined

[priti-parate]

Description of the Solution

Summary: Fixes kube_vip group being incorrectly added to orchestrator inventory when Kubernetes is not actually deployed. The kube_vip group is now only added when K8s functional groups (service_kube_*) are defined in the PXE mapping file, which is the definitive indicator that K8s should be deployed.

Changes

generate_inventories role

• Added validation to check if K8s functional groups exist in PXE mapping file before setting kube_vip
• Removed dependency on omnia_config.yml deployment flag for kube_vip determination
• Simplified logic to only check for service_kube_* functional groups in mapping data
• kube_vip is only set when both HA config exists AND K8s groups are present in mapping

orchestrator_inventory template

• Updated kube_vip_group conditional logic documentation
• Template now correctly handles undefined kube_vip variable

Files Changed

File	Change Type	Description
src/orchestrator/roles/generate_inventories/tasks/main.yml	Modified	Added K8s functional groups validation in mapping, simplified kube_vip conditions
src/orchestrator/roles/configure_ochami/templates/nodes/orchestrator_inventory.yaml.j2	Modified	Updated conditional logic for kube_vip_group

Testing

• Verified kube_vip group is NOT added when K8s functional groups are absent from PXE mapping
• Verified kube_vip group IS added when service_kube_* groups are present in mapping and HA config exists
• Verified template handles undefined kube_vip variable correctly

Backward Compatibility

• No breaking changes - only fixes incorrect behavior where kube_vip was added when it shouldn't be
• Existing deployments with K8s functional groups will continue to work as expected
• Deployments without K8s functional groups will no longer have spurious kube_vip entries