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

Handle correctly duplicated headless services #7283

Closed
lukidzi opened this issue Jul 18, 2023 · 8 comments
Closed

Handle correctly duplicated headless services #7283

lukidzi opened this issue Jul 18, 2023 · 8 comments
Labels
kind/bug A bug triage/needs-reproducing Someone else should try to reproduce this

Comments

@lukidzi
Copy link
Contributor

lukidzi commented Jul 18, 2023

What happened?

As a followup to #6819 we should handle correctly issue when there are 2 or more headless services pointing to the same service. So far we are ignoring duplicates.
@lukidzi lukidzi added triage/pending This issue will be looked at on the next triage meeting kind/bug A bug labels Jul 18, 2023
@jakubdyszkiewicz jakubdyszkiewicz added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Jul 24, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Oct 23, 2023
@github-actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label Nov 3, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Feb 2, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Feb 2, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@slonka
Copy link
Contributor

slonka commented Feb 7, 2024

@lukidzi was this solved by #7282 ? if so please close

@slonka slonka removed the triage/stale Inactive for some time. It will be triaged again label Feb 7, 2024
@lukidzi
Copy link
Contributor Author

lukidzi commented Feb 19, 2024

I think that was a quick fix buy not full handling. We should validate it and improve

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label May 20, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label May 20, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Aug 19, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label Aug 19, 2024
@lahabana
Copy link
Contributor

What's the state of this with MeshService?

@lahabana lahabana added triage/pending This issue will be looked at on the next triage meeting and removed triage/accepted The issue was reviewed and is complete enough to start working on it labels Sep 19, 2024
@jakubdyszkiewicz jakubdyszkiewicz added triage/needs-reproducing Someone else should try to reproduce this and removed triage/pending This issue will be looked at on the next triage meeting labels Sep 23, 2024
@lobkovilya
Copy link
Contributor

Triage: we tried headless service with new MeshService and found only this #11513. Closing this issue.

@lobkovilya lobkovilya closed this as not planned Won't fix, can't repro, duplicate, stale Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug A bug triage/needs-reproducing Someone else should try to reproduce this
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@lahabana @slonka @jakubdyszkiewicz @lobkovilya @lukidzi