Matti Paksula
Matti Paksula
I'm not sure if changing the delay from 100 to 500 is a good change. Can't the server see otherwise that the connection is websockets, like read headers or something?...
But can't we "pre-read" the connection and see if there is websocket stuff coming or if it's silent as an additional hint?
added my comments in the issue https://github.com/LibVNC/libvncserver/issues/438
increasing handshake wont fix this for slow networks, it just increases propability to succeed and makes ws connections to start slower this dual mode operation should just be change to...
same here with: ``` apiVersion: eksctl.io/v1alpha5 kind: ClusterConfig metadata: name: 'test-1' region: 'eu-north-1' managedNodeGroups: - name: 'test-16-32-6-2022-06-16-14-12-45' labels: test: 'yes' volumeType: 'gp3' volumeSize: 6 volumeIOPS: 3000 volumeThroughput: 125 minSize: 0...
so workaround like this: ``` nodegroup=$1 # fetch nodegroups asg asg=$( aws eks describe-nodegroup --region $REGION --cluster-name $CLUSTER_NAME \ --nodegroup-name $nodegroup \ --query "nodegroup.resources.autoScalingGroups[0].name" \ --output text ) # fetch...
the problem is that it doesn't propagate these tags to the underlying auto scaling group - they only get correctly added to the eks tags listing what is shown in...
okay, I'll try to make my own screenshots soon
@youwalther65 you have the yaml wrong ``` auto-delete: no ``` ^-- yaml turns `no` and `yes` to booleans unless they are inside of " so ``` auto-delete: "no" ```