Filip Pytloun

> @fpytloun What is your cluster - in K8s? If yes, then you could just define a ingress and point to respective service names My setup are two regions running...

@allanrogerr Thank you for testing option with `/etc/hosts`. I don't have environment to test this workaround but I think it might work as problem seemed to be that minio node...

Forward plugin has these parameters: ``` source_address_key forward_source_address source_hostname_key forward_source_hostname ``` so it's possible to use `record_transformer` like this: ``` @type record_transformer enable_ruby true auto_typecast true input ${record['sqs_source_url'] != nil...

Also certificate issuer does not set namespace so it is created in default namespace so certificate never gets issued due to issuer not found error.

I just hit this error on multiple of my vector instances after restart which then fails to start: ``` 2024-05-24T09:09:52.916943Z ERROR vector::topology::builder: Configuration error. error=Sink "out_vector_high": error occurred when building...

Another workaround is to add this into entrypoint before starting vector process: ```sh now=$(date +%s) last_startup=$(cat /var/lib/vector/startup || echo 0) last_startup_age=$[ ($now - $last_startup) / 60 ] if find /var/lib/vector/buffer...

I am digging a bit deeper and I think this is related to consumer group rebalances and partition re-assignments. It seems that if rebalance occurs, original vector instance that was...

v0.44.0 ships newer rdkafka, we should test if this issue is still present.

> Scheduler checks if an entity is unavailable, if this is the case the action is postponed until the entity becomes available, otherwise the action is executed directly. So this...

Bump