docs/k8s-storage/rwx_test.yaml

+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: rwx-test
+spec:
+  accessModes:
+    - ReadWriteMany
+  resources:
+    requests:
+      storage: 1Gi
+---
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: rwx-test
+  labels:
+    app: rwx-test
+spec:
+  replicas: 3
+  selector:
+    matchLabels:
+      app: rwx-test
+  strategy:
+    type: Recreate
+  template:
+    metadata:
+      labels:
+        app: rwx-test
+    spec:
+      containers:
+        - image: ubuntu:xenial
+          imagePullPolicy: Always
+          command: ["/bin/sh", "-c"]
+          args:
+            - sleep 30; touch /mnt/rwx-test/test.log; while true; do date >> /mnt/rwx-test/test.log; sleep 1; done;
+          name: rwx-test
+          stdin: true
+          tty: true
+          livenessProbe:
+            exec:
+              command:
+                - timeout
+                - "10"
+                - ls
+                - /mnt/rwx-test
+            initialDelaySeconds: 10
+            periodSeconds: 10
+            timeoutSeconds: 10
+          volumeMounts:
+            - mountPath: /mnt/rwx-test
+              name: rwx-test
+      restartPolicy: Always
+      volumes:
+        - name: rwx-test
+          persistentVolumeClaim:
+            claimName: rwx-test

docs/postrenderers.md

+# Post Renderers
+
+
+[Flux V2](https://toolkit.fluxcd.io/) provides the ability to apply kustomizations on a Helm Release after rendering using a [Post Renderer](https://toolkit.fluxcd.io/components/helm/helmreleases/#post-renderers).  This feature provides significant flexibility to the Helm objects, and allows for adjusting values inside of Helm that are not exposed explicitly as part of the values file.   Each `HelmRelease` is configured with a `postRenderer` pass through:
+
+
+```
+...
+jaeger:
+  postRenderers:
+    - kustomize:
+    # Array of inline strategic merge patch definitions as YAML object.
+    # Note, this is a YAML object and not a string, to avoid syntax
+    # indention errors.
+    patchesStrategicMerge:
+    # Change operator deployment to be a rolling update
+    - kind: Deployment
+      apiVersion: apps/v1
+      metadata:
+        name: jaeger-operator
+      spec:
+        strategy:
+          type: RollingUpdate
+    patchesJson6902:
+    # change priorityClassName
+    - target:
+        version: v1
+        kind: Deployment
+        name: jaeger-operator
+        patch:
+        - op: add
+            path: /spec/template/priorityClassName
+            value: system-cluster-critical
+    images:
+    # update image to a new tag
+    - name: registry1.dso.mil/ironbank/opensource/jaegertracing/jaeger-operator
+      newName: registry1.dso.mil/ironbank/opensource/jaegertracing/jaeger-operator
+      newTag: 1.23.0
+```
\ No newline at end of file

scripts/latest.sh

+#!/bin/bash
+
+# This script looks at all the deployed images from iron bank and identifies if the 
+# currently deployed version is the latest in IronBank.  Could be used as part of CI
+# or as general awareness for development
+
+# Needs crane( https://github.com/google/go-containerregistry/tree/main/cmd/crane )
+# to be configured before hand via
+
+# crane auth login -p ${REGISTRY1_CREDENTIALS} -u ${REGISTRY1_USER} registry1.dso.mil
+
+images=`kubectl get pods -A -o jsonpath="{..image}" | tr -s '[[:space:]]' '\n' | sort | uniq -c | grep "registry1" | awk '{ print $2 }'`
+
+
+for i in $images
+do
+    image=`echo "$i" | awk '{split($0,a,":"); print a[1] }'`
+    tag=`echo "$i" | awk '{split($0,a,":"); print a[2] }'`
+
+    upstream_tag=`crane ls $image | grep -v "latest" | sort -r | head -n1`
+    
+    if [[ "$tag" != "$upstream_tag" ]]
+    then
+        echo "Update for $image:  $tag ---->  $upstream_tag"
+    fi
+done
\ No newline at end of file

scripts/package/synker.yaml

@@ -41,8 +41,8 @@ source:
     - registry.il2.dso.mil/platform-one/devops/pipeline-templates/pipeline-job/anchore:0.8.2
     - registry.il2.dso.mil/platform-one/devops/pipeline-templates/pipeline-job/test:gcc
     - registry.il2.dso.mil/platform-one/devops/pipeline-templates/pipeline-job/dependency-check611-sonar-scanner45-dotnet-31:021921
-    # Gitlab Runner images
-    - registry1.dso.mil/ironbank/gitlab/gitlab-runner/gitlab-runner:v13.2.2
-    - registry.dso.mil/platform-one/big-bang/apps/developer-tools/gitlab-runner/gitlab-runner-helper:ib-v13.2.2
+    # gitlab-runner-helper image: This image does not get captured from the release deployment
+    # the gitlab-runner-helper image only gets pulled when a pipeline runs. So it must be listed here
+    - registry1.dso.mil/ironbank/gitlab/gitlab-runner/gitlab-runner-helper:v13.9.0
     # Don't include until fortify is supported
     #- registry.il2.dso.mil/platform-one/devops/pipeline-templates/pipeline-job/dotnet-fortify:20.2.0

tests/ci/k3d/values.yaml

@@ -340,6 +340,8 @@ addons:
 
   mattermost:
     enabled: false
+    elasticsearch:
+      enabled: true
     values:
       replicaCount: 1
       resources: