Allow the nnf-mfu release to be specified.

[roehrich-hpe]

No description provided.

[roehrich-hpe]

Here's the NNFContainerProfile example resource that is installed as a result of this change:

$ kubectl get nnfcontainerprofiles -n nnf-system example-mpi -o yaml | grep image:
              image: ghcr.io/nearnodeflash/nnf-mfu:0.0.1
            - image: ghcr.io/nearnodeflash/nnf-mfu:0.0.1

[bdevcich]

Do you plan on doing this for nnf-dm as well? It's also used there for data movement. https://github.com/search?q=repo%3ANearNodeFlash%2Fnnf-dm%20mfu&type=code

[roehrich-hpe]

Do you plan on doing this for nnf-dm as well? It's also used there for data movement. https://github.com/search?q=repo%3ANearNodeFlash%2Fnnf-dm%20mfu&type=code

Well. Shoot.

[roehrich-hpe]

Here are the results with the newest nnf-dm, from PR NearNodeFlash/nnf-dm#106

$ kubectl get datamovementmanager -n nnf-dm-system   nnf-dm-manager-controller-manager -o yaml | grep -e image: -e name:
  name: nnf-dm-manager-controller-manager
        image: ghcr.io/nearnodeflash/nnf-mfu:0.0.1
        name: worker
        - name: NNF_NODE_NAME
        image: ghcr.io/nearnodeflash/nnf-dm:d6b3864f6026ba2a219c7d6d481f35df26cca031
        name: manager

$ docker inspect --format='{{json .Config.Labels}}' ghcr.io/nearnodeflash/nnf-dm:d6b3864f6026ba2a219c7d6d481f35df26cca031
{"nnf-mfu":"ghcr.io/nearnodeflash/nnf-mfu:0.0.1"}


$ kubectl get nnfcontainerprofiles -n nnf-system example-mpi -o yaml | grep image:                                       
              image: ghcr.io/nearnodeflash/nnf-mfu:0.0.1
            - image: ghcr.io/nearnodeflash/nnf-mfu:0.0.1