Debezium platform with external database standalone server pod is not created [DBZ-9325]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 9
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-9325](https://issues.redhat.com/browse/DBZ-9325)
h2. Description
when using external database the standalone server pod/replicaset is not created after creating a pipeline.
recreate environment:
{code:java}
helm repo add debezium https://charts.debezium.io
helm upgrade --install debezium debezium/debezium-platform --version 3.2.0-final -n playground --create-namespace -f values.helm.yml {code}
values.helm.yml:
{code:java}
domain:
url: dbz.my.sv
database:
enabled: false
name: debezium
host: postgresql.infra
auth:
existingSecret: debezium-postgresql # <---- a secret {code}
secret.yml
{code:java}
apiVersion: v1
kind: Secret
metadata:
name: debezium-postgresql
namespace: playground
type: Opaque
data:
username: cG9zdGdyZXM=
password: cG9zdGdyZXM= #<---- base64(postgres) {code}
Contributor guide
Research direction
Start by reproducing the deployment with the supplied helm repo, helm upgrade command, and values.helm.yml using database.enabled: false and the external PostgreSQL secret.yml. Confirm the pipeline creation behavior and trace why the standalone server pod or ReplicaSet is absent; done means it is created when the external database configuration is used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100