Skip to content
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

evaluate ansible and choice of dns #104

Closed
rtang03 opened this issue Aug 13, 2020 · 1 comment
Closed

evaluate ansible and choice of dns #104

rtang03 opened this issue Aug 13, 2020 · 1 comment
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@rtang03
Copy link
Owner

rtang03 commented Aug 13, 2020

After watching the introduction of Blockchain Automation Framework, it leverages ansible to do orchestration over helm. That sounds good approach. Should further evaluate it.

Also, need to figure how to implement dns properly

@rtang03 rtang03 added the enhancement New feature or request label Aug 13, 2020
@rtang03 rtang03 added this to the sprint-7 milestone Aug 13, 2020
@rtang03 rtang03 self-assigned this Aug 13, 2020
@rtang03 rtang03 added this to To do in library packages via automation Aug 13, 2020
@rtang03
Copy link
Owner Author

rtang03 commented Aug 29, 2020

Ansible is not required. Instead, will use FluxCD

Currently, there is no need for external DNS. However, use use GCP private zone DNS, if later found necessary.

The GCP L7 LB can do routing, based on requesting URL, and its tlsca cert. This is a pretty nice and simple solution.

@rtang03 rtang03 closed this as completed Aug 29, 2020
library packages automation moved this from To do to Done Aug 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

1 participant