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

In "all-component-tls" scenario, Pulsar function worker always have both non-TLS port and TLS port enabled #191

Open
yabinmeng opened this issue Apr 25, 2022 · 0 comments
Open

In "all-component-tls" scenario, Pulsar function worker always have both non-TLS port and TLS port enabled #191

yabinmeng opened this issue Apr 25, 2022 · 0 comments

Comments

@yabinmeng
Copy link

Using "all-component-tls" example values.yaml file, I can see that the function worker always have both ports enabled.

workerPort: "6750"
workerPortTls: "6751"

Also, the function worker Pod readiness probe is always checking against the non-TLS port:

% kubectl describe pod pulsar-function-0 | grep Readiness:
    Readiness:  tcp-socket :6750 delay=10s timeout=5s period=30s #success=1 #failure=3
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

No branches or pull requests
1 participant
@yabinmeng