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.

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

The statefulset does not show the actual port being used after updating port of graphd in config #275

Closed
wenhaocs opened this issue Sep 14, 2023 · 0 comments · Fixed by #281
Assignees
Labels
affects/none PR/issue: this bug affects none version. process/fixed Process of bug severity/none Severity of bug type/bug Type: something is unexpected

Comments

@wenhaocs
Copy link

wenhaocs commented Sep 14, 2023

Please check the FAQ documentation before raising an issue

We update the default port of graphd from 9669 to 8080. But the statefulset does not reflect this when getting the yaml.

kubectl get statefulset <graphd set> -n <ns> -o yaml
image

The same to command kubectl describe pod <graphd pod> -n <ns>

Though now graphd is using 8080 port, the showing needs to be fixed.

@wenhaocs wenhaocs added the type/bug Type: something is unexpected label Sep 14, 2023
@github-actions github-actions bot added affects/none PR/issue: this bug affects none version. severity/none Severity of bug labels Sep 14, 2023
@kqzh kqzh mentioned this issue Sep 18, 2023
3 tasks
@github-actions github-actions bot added the process/fixed Process of bug label Sep 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects/none PR/issue: this bug affects none version. process/fixed Process of bug severity/none Severity of bug type/bug Type: something is unexpected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants