Hi folks! I can't understand why after deploying kubequery only a limited number of tables are available and nothing about kubernetes? @Seshu perhaps you know and can help with the problem. Best regards!

Maybe best for #uptycs? We can help with getting it connected to Fleet, but I'm not sure about the actual tables.

@zwass "help with getting it connected to Fleet" - it's very actual for me ) I have a problem with only seeing the kubequery version in Fleet How to fix it? Maybe there is an instruction for setting up interaction?

Ah, interesting. Kubequery removes all of the tables that are used to populate information about the host, so we'll need to handle that differently.

I thought about it. But while there are difficulties, perhaps you have gone this way and share the solution to the problem?

Last time I tried kubequery it was before they removed all of the tables with that info. I don't think there is a good immediate solution here.

Can you recommend a working alternative?

Maybe modify kubequery so that it returns at least a hostname or something that can identify the host?

I'll try. Thanks.