blixt icon indicating copy to clipboard operation
blixt copied to clipboard
verified publisher icon kubernetes-sigs

Decide whether we keep the gRPC API?

Open shaneutt opened this issue 1 year ago • 3 comments

When we originally started this project the dataplane code included a Kubernetes controller that would pull configuration from the Kubernetes API, after the controlplane had updated the relevant resources. We switched to a gRPC API with a push mechanism which was originally intended to be an interim solution to improve the development experience, testing and debuggability (e.g. you could manually push configuration changes from a console, see all the logs in one place, e.t.c.).

The purpose of this task after discussion with @astoycos and @aryan9600 is that we wanted to check back in and discuss whether we want to go back, or we actually want to keep the gRPC API, as there are pluses and minuses to both.

shaneutt avatar Jan 24 '24 15:01 shaneutt

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-triage-robot avatar Jul 18 '24 16:07 k8s-triage-robot

The Kubernetes project currently lacks enough active 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 rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

k8s-triage-robot avatar Aug 17 '24 16:08 k8s-triage-robot

We need to triage and discuss this again.

/remove-lifecycle rotten /triage needs-information /remove-priority important-longterm

shaneutt avatar Sep 06 '24 19:09 shaneutt