allow making bastions highly available #117
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.
Summary:
This PR introduces high availability for bastions across AWS, Azure, and Kubernetes providers by adding a
highAvailability
field to theBastionArgs
struct, updating the auto-scaling and deployment logic, updating theschema.yaml
and SDKs, and updating the Node.js version used in the GitHub workflows.Key points:
HighAvailability
field toBastionArgs
struct inaws
,azure
, andkubernetes
providers.HighAvailability
istrue
.schema.yaml
to includehighAvailability
in the schema of the bastion resources.go
,dotnet
,python
,nodejs
) to includehighAvailability
in the bastion resources.Generated with ❤️ by ellipsis.dev