nfs-ganesha-server-and-external-provisioner: Chart version 1.6.0 doesn't have its image available

Since the release of version 1.6.0 a couple of hours ago, any install of the latest version of the chart is broken. The image k8s.gcr.io/sig-storage/nfs-provisioner:v4.0.8 is not available.

Currently, the available versions in the registry are:

[
  "v2.2.2",
  "v3.0.0",
  "v3.0.1"
]

Easiest workaround for us (and we should have been doing it from the start), was to pin the chart version to 1.5.0.

The pipeline of the repo on master seems to be broken on the “Build nfs-ganesha base container”, so it’s most likely due to that.

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 18
  • Comments: 19 (8 by maintainers)

Commits related to this issue

Most upvoted comments

Same issue with 1.7.0

i’ve installed prev version successfully:

helm install --version=1.5.0 nfs-provisioner nfs-ganesha-server-and-external-provisioner/nfs-server-provisioner -n nfs --wait
NAME: nfs-provisioner
LAST DEPLOYED: Sun Jan 22 16:06:45 2023
NAMESPACE: nfs
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
The NFS Provisioner service has now been installed.

A storage class named 'nfs' has now been created
and is available to provision dynamic volumes.

You can use this storageclass by creating a `PersistentVolumeClaim` with the
correct storageClassName attribute. For example:

    ---
    kind: PersistentVolumeClaim
    apiVersion: v1
    metadata:
      name: test-dynamic-volume-claim
    spec:
      storageClassName: "nfs"
      accessModes:
        - ReadWriteOnce
      resources:
        requests:
          storage: 100Mi

For now you could use my image: https://github.com/modzilla99/nfs-ganesha-server-and-external-provisioner/pkgs/container/nfs-ganesha-server-and-external-provisioner

image:
  repository: ghcr.io/modzilla99/nfs-ganesha-server-and-external-provisioner

I changed the container build context directory from . to bin in release-tools/build.make after that make build and make container worked. nfs-provisioner:latest was successfully built locally.

Changed build.make: https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner/compare/master...revant:nfs-ganesha-server-and-external-provisioner:build-nfs-provisioner?expand=1

It seems only the base image (which is named ghcr.io/kubernetes-sigs/nfs-ganesha:V4.0.8) is built in .github/workflows/docker-build.yml.

Will it need one step to build nfs-provisioner and another step to build the final image which copies bin/nfs-provisioner to the base image (as specified in deploy/docker/Dockerfile)? What will be the final image? k8s.gcr.io/sig-storage/nfs-provisioner or ghcr.io/kubernetes-sigs/nfs-ganesha? or anything else #117?

Finally the helm chart needs to change .Values.image if final image is set to any name other than k8s.gcr.io/sig-storage/nfs-provisioner.

@kvaps the https://github.com/kubernetes/org/pull/3976 has been merged.

Can you publish the images for us such that we can upgrade to versions after chart 1.5.0?

It seems CI-pipeline does not push actually docker image. Sorry, I have no enough time to solve this right now. If someone could take a look and make a fix, I’ll be happy to merge it.

Guys, any idea when this will be resolved?