Commit dd015393 authored by Sergio Gimenez's avatar Sergio Gimenez
Browse files

Fix kubeconfig variable to support both playbook and scenario usage 

The federation_manager_kubeconfig variable now falls back to kubeconfig_output_dir
if kind_config_dir is not defined. This allows the roles to work in both scenarios:

- Playbooks (deploy.yml): Set kind_config_dir in pre_tasks
- Scenarios (deploy_quick_single_oop.yml): Only set kubeconfig_output_dir

Tested with deploy_quick_single_oop.yml - all components deployed successfully.
parent a93a415e

ansible/roles/federation-manager-remote/defaults/main.yml

+2 −1
Original line number Diff line number Diff line
@@ -11,7 +11,8 @@ remote_federation_manager_state: present 
remote_federation_manager_namespace: "federation-manager-remote"



# Kubeconfig

remote_federation_manager_kubeconfig: "{{ kubeconfig_output_dir }}/{{ kubeconfig_filename }}"

# Supports both kind_config_dir (from playbooks) and kubeconfig_output_dir (from scenarios)

remote_federation_manager_kubeconfig: "{{ kind_config_dir | default(kubeconfig_output_dir) }}/{{ kubeconfig_filename }}"



# ==========================================

# Remote Federation Manager Image

ansible/roles/federation-manager/defaults/main.yml

+2 −1
Original line number Diff line number Diff line
@@ -10,7 +10,8 @@ federation_manager_state: present 
federation_manager_namespace: "federation-manager"



# Kubeconfig

federation_manager_kubeconfig: "{{ kind_config_dir }}/{{ kubeconfig_filename }}"

# Supports both kind_config_dir (from playbooks) and kubeconfig_output_dir (from scenarios)

federation_manager_kubeconfig: "{{ kind_config_dir | default(kubeconfig_output_dir) }}/{{ kubeconfig_filename }}"



# ==========================================

# Federation Manager Image