Erik
Erik
poc in my pants
i suggest looking at analyses of the other rdp vulns
This would be much easier if peers worked with resolvers - as far as I can tell, it only takes IP's Alternatively, if you're using host network and your nodes...
Even if it's a string, you can still use the value unquoted elsewhere
Looks like this has been unanswered for over a year, so I'll add my thoughts... We have 20-30 microservices which are mostly identical, but require slightly different ingress rules, environment...
I'd like to see this merged! I think the only thing missing is adding those new options to the README as well.
With kubectl dry-run, it only works with --dry-run=server, not client, for some reason. So this might unfortunately be outside of kubeval's scope. Not sure why, though.
I tried different configs till it stopped erroring - this seems to be what did it - ```[publish] publish-addresses=yes publish-hinfo=no publish-workstation=no publish-domain=no publish-resolv-conf-dns-servers=no publish-aaaa-on-ipv4=no publish-a-on-ipv6=no ```
Could possibly define it as a plugin that pipes the logs to jq?