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

Task: Use service names instead of pod_name #64

Closed
ridoo opened this issue Sep 4, 2023 · 0 comments · Fixed by #151
Closed

Task: Use service names instead of pod_name #64

ridoo opened this issue Sep 4, 2023 · 0 comments · Fixed by #151
Labels
enhancement New feature or request
Milestone

Comments

@ridoo
Copy link
Contributor

ridoo commented Sep 4, 2023

Task Description

Currently, pod_name is being used for deployed containers. In k8s context pods are volatile and could be replicated as well. We should use the service name for a given deployment. This would reduce the configuration pod_name boilerplate at several locations.

Also, IMO there is no need to make the name configurable. Is there a reason I do not see?

@mwallschlaeger mwallschlaeger added this to the release 1.1.0 milestone Sep 12, 2023
@mwallschlaeger mwallschlaeger added enhancement New feature or request 1.1.0 labels Sep 12, 2023
ridoo added a commit that referenced this issue Feb 27, 2024
…s_instead_of_pod_name

[Fixes #64] Task: Use service names instead of pod_name
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants