Dual cluster FRIDGE deployment #137
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e Kubernetes Service (AKS) cluster using Pulumi and Python.
This was referenced Nov 11, 2025
…tor and MinIO config job.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR splits FRIDGE deployment up across two clusters.
The
accesscluster contains an SSH server and the Harbor container registry.The
isolatedcluster contains the rest of the FRIDGE deployment.This complements PR #131, which does the initial deployment of two AKS clusters.
The intended deployment pattern here is for the TRE Operator to first deploy the access cluster components, then set up the SSH proxy to allow them to deploy the isolated cluster components.
That will then be followed by a final infrastructure configuration step to limit network traffic more completely.