Remote dev solution for elastic integrations

[matschaffer]

At least for my home internet, operations involving elastic-package stack take at least 30 minutes. Sometimes more than an hour to complete.

Eventually they also fill up my docker-for-mac disk and fail out in non-obvious ways when ES hits the high disk watermark.

I'm going to see if I can use kibana-remote-dev (internal), maybe plus off-repo vscode containers to get a decent package/integration workflow going that doesn't take too long to test out.

[matschaffer]

I did some timing with @klacabane last night and it might be better now, but unclear why. Could be there are situations where I end up warming the NRT docker cache, or maybe I wasn't hitting it in my previous runs for some reason.

I guess I'll put this down while I try to work on the packages themselves and keep time information handy for now.

[matschaffer]

Ah, I might have found the problem. Looks like in some cases (cold cache? bad routing?) I'm also grabbing images from LAX

cc @Crazybus who was able to tell me about the presence of cloudfront for docker layers. He may have some ideas on why end up grabbing from LAX.

[matschaffer]

I noticed that during the phase where elastic-package was pulling docker.elastic.co/elastic-agent/elastic-agent-complete:8.3.2

[matschaffer]

I guess I'll close this for now. Either my internet is doing better since yesterday or the CDN is working better. I'll keep timing as I work on other things and maybe re-open this or other issues as I go.