Smruti

[Update] Running the container once, before testing it, seems to solve the issue. ``` docker run --rm ${CONTAINER_REGISTRY}:${CI_PIPELINE_ID} php -v ``` Not sure about the root cause yet.

> Multiple KCQL statements can be provided to the connector to support multiple topics, separated by a semi-colon. For example: > > ``` > INSERT INTO kafka-backup:data1 SELECT * FROM...

**### Update** I replicated the data of a single topic to another bucket and the restore worked as expected. I deliberately didn't copy the `.indexes/` folder to the new bucket....

This is what I did ``` wget -v --tries=5 --wait=3 --retry-connrefused --continue --no-dns-cache https://deb.nodesource.com/node_10.x/pool/main/n/nodejs/nodejs_10.22.0-1nodesource1_amd64.deb dpkg -i nodejs_10.22.0-1nodesource1_amd64.deb apt-get install -f -yqq rm nodejs_10.22.0-1nodesource1_amd64.deb ```

> I see this after `vault operator init` on the other nodes, until they are restarted, then everything is as expected. I deploy a 3 node HA cluster to K8s...

This will definitely help.

Facing the same issue. ```bash bash-3.2$ helm list -n pure-pso NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION pure-pso pure-pso 1 2021-06-30 01:00:21.279272 +0200 CEST deployed pure-pso-6.1.1 6.1.1 bash-3.2$ kubectl...

Hi, Thanks for getting back to me. I am in the process of getting my support contract in order. In the meantime, I found that that the following feature-gate defaults...

Hi @dsupure , I understand that. If compatibility is really an issue though, the https://github.com/purestorage/pso-csi#environments-supported section, assuring support for v1.17+, is a bit confusing. I will get in touch with...