Edit: ah, I see you are referring to the setup-trivy action rather than the trivy-action. Yeah, that looks like a bad default, although to be fair it is a setting that they document quite prominently, and direct usage of the setup-trivy action is a bit atypical as-is.
It's pretty single-server focused... but there is a 'Multi Host' mode. One instance can use SSH to look at N systems [independently]. This consolidates the Cockpit endpoints you might need to use/ports to open... but doesn't give much in the way of orchestration.
I believe when 'roscas' says this feature was dropped, they're talking about the requirement to enable 'AllowMultiHost'. As far as I know, this is still supported with some risk (according to the latest docs): https://cockpit-project.org/guide/latest/#secondary-auth
I think they dropped multi server managment because it was possible to add a few servers but I guess they drop that one out. You do can logon into a server right on the logon page. That is nice.
It means that when AngryData "skips every step past the field" they didn't save any notable money by doing so. Their beef costs more than unsubsidized industrial beef would cost, so when they call BS on $30-40 that is a valid call.
I remember seeing a lot of social media posts during the Biden admin about grocery prices... Turns out a lot of folks were just comparing the same cart, not taking into account discontinued items that were being auto-replaced with more expensive goods, or things like that. It wasn't always an accurate representation.
Look up what their production targets were and compare that to their sales. A small temporary demand surge isn't going to be enough to chew through their current inventory, let alone keep the production lines busy.
reply