Updated image with Ganesha 6.x

[pat-s]

Given the outdated image included in the chart, I went ahead and built a fresh one: devxygmbh/nfs-server-provisioner (with the plan to keep it updated as new versions of Ganesha and Fedora are released).

Key changes:

• Uses Ganesha 6.2 (Oct 2024) instead of 4.0.8 (Aug 2022)
• Size: 100 MB vs 246 MB
• Built for amd64 & arm64
• Based on Fedora 40 (instead of 36)

I am using it with the existing chart and it works fine so far.

[Hi-Fi]

Hopefully #152 gets merged and images published as earlier ones from this repo. Otherwise it seems that forking would be only option if needing functionality that this repo's code offers.

[pat-s]

Even then, without an active maintainer the same state will occur shortly afterwards again.

For now you can use the linked image from OP (using it without issues since then). The chart itself still works as is.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[pat-s]

/remove-lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[pat-s]

/remove-lifecycle stale