I'm actually not sure that this is not implemented for TCP, I just copied it from the dynamic metadata documentation.  I can understand why HTTP filter setting metadata would not be implemented for TCP for the dynamic metadata.  For cluster metadata, however, the question is whether the stream info contains any metadata for TCP clusters - @yanavlasov do you know how do that works?