fog-view - blue/green and zone based deployments. #4009
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Set up deployments to allow us to specify blue/green and specific availability zones.
Instead of a monolithic install for fog-view components we break the install out into shared network components and the "stacks" that container the shard sets.
fog-view-services
- which contains theingress
and supporting routing objects. The ingress routing can be updated by modifying thecolor:
selector label on thefog-view-service-router
service object.fog-view-fsg
- the fogShardGenerator object. This object will now be deployed as a blue/green set and statically tied to an Availability Zone so we can ensure balancing.A common deployment will use these helm deployments.
On an upgrade we will add a green set. Once the green set is loaded we can switch the selector labels on the fog-view-service-router service to start routing traffic.
Future Work