aboutsummaryrefslogtreecommitdiffstats
path: root/kud/deployment_infra/emco/examples/values.yaml.example
diff options
context:
space:
mode:
authorTodd Malsbary <todd.malsbary@intel.com>2021-09-09 11:24:45 -0700
committerTodd Malsbary <todd.malsbary@intel.com>2021-09-15 09:40:39 -0700
commit6027abb96369a30e6ccd3f747f4029e36232c0af (patch)
treef9c5ed58c4737e5728b67280debbba4b2eb034dd /kud/deployment_infra/emco/examples/values.yaml.example
parent5aa8c4de9fd620ef42ac5bf73b62f76d80e713a0 (diff)
Fix KubeVirt and SR-IOV addon interaction
SR-IOV wants to drain the nodes during reconciliation of SriovNetwork resources, while KubeVirt wants to keep at least one instance running at all times via a PodDisruptionBudget. KubeVirt's behavior is not customizable, so split the addons into different composite apps that allow finer control of the instantiation order. Issue-ID: MULTICLOUD-1324 Signed-off-by: Todd Malsbary <todd.malsbary@intel.com> Change-Id: I15c5cec3ef524b0b1d60dc201e04157272cbe376
Diffstat (limited to 'kud/deployment_infra/emco/examples/values.yaml.example')
-rw-r--r--kud/deployment_infra/emco/examples/values.yaml.example46
1 files changed, 24 insertions, 22 deletions
diff --git a/kud/deployment_infra/emco/examples/values.yaml.example b/kud/deployment_infra/emco/examples/values.yaml.example
index 67944eb8..41e3cc82 100644
--- a/kud/deployment_infra/emco/examples/values.yaml.example
+++ b/kud/deployment_infra/emco/examples/values.yaml.example
@@ -7,31 +7,33 @@ DtcPort: 30483
ClusterProvider: kud
ClustersLabel: kud-cluster
Clusters:
-- KubeConfig: $KUBE_PATH
- Name: cluster
+ cluster:
+ KubeConfig: $KUBE_PATH
ProjectName: kud
LogicalCloud: kud
PackagesPath: $PWD/../output/packages
-AddonsApp: addons
-AddonsProfile: addons-profile
-AddonsDeploymentIntentGroup: addons-deployment-intent-group
-AddonsDeploymentIntent: addons-deployment-intent
-AddonsPlacementIntent: addons-placement-intent
-Addons:
-- multus-cni
-- ovn4nfv
-- node-feature-discovery
-- sriov-network-operator
-- qat-device-plugin
-- cpu-manager
-AddonResourcesApp: addon-resources
-AddonResourcesProfile: addon-resources-profile
-AddonResourcesDeploymentIntentGroup: addon-resources-deployment-intent-group
-AddonResourcesDeploymentIntent: addon-resources-deployment-intent
-AddonResourcesPlacementIntent: addon-resources-placement-intent
-AddonResources:
-- ovn4nfv-network
-- sriov-network
+# Each composite app will be contained in its own deployment intent
+# group. This is to enable instantiating the addons in a specified
+# order.
+CompositeApps:
+ addons:
+ Apps:
+ - kubevirt-operator
+ - cdi-operator
+ - multus-cni
+ - ovn4nfv
+ - node-feature-discovery
+ - sriov-network-operator
+ - qat-device-plugin
+ - cpu-manager
+ networks:
+ Apps:
+ - ovn4nfv-network
+ - sriov-network
+ kubevirt:
+ Apps:
+ - kubevirt
+ - cdi