Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Dev environment load balancing and routing issue #715

Closed
6 tasks done
placek opened this issue Apr 15, 2024 · 0 comments · Fixed by #728
Closed
6 tasks done

Dev environment load balancing and routing issue #715

placek opened this issue Apr 15, 2024 · 0 comments · Fixed by #728
Labels
🐛 Bug Something isn't working 🏗 Infrastructure
Milestone
Infrastructure ma...

Comments

@placek
Copy link
Contributor

placek commented Apr 15, 2024 •
edited
Loading

As a developer,

I want the backend service to be reachable in the dev environment through proper load balancing and routing setup

so that I can test and debug the backend functionality effectively.

Summary

The issue in the dev environment is that the backend service is not reachable, although the same configuration is functional in the test environment. The problem seems to stem from the dynamic configuration of the Traefik service, which is not detecting the backend part correctly and is not loading its setup properly, causing all traffic to be resolved to the frontend app.

Acceptance Criteria:

  • Investigate the current configuration of Traefik service in the dev environment.
  • Ensure that the backend service is correctly defined and reachable in the configuration.
  • Test the routing setup to verify that traffic is correctly directed to the backend service.
  • Compare the dev and test environment configurations to identify any discrepancies.
  • Implement necessary changes to the Traefik configuration to properly load balance and route traffic to the backend service.
  • Verify that after the changes, the backend service in the dev environment is reachable and functioning correctly.
@placek placek self-assigned this Apr 15, 2024
@placek placek added 🐛 Bug Something isn't working 🏗 Infrastructure labels Apr 15, 2024
@placek placek moved this to In progress in Govtool all Apr 15, 2024
placek added a commit that referenced this issue Apr 15, 2024
@placek
[#715] rename the routers names to distinguish them from the service …
0f3ca5a 
…names

The commit adjusts the names of the routers in the Traefik configuration
within the docker-compose.yml file. This modification ensures that the
routers are distinctively named and do not share names with the
services, enhancing clarity and manageability of the setup. By renaming
the router identifiers, it becomes easier to differentiate them from the
corresponding services, thus facilitating maintenance and
troubleshooting of the configuration.
placek added a commit that referenced this issue Apr 15, 2024
@placek
[#715] Fix indentation in Traefik configuration in docker-compose file
f7f61c2 
The adjustments in this commit focus on correcting the indentation in
the Traefik configuration section within the docker-compose.yml.tpl
file. The changes entail ensuring consistent and proper alignment of the
services' definitions, specifically the metadata-validation service, to
enhance readability and maintainability. By reformatting the
indentation, the Traefik configuration becomes more organized,
facilitating easier navigation and understanding of the setup.
placek added a commit that referenced this issue Apr 15, 2024
@placek
[#715] Update Traefik image version to v3.0
0856db4 
The commit modifies the Traefik image version specified in the
docker-compose.yml.tpl file from v2.10 to v3.0. By updating the Traefik
image, we ensure compatibility with the necessary features and
improvements introduced in version 3.0. This adjustment aligns with the
user story's goal to enhance load balancing and routing setup in the dev
environment by making sure that the configuration utilizes the latest
Traefik version for more efficient backend service management and
testing capabilities.
placek added a commit that referenced this issue Apr 15, 2024
@placek
[#715] Apply better priorities to the routing
c47e0e9 
The commit enhances the routing setup in the Traefik configuration
within the docker-compose.yml.tpl file by implementing better
priorities. By adjusting the priority of the router for the frontend
service to 1, the routing for this service looses precedence, ensuring
that frontend traffic is correctly directed. This change aims to
optimize the routing logic, ensuring that the frontend service receives
appropriate traffic allocation and improving the overall efficiency of
the load balancing and routing setup in the dev environment.

This is an actual fix of the problem stated in the related issue.
placek added a commit that referenced this issue Apr 15, 2024
@placek
[#715] Add healthchecks to two main backend services from Traefik loa…
6a1968a 
…d balancer

The commit enhances the Traefik configuration within the
docker-compose.yml.tpl file by adding healthcheck configurations to the
two primary backend services, `metadata-validation` and `backend`. These
healthchecks include defining paths, ports, intervals, and timeouts for
monitoring the health and status of the backend services. By
implementing healthchecks, Traefik can periodically verify the
availability and responsiveness of the backend services through
specified endpoints, contributing to improved load balancing and routing
efficiency. This change directly addresses the user story requirement to
ensure the backend service is correctly defined, reachable, and
functioning optimally in the dev environment for effective testing and
debugging purposes.
@placek placek mentioned this issue Apr 15, 2024
Merged
@placek placek linked a pull request Apr 15, 2024 that will close this issue
[#715] Dev environment load balancing and routing issue #728
Merged
placek added a commit that referenced this issue Apr 15, 2024
@placek
[#715] Add additional CORS exception for dev environment
aaecda0 
The changes made in this commit focus on enhancing the CORS
configuration for the dev environment by adding an additional exception
to allow specific origins. The modification includes appending
"http://localhost:5173" to the list of allowed hosts when the
environment is set to "dev." This adjustment aims to address
Cross-Origin Resource Sharing (CORS) issues related to accessing
services from different origins, ensuring that the specified host is
permitted to interact with the backend service seamlessly.
placek added a commit that referenced this issue Apr 16, 2024
@placek
Merge pull request #728 from IntersectMBO/fix/715-dev-environment-loa…
cc64e97 
…d-balancing-and-routing-issue

[#715] Dev environment load balancing and routing issue
@github-project-automation github-project-automation bot moved this from In progress to Done in Govtool all Apr 16, 2024
@placek placek moved this from Done to In QA in Govtool all Apr 16, 2024
@pmbinapps pmbinapps mentioned this issue Apr 19, 2024
Merged
@MSzalowski MSzalowski mentioned this issue Apr 19, 2024
Merged
@pmbinapps pmbinapps moved this from In QA to In staging in Govtool all May 16, 2024
@bosko-m bosko-m moved this from In staging to Done in Govtool all Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🐛 Bug Something isn't working 🏗 Infrastructure
Projects
Govtool all
Status: Done
Milestone
Infrastructure management (DevOps)
Development

Successfully merging a pull request may close this issue.

[#715] Dev environment load balancing and routing issue IntersectMBO/govtool
2 participants
@placek @pmbinapps