Comments (9)
Same as this https://stackoverflow.com/questions/55044486/waitforfirstconsumer-persistentvolumeclaim-waiting-for-first-consumer-to-be-crea
But the solution given is not working
from vault-helm.
Hello,
Can you provide the output to the following commands:
kubectl get storageclass
kubectl describe storageclass
kubectl get pvc
kubectl describe pvc
kubectl get pv
from vault-helm.
[root@node1-dev]# k get storageclass
NAME PROVISIONER AGE
local-storage kubernetes.io/no-provisioner 23h
[root@node1-dev]# k describe sc local-storage
Name: local-storage
IsDefaultClass: No
Annotations:
Provisioner: kubernetes.io/no-provisioner
Parameters:
AllowVolumeExpansion:
MountOptions:
ReclaimPolicy: Delete
VolumeBindingMode: WaitForFirstConsumer
Events:
[root@node1-dev]# kubectl get pvc
data-vault10-0 Pending local-storage 2m13s
[root@node1-dev]# k describe pvc data-vault10-0
Name: data-vault10-0
Namespace: default
StorageClass: local-storage
Status: Pending
Volume:
Labels: app.kubernetes.io/instance=vault10
app.kubernetes.io/name=vault
component=server
helm.sh/chart=vault-0.2.1
Annotations:
Finalizers: [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode: Filesystem
Mounted By: vault10-0
Events:
Type Reason Age From Message
Normal WaitForFirstConsumer 14s (x13 over 3m7s) persistentvolume-controller waiting for first consumer to be created before binding
[root@node1-dev]# k get pv
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
local-pv 10Gi RWO Retain Available local-storage 6m24s
from vault-helm.
In values.yaml I made entered these values
affinity: |
podAntiAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
- labelSelector:
matchLabels:
app.kubernetes.io/name: {{ template "vault.name" . }}
app.kubernetes.io/instance: "{{ .Release.Name }}"
component: server
topologyKey: kubernetes.io/node1
dataStorage:
enabled: true
# Size of the PVC created
size: 5Gi
# Name of the storage class to use. If null it will use the
# configured default Storage Class.
storageClass: local-storage
# Access Mode of the storage device being used for the PVC
accessMode: ReadWriteOnce
from vault-helm.
Is there any other value in values.yaml we need to modify?
from vault-helm.
I'm having the same problem. So happy to add values etc.
from vault-helm.
btw, if you change
dev: from false to true the pod comes up. All keys will be deleted upon restart but it's dev mode so...
from vault-helm.
Dev mode auto-initializes and unseals itself, so it will show a ready status. Standard and HA mode do not, they need to be initialized and unsealed before they become ready.
Dev mode also has no volume claims, so if there's a problem with storage, you won't see it in dev mode.
from vault-helm.
@amanchourasiya This issue seems to be related to the storage class being used and not Vault Helm itself. I haven't been able to track down what the issue with the storage class is because I cannot replicate it on my end. Can you provide more info about your environment? I'm not familiar with local-storage
storage class. Where can this be found?
from vault-helm.
Related Issues (20)
- Latest vault helm chart (0.27.0) does not work with GCPCKMS
- Add a way to create Secrets in the values.yaml
- allow to pin IPs of vault services HOT 3
- json formatted server config converts to a freak vault-config k8s secret which is both hcl and json HOT 1
- Chart prevents synchronisation with ArgoCD when using custom sync label HOT 3
- Add MutatingWebhookConfiguration rule scope
- Error: values don't meet the specifications of the schema(s) in the following chart(s): HOT 2
- Forbidden response when the vault-agent-injector is enabled in HA mode HOT 1
- Server side apply does not properly render volumeClaimTemplates
- Access denied to helm.releases.hashicorp.com HOT 2
- Test.dockerfile throwing an error while building. HOT 1
- Agent Injector on EKS is not working. HOT 4
- Prometheus metrics disappear in HA setup when all Vault pods are sealed
- Please release a new version of helm chart with the current vault versions HOT 4
- Ability to have top level label on StatefullSet
- Cannot use HOSTNAME env var in VAULT_API_ADDR env var
- helm value server.logLevel does not set the log level but just logs all entries using this value
- Sidecar agent in CSI can't estabish a TLS connection with an external vault using a custom CA
- Deploying vault on OCI gives seal type Shamir not OCIKMS HOT 1
- Tests Assert that HA Should not be able to set the dataStorage StorageClass
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 vault-helm.