Post

We helped empower CloudBank to provision and manage their own infrastructure on our shared platform. Instead of waiting on 2i2c engineers, they can now handle these changes themselves. 2i2c.org/blog/cloudba...

2i2c.org2i2c.org

2i2c

@2i2c.org

22 Jan

The core fix was to move CloudBank’s Terraform state into CloudBank’s own GCP project, so access is scoped to their cluster and can’t spill over to other communities. It allows them make their own changes while still using our multi-community platform.

github.comAllow Sean Morris to allocate new disks for CloudBank · Issue #6795 · 2i2c-org/infrastructurePresently, for new Hubs on CloudBank, Sean has to ping us to allocate raw block storage for the home directory volume. It would be nice to prevent these synchronous requests from blocking him. What...

2i2c

@2i2c.org

This is part of how we think about agency vs safety on a shared open platform, give partners control in a way that's safe for other member organizations. As a result, CloudBank can run routine Terraform changes, and they validated it by deploying a hub without 2i2c in the loop.

22/1/26, 2:02 pm0 reposts0 likes

2i2c

@2i2c.org

22 Jan

This is nuanced and complex, so if you'd like to learn more, see discussion about how to do this here: github.com/2i2c-org/inf...