Endpoints are missed when creating many services fast about kpng HOT 11 CLOSED

Copied from the old repo

from kpng.

Restarting kpng fixes the problem.

from kpng.

from kpng.

I've found a bug that has a really high probability to have caused your issue (not a race condition though). It's worth trying again :)

from kpng.

No, still the same problem. Re-built on;

commit 95df644fd8750210c91bd6c938ca74ce768cbac0 (HEAD -> master, origin/master, origin/HEAD)
Author: Mikaël Cluseau <[email protected]>
Date:   Fri May 7 22:54:44 2021 +0200

    api2store: fix tls config build

Is there a kpng version command of some kind, showing version or git commit? If not, it should be IMHO.

from kpng.

I am testing dual-stack, with ipFamilies and ipFamilyPolicy here.
Is kpng and the nft backend prepared for that? Or am I tesing a Not-Implemented-Yet feature?

from kpng.

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

from kpng.

I think we need the test yaml definitions to move forward here.

from kpng.

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

from kpng.

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

from kpng.

@k8s-triage-robot: Closing this issue.

from kpng.