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

[Bug]: Tenant CN is considered as shared CN since the label reconciliation is async #360

Closed
1 task done
aylei opened this issue May 18, 2023 · 0 comments
Closed
1 task done
Assignees
Labels
kind/bug Something isn't working

Comments

@aylei
Copy link
Contributor

aylei commented May 18, 2023

Is there an existing issue for the same bug?

  • I have checked the existing issues.

Environment

  • Version or commit-id (e.g. v0.1.0 or 8b23a93): latest
  • Hardware parameters:
  • OS type:
  • Others:

Actual Behavior

When add scale-out new CNs with certain labels, since the label reconciliation is async, the CN is shortly considered as "NO LABEL" and can be used by other clients.

企业微信截图_164b684c-4625-4ddf-97b0-227aa117a122

Expected Behavior

CN should not accept connections before its label is properly synced.

Steps to Reproduce

No response

Additional information

No response

@aylei aylei added the kind/bug Something isn't working label May 18, 2023
@aylei aylei self-assigned this May 18, 2023
@aylei aylei closed this as completed Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant