[redhat-3.13] blocker: fixing recursed accumulation of path for manag…

…ed clair resources (PROJQUAY-7993) (#970)

The scale-down component was never rendered because of the incorrect path.
The clair-postgres and clair-app needed to scale back after the postgres upgrade.

This change ensures following flow in the case where clair is managed:
- Scale down clair-app
- Scale down clair-postgres
- Upgrade clair-postgres
- Scale up clair-postgres
- Scale up clair-app

---------

Co-authored-by: Shubhra Deshpande <shubhrajayant+github.com>

kustomize/components/clairpgupgrade/scale-down-clair/clair-pg-scale-up.patch.yaml

@@ -0,0 +1,6 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: clair-app
+spec:
+  replicas: 2

kustomize/components/clairpgupgrade/scale-down-clair/clair.deployment-scale-up.patch.yaml

@@ -0,0 +1,6 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: clair-postgres
+spec:
+  replicas: 2

kustomize/components/clairpgupgrade/scale-down-clair/kustomization.yaml

@@ -2,5 +2,7 @@ apiVersion: kustomize.config.k8s.io/v1alpha1
 kind: Component
 patchesStrategicMerge:
   - ./clair.deployment.patch.yaml
-resources:
-  - "../base"
+  - ./clair-pg-scale-up.patch.yaml
+  - ./clair.deployment-scale-up.patch.yaml
+components:
+  - ../base

pkg/kustomize/kustomize.go

@@ -439,8 +439,9 @@ func KustomizationFor(
 	if ctx.NeedsClairPgUpgrade {
 		if v1.ComponentIsManaged(quay.Spec.Components, v1.ComponentClair) {
 			componentPaths = append(componentPaths, "../components/clairpgupgrade/scale-down-clair")
+		} else {
+			componentPaths = append(componentPaths, "../components/clairpgupgrade/base")
 		}
-		componentPaths = append(componentPaths, "../components/clairpgupgrade/base")
 	}
 
 	images := []types.Image{}