Skip to content

docs: Update k8s startup port to be on same as liveness port #2519

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
Merged
hessjcg merged 1 commit into from
Dec 9, 2025
Merged

docs: Update k8s startup port to be on same as liveness port #2519

hessjcg merged 1 commit into from
Dec 9, 2025

Conversation

@Ryuheeeei
Copy link
Contributor

@Ryuheeeei Ryuheeeei commented Dec 6, 2025

What

This PR resolves #2473 .

It feels very unlikely that the /startup and /liveness routes are on different ports, but in the example one is referring to 9090 and the other 9801.
...
I expect this is probably a typo and the ports should be the same.

@Ryuheeeei Ryuheeeei requested a review from a team as a code owner December 6, 2025 06:28
@hessjcg hessjcg enabled auto-merge (squash) December 9, 2025 17:56
@hessjcg hessjcg merged commit 8bc5285 into GoogleCloudPlatform:main Dec 9, 2025
10 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@hessjcg hessjcg hessjcg approved these changes

Assignees

@hessjcg hessjcg

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Docs suggests /startup and /liveness routes are on different ports

2 participants

@Ryuheeeei @hessjcg