There's a request in place to give you AWS creds, @seph what's the status ?

Ping again here, were we able to get credits? I know you have a lot going on @seph so no worries if this needed to be picked up again next year.

We have credits, which we are rapidly consuming with the CDN usage. (Though at an absolute scale, we can float these costs)

I read through the EnvoyProxy quickly and I feel comfortable with how that orchestration works. What I do not yet understand is how we would maintain that setup as code (tf) but @CptOfEvilMinions was helping us along a bit. Maybe we can delegate this setup to Ben?

I can assist with TF

@CptOfEvilMinions do you more or less grok the explanation from https://github.com/envoyproxy/ci-infra? I think we'll want to tee up this work in Jan or Feb.

My other pretty vague concern, is that I kinda want to take that work and shift it to github actions. But mostly, azure makes me cry

I am optimistic that GitHub actions will improve the rough edges and I also think it's the best solution long term. If we do want to make the commitment to migrate we should do that before any ARM64 work

@theopolis just to ensure I understand the request. The request is about setting up Envoy’s publicly released CI pipeline and not setting up Envoy?

well if we switch to GH actions then the request would be something like: can we mimic what Envoy does only using GH actions agents. The appealing thing in that linked repo is the ephemeral VMs.

@theopolis and @seph I have some questions about the current state of the CI pipeline and deliverables. Can we set up a Zoom call sometime this week or in the new year to discuss these?

I'm happy to chat! Not sure who else we might need. I'm generally available 1pm-5pm eastern time. (With a couple of meeting carveouts)

Hi Folks ! Happy new year ...