Skip to content

Fix issues with new AWS deployment#519

Merged
BernhardFuchs merged 7 commits into
mainfrom
fix-add-ingress-creation
Oct 15, 2025
Merged

Fix issues with new AWS deployment#519
BernhardFuchs merged 7 commits into
mainfrom
fix-add-ingress-creation

Conversation

@BernhardFuchs

Copy link
Copy Markdown
Member
  • Check if Ingress exists and create if not
  • Deploy uni-resolver-frontend and exclude it from cleanup as it is not part of the docker-compose.yml file
  • Don't apply uni-resolver-web environment variables as they mess up connection to the drivers
  • Keep Services in sync with docker-compose.yml

@BernhardFuchs
BernhardFuchs merged commit 3386e59 into main Oct 15, 2025
1 check passed
@BernhardFuchs
BernhardFuchs deleted the fix-add-ingress-creation branch October 26, 2025 15:02
mingneedbeer pushed a commit to mingneedbeer/universal-resolver that referenced this pull request Jul 19, 2026
* fix: check for Ingress and create it if not present

* fix: use NodePort for uni-resolver-web and uni-resolver-frontend

* fix: deploy frontend too

* fix: don't cleanup uni-resolver-frontend as orphaned deployment

* fix: skip environment variables for uni-resolver-web to fix host not found exception

* fix: use container port instead of host port for K8s service

* feat: align Services with docker-compose.yml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant