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

Unexpected Automatic Creation of Network Endpoint Groups (NEG) on GKE #2581

Open
marsaultj opened this issue Jun 4, 2024 · 2 comments
Open
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@marsaultj
Copy link

We are experiencing an issue with our production environment on Google Kubernetes Engine (GKE) where Network Endpoint Group (NEG) resources are being automatically created for all our services deployed on our GKE cluster.

Adding the annotation cloud.google.com/neg: '{"ingress":false}' removes the NEG, but it is automatically recreated after 2 minutes by the neg-controller. The annotation is replaced by:

cloud.google.com/neg: '{"exposed_ports": ...}'
cloud.google.com/neg-status

We are using an external Network passthrough Load Balancer with an Istio ingress gateway, and we do not utilize NEGs.

This behavior is unexpected, especially since our test environment, which is built from the same deployment code, does not exhibit this phenomenon and no NEG resources are created automatically.

How can we explain this difference in behavior between two seemingly identical environments? Is there a way to completely disable the automatic creation of NEGs in GKE?

@swetharepakula
Copy link
Member

This is due to the preparation of migration of the control plane for CSM : https://cloud.google.com/service-mesh/docs/managed-control-plane-overview#control-plane-migration.

The automatic NEG creation is slowly being rolled out to all CSM enabled clusters which is likely the reason the test cluster is not exhibiting the same behavior as your production cluster.

If you have any more questions please open a Google Support Ticket with the topic as CSM. They will better be able to answer specific questions about your clusters and the state of the migration.

@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants