enabling k8s cluster

globals.yml

@@ -124,7 +124,7 @@ containerd_configure_for_zun: "yes"
 # Yet another way to workaround the naming problem is to create a bond for the
 # interface on all hosts and give the bond name here. Similar strategy can be
 # followed for other types of interfaces.
-network_interface: "eth1"
+network_interface: "enp2s0"
 
 # These can be adjusted for even more customization. The default is the same as
 # the 'network_interface'. These interfaces must contain an IP address.
@@ -135,7 +135,7 @@ network_interface: "eth1"
 #swift_replication_interface: "{{ swift_storage_interface }}"
 #tunnel_interface: "{{ network_interface }}"
 #dns_interface: "{{ network_interface }}"
-octavia_network_interface: "eth0"
+octavia_network_interface: "enp1s0"
 
 # Configure the address family (AF) per network.
 # Valid options are [ ipv4, ipv6 ]
@@ -154,7 +154,7 @@ octavia_network_interface: "eth0"
 # though an IP address can exist on this interface, it will be unusable in most
 # configurations. It is recommended this interface not be configured with any IP
 # addresses for that reason.
-neutron_external_interface: "eth2,eth0"
+neutron_external_interface: "enp3s0,enp1s0"
 neutron_bridge_name: "br-ex,br-lbaas"
 
 # Valid options are [ openvswitch, ovn, linuxbridge, vmware_nsxv, vmware_nsxv3, vmware_dvs ]
@@ -835,3 +835,8 @@ octavia_amp_network_cidr: "{LB_NETWORK}.0/24"
 
 # this is UDP port
 #hacluster_corosync_port: 5405
+
+########################
+# Magnum options
+#######################
+enable_cluster_user_trust: true