-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
install nsm problem #11930
Comments
As far as I know, we started to use The problem is going from e541301 To fix it locally, you may play with volumeClaimTemplates:
- metadata:
name: spire-data
namespace: spire
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi Most likely, you might need to remove the request or storage or make sure that your cluster provider has this storage. |
Also, since NSM has backward compatibility, you may try: use spire from v1.11.0 and deploy nsm v1.13.0. I suppose it should be a quick workaround for now. |
As @denis-tingaikin mentioned you must fix it locally, for me i just edited the pvc that spire automatically created, and added the following line: storageClassName: openebs-hostpath. In your case instead of openebs-hostpath add your storage provisioner that you have configured in your cluster.
|
hi @glazychev-art
I install nsm v1.13.0-relase
first install spire, but it failed as followed:https://github.com/networkservicemesh/deployments-k8s/tree/release/v1.13.0/examples/spire/single_cluster
spire-server can not start
error log :
Warning FailedScheduling 46s default-scheduler 0/3 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling..
v1.11.0-relase version no problem
The text was updated successfully, but these errors were encountered: