Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PulsarSQL worker node readiness and liveness probes fail #87

Closed
robparrott opened this issue Dec 3, 2021 · 3 comments · Fixed by #97
Closed

PulsarSQL worker node readiness and liveness probes fail #87

robparrott opened this issue Dec 3, 2021 · 3 comments · Fixed by #97

Comments

@robparrott
Copy link

The readiness and liveness probes fail for the pulsarSQL worker nodes.

For example, from the pod in question:

pulsar@pulsar-sql-worker-84b789f6bc-wtztr:/pulsar/conf$ hostname -i
192.168.14.34

Calling the status endpoint as localhost fails:

pulsar@pulsar-sql-worker-84b789f6bc-wtztr:/pulsar/conf$ curl http://localhost:8090/v1/service/presto
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 404 Not Found</title>
</head>
<body><h2>HTTP ERROR 404 Not Found</h2>
<table>
<tr><th>URI:</th><td>/v1/service/presto</td></tr>
<tr><th>STATUS:</th><td>404</td></tr>
<tr><th>MESSAGE:</th><td>Not Found</td></tr>
<tr><th>SERVLET:</th><td>org.glassfish.jersey.servlet.ServletContainer-5f6e2ad9</td></tr>
</table>

</body>
</html>

As does calling the status endpoint via the pod IP:

pulsar@pulsar-sql-worker-84b789f6bc-wtztr:/pulsar/conf$ curl http://192.168.14.34:8090/v1/service/presto
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 404 Not Found</title>
</head>
<body><h2>HTTP ERROR 404 Not Found</h2>
<table>
<tr><th>URI:</th><td>/v1/service/presto</td></tr>
<tr><th>STATUS:</th><td>404</td></tr>
<tr><th>MESSAGE:</th><td>Not Found</td></tr>
<tr><th>SERVLET:</th><td>org.glassfish.jersey.servlet.ServletContainer-5f6e2ad9</td></tr>
</table>

</body>
</html>
@michaeljmarshall
Copy link
Member

@robparrott - thanks for the detailed issue report. I am looking into it now.

@michaeljmarshall
Copy link
Member

Update: I've reproduced the issue in my local environment using minikube and the latest released version of the helm chart 2.0.1 and a slightly modified version of examples/dev-values-sql.yaml for my values. I am investigating a fix. I will follow up on this tomorrow.

@michaeljmarshall michaeljmarshall mentioned this issue Dec 14, 2021
Merged
@michaeljmarshall
Copy link
Member

@robparrott - chart version 2.0.7 includes the fix for this issue. Please let us know if you encounter any other issues on the chart. Thanks!

pgier pushed a commit to pgier/datastax-pulsar-helm-chart that referenced this issue Jul 13, 2022
@miecio45
Add basic PSP and RBAC for core components (datastax#87)
667e634 
Add PSP and add/modify RBAC. I'm open for all discussion.

### Motivation

On clusters which use PSP and restrictive default policy pulsar cannot be installed, because it uses root user and requires writable container root directory. Additionally default RBAC for broker are too permissive (usage of ClusterRoleBinding) in my opinion.

### Modifications

Add PSP and RBAC for bookkeeper and autorecovery to add
exception to allow startup even in secure environment
where containers cannot access RW on root by default.

Add option for limiting broker ClusterRoleBinding
to single namespace by replacing to RoleBinding

### Verifying this change

- [x] Make sure that the change passes the CI checks.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Pulsar SQL] Fix liveness and readiness probes datastax/pulsar-helm-chart
2 participants
@robparrott @michaeljmarshall