loom
loom copied to clipboard
Loom enables operations engineers to provide a self-serve Kubernetes provisioning experience for developers
Seems to be an intermittent issue where a fabric VPC will fail to delete when a user deletes and then recreates a fabric. Usually the issue is the Internet Gateway...
Loom is too much of a black box with regards to its networking setup. Based on user feedback it's become clear we need to open up the networking components laid...
Asked for by @kflynn in conversation. It can be confusing for developers to remember which Fabric Model they should use. This API allows an operations user to configure a "default"...
fabrics/name/cluster returns application/json fabrics/name return text/html fabrics returns text/html
The IAM GetUser call requires additional IAM permissions for users that the STS call does not require therefore the less friction-y approach for getting this information is to rely on...
Developers would like to be able to spin up cloud resources, for example, a PostgreSQL database that runs on AWS RDS. From Bob the Ops Engineers perspective he wants to...
http://loom.run/about/why-loom.html talks about databases, but the quickstart talks about Kubernetes clusters. I suggest redoing why-loom so it talks about spinning up k8s clusters on AWS easily, and a section about...
Loom should provide a clearer error message to the end user when AWS credentials are not found.