busyboy77

Up for this Issue.

and I am sure until they find who's fault was it, people will forget weave altogether on Kubernetes, my guess after seeing that weave was last updated about an year...

I'm also using `--set architecture=standalone ` so the option should take over the existing PVC/PV. using architecture as `standalone` and `useStatefulSet` at the same time should be negated then or...

disabling `useStatefulSet` doesn't make any sense. Its still going to create its own PVC/PV couple.

I have even disabled all architecture options and just relying on standard helm install with only `existingClaim` and it doesn't work, always creating a new PVC+PV

hi I'm not sure what is the way to open a PR . Can someone please guide me and I'll be happy to do that. Regards, NMR On Mon, Sep...

Even after applying this change recommended by [Jasper-Ben](https://github.com/Jasper-Ben) , my helm based deployment is still waiting for the LoadBalancer IP to be assigne. Doesn't this should also disable the Service.enable=false...

``` 2023/04/09 12:42:35.248 [server.go:2977] [HTTP] http: multiple response.WriteHeader calls 2023/04/09 12:43:44.505 [D] [server.go:2741] | 192.168.50.6| 404 | 542.493µs| nomatch| GET /index.yaml 2023/04/09 12:43:49.615 [main.go:16] I'm alive 2023/04/09 12:43:49.615 [chartmuseum.go:17] 0x890480...

@The-Judge If you can share the config used for adding custom secret. I'm facing the same issue and similarly getting confused with extraTLS etc. Can you please share a working...

my storageclass ```YAML apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: mayastor-replica-3 parameters: ioTimeout: "30" protocol: nvmf repl: "3" fsType: "xfs" provisioner: io.openebs.csi-mayastor ``` my DSP ``` NAME NODE STATE POOL_STATUS CAPACITY...