Ensure that all Helm charts are deployed in the cluster before
deploying the SriovNetwork. Deploying the SriovNetwork causes the
node to drain, which in turn causes the helm-controller to restart.
If the helm-controller is restarted while reconciling a HelmRelease,
it's possible the HelmRelease becomes stuck in a failed state.
Signed-off-by: Todd Malsbary <todd.malsbary@intel.com>
Change-Id: I1ec23f024707b936a0cd3c8bd3ff2b873de814a9
name: icn
wait: true
timeout: 10m
+ patches:
+ - patch: |
+ - op: add
+ path: /spec/healthChecks/-
+ value:
+ apiVersion: helm.toolkit.fluxcd.io/v2beta1
+ kind: HelmRelease
+ name: monitor
+ namespace: emco
+ - op: add
+ path: /spec/healthChecks/-
+ value:
+ apiVersion: helm.toolkit.fluxcd.io/v2beta1
+ kind: HelmRelease
+ name: services
+ namespace: emco
+ - op: add
+ path: /spec/healthChecks/-
+ value:
+ apiVersion: helm.toolkit.fluxcd.io/v2beta1
+ kind: HelmRelease
+ name: tools
+ namespace: emco
+ target:
+ kind: Kustomization
+ name: sriov-network-operator
+ namespace: kud