feat: refactor some to use PodSet

Signed-off-by: vsoch <vsoch@users.noreply.github.com>

Author: vsoch

examples/flux/lammps-train-job.yaml

@@ -11,7 +11,7 @@
 apiVersion: trainer.kubeflow.org/v1alpha1
 kind: TrainJob
 metadata:
-  name: lammps-flux-interactive
+  name: lammps-flux
 spec:
   # Reference the pre-defined runtime by name
   runtimeRef:
@@ -21,12 +21,8 @@ spec:
     image: ghcr.io/converged-computing/metric-lammps:latest
     # You do not need to write "flux run, etc" here. It will be wrapped
     command: ["lmp", "-v", "x", "2", "-v", "y", "2", "-v", "z", "2", "-in", "in.reaxc.hns", "-nocite"]
-    # Comment out the command above to make an interactive cluster! Then shell into the 0-0 pod:
-    #  # Source environment
-    #  . /mnt/flux/flux-view.sh
-    #  # Connect to the running lead broker socket
-    #  flux proxy $fluxsocket bash
-    #  # See Flux resources!
-    #  flux resource list
-    #  Run lammps!
-    #  flux run -N 4 -n 4 lmp -v x 2 -v y 2 -v z 2 -in in.reaxc.hns -nocite
+    # See flux-interactive.yaml for running the above interactively.
+    # This is how we match the view (operating system and verison) of the initContainer to install Flux
+    env:
+     - name: FLUX_VIEW_IMAGE
+       value: ghcr.io/converged-computing/flux-view-ubuntu:tag-jammy

manifests/base/manager/manager.yaml

@@ -23,6 +23,8 @@ spec:
       containers:
         - name: manager
           image: ghcr.io/kubeflow/trainer/trainer-controller-manager
+          # Uncomment for local development with kind
+          # imagePullPolicy: Never
           securityContext:
             readOnlyRootFilesystem: true
             allowPrivilegeEscalation: false