chore: redis as Deployment, not StatefulSet.

[tadeusz-delphai]

No description provided.

[anton-delphai]

Did you test it? Is it that transparent change?
Will it apply newer chart to existing releases?

[tadeusz-delphai]

Did you test it? Is it that transparent change?
Will it apply newer chart to existing releases?

This definitely deserves some QA in review.

[tadeusz-delphai]

A test version of the page-scraper service got deployed in the review cluster.

$> kubectl get deployments -n page-scraper -l app.kubernetes.io/name=redis
NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
page-scraper-test-redis-deployment-master   1/1     1            1           18m

[tadeusz-delphai]

Did you test it?

Yes, @hennadii-delphai and I tested it in review. There's a page-scraper-test-redis-deployment release in the review environment. It works just fine.

Is it that transparent change?

It's as transparent as any new version of the delphai-deployment Helm Chart, e.g. #58 . There'll be a new helm release deployed through the usual GitHub Actions CI mechanism.

Will it apply newer chart to existing releases?

For each of the affected services we'll trigger a re-release for the master branch.

[anton-delphai]

It's as transparent as any new version of the delphai-deployment Helm Chart, e.g. #58 . There'll be a new helm release deployed through the usual GitHub Actions CI mechanism.

I asked another thing. Is it possible to upgrade existing statefulset-based release to new one in place?