Comments (6)
build arm64
GOOS=linux GOARCH=arm64 go build -o deploy/docker/nfs-provisioner ./cmd/nfs-provisioner
cd deploy/docker/
docker build . -t omegazeng/nfs-provisioner:latest
docker push omegazeng/nfs-provisioner:latest
install
- nfs.yaml
# kubectl create ns nfs --context=xxx
# helm repo add kvaps https://kvaps.github.io/charts
# helm install nfs -n nfs kvaps/nfs-server-provisioner -f nfs.yaml --kube-context=xxx
replicaCount: 1
image:
repository: omegazeng/nfs-provisioner
tag: latest
pullPolicy: IfNotPresent
persistence:
enabled: true
storageClass: oci
size: 100Gi
resources:
limits:
cpu: 200m
memory: 256Mi
requests:
cpu: 100m
memory: 128Mi
kubectl create ns nfs --context=xxx
helm repo add kvaps https://kvaps.github.io/charts
helm install nfs -n nfs kvaps/nfs-server-provisioner -f nfs.yaml --kube-context=xxx
k get po -n nfs
NAME READY STATUS RESTARTS AGE
nfs-nfs-server-provisioner-0 1/1 Running 0 6m32s
k get sc
NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
nfs cluster.local/nfs-nfs-server-provisioner Delete Immediate true 175m
oci (default) oracle.com/oci Delete Immediate false 8d
oci-bv blockvolume.csi.oraclecloud.com Delete WaitForFirstConsumer false 8d
test
- test-dynamic-volume-claim.yaml
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: test-dynamic-volume-claim
spec:
storageClassName: "nfs"
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 100Mi
k apply -f test-dynamic-volume-claim.yaml
k get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
test-dynamic-volume-claim Bound pvc-28d1e8e4-ebe7-4f12-a0b8-42e99d913ecc 100Mi RWO nfs 10m
k get pv
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
ocid1.volume.oc1.phx.abyhqljsv43hgrbhwibnblhtg7myrf46gfd7yp4j5ialzxzftbw6i3g7qtba 100Gi RWO Delete Bound nfs/data-nfs-nfs-server-provisioner-0 oci 178m
pvc-28d1e8e4-ebe7-4f12-a0b8-42e99d913ecc 100Mi RWO Delete Bound default/test-dynamic-volume-claim nfs 8m35s
so good so far.
I will keep this issue open until official support for arm64.
from nfs-ganesha-server-and-external-provisioner.
https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner/tree/v3.0.0/deploy/docker/arm/Dockerfile
only arm32 v7
Hope to support arm64 v8
Thx!
from nfs-ganesha-server-and-external-provisioner.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs 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 or PR as fresh with
/remove-lifecycle stale
- Mark this issue or PR as rotten with
/lifecycle rotten
- Close this issue or PR with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
from nfs-ganesha-server-and-external-provisioner.
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs 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 or PR as fresh with
/remove-lifecycle rotten
- Close this issue or PR with
/close
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
from nfs-ganesha-server-and-external-provisioner.
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs 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:
- Reopen this issue or PR with
/reopen
- Mark this issue or PR as fresh with
/remove-lifecycle rotten
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
from nfs-ganesha-server-and-external-provisioner.
@k8s-triage-robot: Closing this issue.
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs 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 closedYou can:
- Reopen this issue or PR with
/reopen
- Mark this issue or PR as fresh with
/remove-lifecycle rotten
- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
from nfs-ganesha-server-and-external-provisioner.
Related Issues (20)
- Changing mountOptions HOT 5
- Wanting to maintain this if possible HOT 2
- k8s.gcr.io registiry will be frozen by 3rdApr-2023 HOT 4
- Issues when using more replicas! HOT 7
- Failed pull image (Helm chart) HOT 3
- nfs storage size modification impact HOT 6
- Performance issue on NFS provisioner 4.08 HOT 4
- v4.0.8 tag is missing HOT 6
- Extend the disk size of NFS share HOT 7
- Replace deprecated `set-output` command with environment file
- Issue with getting latest version of nfs-server-provisioner chart HOT 4
- How to specify namespace when installing nfs-server-provisioner as sub-chart HOT 7
- How to export and mount pvc for nfs-ganesha to different cluster pv and pvc HOT 5
- Pods stucks sometime in Terminating status HOT 5
- Question: Backing up data by NFS - permission issues? HOT 1
- ESTALE 116 Error HOT 4
- Unable to add labels to nfs-server-provisioner pod when installed as helm subchart HOT 4
- Issue with nfs-ganesha-server-and-external-provisioner HOT 4
- Extremely poor perfomance with WSL2/Docker Desktop/k8s HOT 2
- Is Project maintained? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nfs-ganesha-server-and-external-provisioner.