Skip to content

PulsarSQL coordinator liveness probe unauthorized #300

Open
@hyperevo

Description

The PulsarSQL liveness probe fails causing a crashloopbackoff. It fails because because presto requires authentication but the livenessprobe does not use authentication as seen here:

The presto service doesnt by defualt even require a password. just a username. This problem is fixed by adding the following to the liveness probe in the above link. This adds the base64 encoded username of "admin":

          httpHeaders:
            - name: Authorization
              value: Basic YWRtaW46

I can make a PR to add this in but I wanted to ask about it here first. Does anyone object to this solution? Another solution could be to set up actual authentication and handle that correctly.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions