-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Devise engineering operation DNS specification #50
Comments
An organization has many operations. The effective definition of an "organization" in this design is simply some DNS zone under our control. Typically that will be a root domain, but it can also be subdomains. Separate private repositories have been produced as a result of research and work into this issue:
|
Might consider just upgrading this to an IPv6 scheme. |
The infrastructure scheme underlying this structure has been deployed; helm has been added to this project. |
Added a bonus organizations infrastructure module. Under the current paradigm, a domain is associated with an organization. That does not preclude configurations where multiple domains belong to a single organization, or a configuration where this domain can be modified to a subdomain. There should be no loss in the extensibility of this structure. |
- Remove unnecessary EC2 Terraform; application now uses Kubernetes - Add basic helm/k8s configuration - Remove Terraform from Drone while application has no specific infra
The latest build of
develop
has broken due to hosted-zone DNS incompatibilities between this application repository and other, private repositories.Personal infrastructure has grown beyond the scope of this application and now needs its own repository and accompanying Terraform configuration.
The text was updated successfully, but these errors were encountered: