12,257 karma · joined December 15, 2009
The problem is that we need a ton of logic in the coordinator. For example on how to do matrix builds. For local builds to be perfectly similar we would have to recreate that logic inside the runner. This is hard, not in the least because it are different programming languages.
Logging in via SSH seems useful although that would mean keeping the machine running after a failed build.
Microkernels were presented as the future in which fewer things would run in the kernel. Instead we've gone in the other direction in which more is running inside the kernel.
Monolithic kernel: the Network Device runs inside the kernel and the Packet Filter outside.
Microkernel: both the Network Device and Packet Filter run outside the kernel.
eBPF: both the Network Device and the Packet Filter run inside the kernel.
So far that functionality has lived in separate repositories from the core codebase since few people needed it, the cycle time was quicker, and it is an advantage to not have the spammers see the code.
If there is strong interest in collaborating on this I'm sure they will be happy to engage. I'll ask them how best to structure this.
Yesterday someone showed us the new tech stack page in a meeting. We're all proud because it replaces a bunch of spreadsheets where each department (finance, security, people) tried to maintain the same list of apps with a single yml file. I ask if anyone has a concern if I tweet it, everyone is OK with it since it is already public anyway.
That takes a value of transparency https://about.gitlab.com/handbook/values/#transparency which has us be public by default https://about.gitlab.com/handbook/values/#public-by-default even when it is hard https://about.gitlab.com/handbook/values/#transparency-is-on...
And it takes us reinforcing these values now in 17 different ways https://about.gitlab.com/handbook/values/#how-do-we-reinforc...
For CDNs we switched from Fastly to Cloudflare because we needed support for SSH (port 22)
And for email sending I think you want multiple providers so you have a hot one (already know on the internet to send a large volume of mail in your name) in cause a provider has problems with delivery.
This was probably submitted to Hacker News after someone saw my tweet https://mobile.twitter.com/sytses/status/1319325053217992704 which has some questions and answers in the replies.
John already linked to the architecture of GitLab the application in https://news.ycombinator.com/item?id=24869339 in case you are interested in that.
Happy to answer any questions about either.
Zero Trust means authenticating per application instead of per network. For more context see https://about.gitlab.com/blog/2019/04/01/evolution-of-zero-t...
Proxying connections as Boundary does seems like the most elegant solution to achieve this in a way that doesn't require modifying the application.
2. GitLab contacted Matrix.
I think 3. and 4. have answers in https://matrix.org/blog/2020/09/30/welcoming-gitter-to-matri...