Skip to content

Add dev-proxmox to UA Apps cluster list#356

Merged
Ziggiyzoo merged 4 commits into
mainfrom
AddDevProxmoxClusterToUAApps
Jun 29, 2026
Merged

Add dev-proxmox to UA Apps cluster list#356
Ziggiyzoo merged 4 commits into
mainfrom
AddDevProxmoxClusterToUAApps

Conversation

@Ziggiyzoo

Copy link
Copy Markdown
Contributor

Closes: #355

@Ziggiyzoo Ziggiyzoo self-assigned this Jun 26, 2026
@Ziggiyzoo Ziggiyzoo requested a review from a team as a code owner June 26, 2026 10:35
Comment thread argocd/dev/ua/vault-operator-configs/app.yaml Outdated
Comment thread argocd/dev/ua/vault-operator/app.yaml Outdated

@ffionalys ffionalys left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@KashDev00 @Ziggiyzoo We had problems with deploying to multiple clusters when the fallback cluster was introduced. e.g. traffic was still delivered to both even when one of them was down, observability was difficult as logs were split across multiple clusters.

Are we going to see similar problems with deploying dev to 2 different clusters?

@KashDev00

Copy link
Copy Markdown
Collaborator

@KashDev00 @Ziggiyzoo We had problems with deploying to multiple clusters when the fallback cluster was introduced. e.g. traffic was still delivered to both even when one of them was down, observability was difficult as logs were split across multiple clusters.

Are we going to see similar problems with deploying dev to 2 different clusters?

The traffic redirection is done at the reverse proxy level.

Ideally, we should make changes to the reverse proxy so it doesn't direct traffic to the cluster that is down. For observability, we can add fields to OpenTelemetry data, such as the cluster name from which the data is emitted. These are separate issues.

This PR just deploys the apps to the new cluster. There are no changes to the reverse proxy, so no traffic is directed to the new cluster. We are just going to deploy apps to the new cluster.

@ffionalys

ffionalys commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

@KashDev00 @Ziggiyzoo We had problems with deploying to multiple clusters when the fallback cluster was introduced. e.g. traffic was still delivered to both even when one of them was down, observability was difficult as logs were split across multiple clusters.
Are we going to see similar problems with deploying dev to 2 different clusters?

The traffic redirection is done at the reverse proxy level.

Ideally, we should make changes to the reverse proxy so it doesn't direct traffic to the cluster that is down. For observability, we can add fields to OpenTelemetry data, such as the cluster name from which the data is emitted. These are separate issues.

This PR just deploys the apps to the new cluster. There are no changes to the reverse proxy, so no traffic is directed to the new cluster. We are just going to deploy apps to the new cluster.

Ok that's fine with me, if we are going to have prod deploy to both then I think we need to make the changes to the reverse proxy first, so that traffic doesn't get directed to a cluster that's down.

@ffionalys ffionalys closed this Jun 29, 2026
@ffionalys ffionalys reopened this Jun 29, 2026
@Ziggiyzoo Ziggiyzoo merged commit 842d5b5 into main Jun 29, 2026
@Ziggiyzoo Ziggiyzoo deleted the AddDevProxmoxClusterToUAApps branch June 29, 2026 11:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add dev-proxmox cluster to UA Apps

3 participants