Fix native compiles not running on our AMD nodes

• Update OKD image policy to only pull if there's no copy in OKD

• Fix native compiles not running on our AMD nodes

As part of our roll out, one of our nodes attempted to start in an AMD-managed OKD node and failed to start. This is due to the build running in an Intel node that had access to the x86-64-v3 instruction set and compiling in that more efficient/modern standard. When attempting to start in AMD, this isn't available and fails to start.

See: https://quarkus.io/guides/native-reference#work-around-missing-cpu-features

src/main/k8s/production.yml

@@ -31,7 +31,7 @@ spec:
       containers:
       - name: api
         image: eclipsefdn/eclipsefdn-downloads-api:latest
-        imagePullPolicy: Always
+        imagePullPolicy: IfNotPresent
         ports:
         - containerPort: 8090
         resources: