Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-8061

Debezium Operator with a provided Service Account doesn't spin up deployment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 3.0.0.Alpha2
    • 3.0.0.Alpha1
    • debezium-operator
    • None
    • Moderate

      TLDR: When you give the operator a `serviceAccount: <account>` there is an issue with the dependent tree. With the reconcilePrecondition, it doesn't build the ServiceAccountDependent (not even read only) and then the RoleBinding doesn't prompt and neither does the Deployment.

      The CR is even marked as ready which is strange.

      Bug report

      For bug reports, provide this information, please:

      What Debezium connector do you use and what version?

      Doesn't matter

      What is the connector configuration?

      Just give it an existing serviceAccount, we use `serviceAccount: default`

      What is the captured database version and mode of deployment?

      Kubernetes

      What behavior do you expect?

      I'd expect that the role binds to the service account that is provided versus a managed SA and the Deployment actually reconciles properly.

      What behavior do you see?

      The RoleBinding and Deployment never spawn.

      Do you see the same behaviour using the latest released Debezium version?

      Yes

      Do you have the connector logs, ideally from start till finish?

      If anything is needed, I'm happy to provide additional logs from builds I have with extra logging added.

      How to reproduce the issue using our tutorial deployment?

      Just deploy any job with a custom SA.

              Unassigned Unassigned
              ryanvanhuuksloot Ryan van Huuksloot (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: