You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was able to deploy STUNner as a STUN service as described in this article, with the dataplane as DaemonSet (I manually converted the Deployment created by the operator). It would be great if you could support this mode of deployment automatically with some annotation in the Gateway CRD (i.e. stunner.l7mp.io/dataplane-deployment-mode: daemonset). The podAntiAffinity approach is doable but you would still need to manually set the number of replicas equal to the number of nodes so that each node gets a stunnerd Pod, which is not ideal if you provision them dynamically with Cluster Autoscaler or Karpenter.
The text was updated successfully, but these errors were encountered:
Full ack. Unfortunately currently there's no resource to automate this, so you'll have to do the manual Deployment-DaemonSet swap. On the long run, we should definitely support this.
I'll leave this one open, maybe someone will jump in and catch it up.
I was able to deploy STUNner as a STUN service as described in this article, with the dataplane as DaemonSet (I manually converted the Deployment created by the operator). It would be great if you could support this mode of deployment automatically with some annotation in the Gateway CRD (i.e.
stunner.l7mp.io/dataplane-deployment-mode: daemonset
). The podAntiAffinity approach is doable but you would still need to manually set the number of replicas equal to the number of nodes so that each node gets astunnerd
Pod, which is not ideal if you provision them dynamically with Cluster Autoscaler or Karpenter.The text was updated successfully, but these errors were encountered: