Tim Jacomb

I think it was just low effort implementation, should be fine to implement.

I've done some scaffolding here: https://github.com/jenkinsci/azure-vm-agents-plugin/compare/master...timja:azure-vm-agents-plugin:vmss-uniform?expand=1 Will see if I have time to get back to it. Its quite a lot of work as all of the deployment / scaling...

not that I know of

TLS would be done under ingress, loadbalancer should just be for the inbound agent port if you're using that and exposing it outside the cluster.

I don't know anything about this area so am uncomfortable reviewing this right now. Thanks for the pull request though.

> Please kindly adhere to the temporary guidance provided by Gowri in the reference link below: [actions/setup-java#685](https://github.com/actions/setup-java/issues/685) The workaround is unreliable, we're having a number of "the network is unreachable"...

Try change the Log Recorder to `FINE` for the `Azure VM Agent (Auto)` logger in the Jenkins system configuration. It should log the ARM template which may help in seeing...

Have you selected gallery image or image reference in the configuration? If that doesn't sort can you provide a screenshot of your config (redacted if necessary)

Is it possible you previously had an image reference and the fields haven't been cleared out? i.e. switch to image reference and clear any fields with data in them.

Something is wrong with your configuration as your ARM template includes imageReference.publisher,offer,sku,version Whereas it should (I just verified on my gallery setup) look like this: ```json "storageProfile": { "imageReference": {...