Vault operator is on evicted status and vault pods are in sealed mode again

Hi Team,
We launched the vault successfully in our pod env. we can see now vault operator pod is on evicted status and one more vault operator pod is created. And vault pods are on sealed status once again. we are getting the error like below.
what would be the next step and what can be the reason to get these error,
could you please help us on this issue?

evicted pods error:
The node was low on resource: ephemeral-storage. Container vault-operator was using 17512Ki, which exceeds its request of 0

Running pods logs :
{“level”:“error”,“ts”:1607875963.7520258,“logger”:“leader”,“msg”:“Leader pod could not be deleted.”,“error”:“pods “vault-vaul t-operator-b54cc55d8-wzfj9” is forbidden: User “system:serviceaccount:sedvip-prod:vault-vault-operator” cannot delete resou rce “pods” in API group “” in the namespace “sedvip-prod””,“stacktrace”:“github.com/go-logr/zapr.(*zapLogger).Error\n\tp kg/mod/github.com/go-logr/zapr@v0.1.1/zapr.go:128\ngithub.com/operator-framework/operator-sdk/pkg/leader.Become\n\tsrc/github. com/operator-framework/operator-sdk/pkg/leader/leader.go:132\ngithub.com/operator-framework/operator-sdk/pkg/helm.Run\n\tsrc/g ithub.com/operator-framework/operator-sdk/pkg/helm/run.go:148\ngithub.com/operator-framework/operator-sdk/cmd/operator-sdk/exe centrypoint.newRunHelmCmd.func1\n\tsrc/github.com/operator-framework/operator-sdk/cmd/operator-sdk/execentrypoint/helm.go:38\n github.com/spf13/cobra.(*Command).execute\n\tpkg/mod/github.com/spf13/cobra@v0.0.5/command.go:826\ngithub.com/spf13/cobra.(*Co mmand).ExecuteC\n\tpkg/mod/github.com/spf13/cobra@v0.0.5/command.go:914\ngithub.com/spf13/cobra.(*Command).Execute\n\tpkg/mod/ github.com/spf13/cobra@v0.0.5/command.go:864\nmain.main\n\tsrc/github.com/operator-framework/operator-sdk/cmd/operator-sdk/mai n.go:39\nruntime.main\n\t/home/travis/.gimme/versions/go1.13.8.linux.amd64/src/runtime/proc.go:203”}
{“level”:“info”,“ts”:1607875980.4054208,“logger”:“leader”,“msg”:“Operator pod with leader lock has been evicted.”,“leader”:“va ult-vault-operator-b54cc55d8-wzfj9”}

vault-pod logs:
2020-12-12T17:59:30.926Z [WARN] core: leadership lost, stopping active operation
2020-12-12T17:59:30.926Z [INFO] core: pre-seal teardown starting
2020-12-12T17:59:31.426Z [INFO] rollback: stopping rollback manager
2020-12-12T17:59:31.426Z [INFO] core: pre-seal teardown complete
2020-12-12T17:59:31.429Z [WARN] core.cluster-listener: no TLS config found for ALPN: ALPN=[req_fw_sb-act_v1]
2020-12-12T17:59:32.433Z [WARN] core.cluster-listener: no TLS config found for ALPN: ALPN=[req_fw_sb-act_v1]
2020-12-12T17:59:32.461Z [INFO] core: acquired lock, enabling active operation
2020-12-12T17:59:33.866Z [WARN] core.cluster-listener: no TLS config found for ALPN: ALPN=[req_fw_sb-act_v1]
2020-12-12T17:59:36.109Z [WARN] core.cluster-listener: no TLS config found for ALPN: ALPN=[req_fw_sb-act_v1]
{“level”:“warn”,“ts”:“2020-12-12T17:59:37.173Z”,“caller”:“clientv3/retry_interceptor.go:61”,“msg”:“retrying of unary invoker failed”,“target”/client-4be46879-93e7-4271-be84-07e080305e53/vault-etcd.sedvip-prod.svc.cluster.local:2379",“attempt”:0,“error”:“rpc error: code = DeadlineEx= context deadline exceeded”}
{“level”:“warn”,“ts”:“2020-12-12T17:59:37.463Z”,“caller”:“clientv3/retry_interceptor.go:61”,“msg”:“retrying of unary invoker failed”,“target”/client-4be46879-93e7-4271-be84-07e080305e53/vault-etcd.sedvip-prod.svc.cluster.local:2379",“attempt”:0,“error”:“rpc error: code = DeadlineEx= context deadline exceeded”}
2020-12-12T17:59:37.463Z [ERROR] core: error performing key upgrades: error=“error checking for key upgrades: context deadline exceeded”
2020-12-12T17:59:37.464Z [INFO] core: marked as sealed
2020-12-12T17:59:40.516Z [WARN] core.cluster-listener: no TLS config found for ALPN: ALPN=[req_fw_sb-act_v1]
2020-12-12T17:59:48.099Z [WARN] core.cluster-listener: no TLS config found for ALPN: ALPN=[req_fw_sb-act_v1]
{“level”:“warn”,“ts”:“2020-12-12T18:15:11.550Z”,“caller”:“clientv3/retry_interceptor.go:61”,“msg”:“retrying of unary invoker failed”,“target”/client-4be46879-93e7-4271-be84-07e080305e53/vault-etcd.sedvip-prod.svc.cluster.local:2379",“attempt”:0,“error”:“rpc error: code = Unavailablnsport is closing”}
{“level”:“warn”,“ts”:“2020-12-12T18:15:11.552Z”,“caller”:“clientv3/retry_interceptor.go:61”,“msg”:“retrying of unary invoker failed”,“target”/client-4be46879-93e7-4271-be84-07e080305e53/vault-etcd.sedvip-prod.svc.cluster.local:2379",“attempt”:1,“error”:“rpc error: code = Unauthenti etcdserver: invalid auth token”}
{“level”:“warn”,“ts”:“2020-12-12T18:15:11.697Z”,“caller”:“clientv3/retry_interceptor.go:61”,“msg”:“retrying of unary invoker failed”,“target”/client-4be46879-93e7-4271-be84-07e080305e53/vault-etcd.sedvip-prod.svc.cluster.local:2379",“attempt”:0,“error”:“rpc error: code = Canceled dt canceled”}
2020-12-12T18:15:11.697Z [INFO] core: stopping cluster listeners
2020-12-12T18:15:11.697Z [INFO] core.cluster-listener: forwarding rpc listeners stopped
2020-12-12T18:15:11.919Z [INFO] core.cluster-listener: rpc listeners successfully shut down
2020-12-12T18:15:11.919Z [INFO] core: cluster listeners successfully shut down
2020-12-12T18:15:11.933Z [INFO] core: vault is sealed

Note : we are using vault helm version 0.6.0.