Planning Thread: Dev Team Sprints

Development
1

This thread is to be used to keep notes on planning dev team 2-week sprints

2

Dev Team Developing Sprint #3: Scholarx Frontend

  • From: 2021-02-26T18:30:00Z to 2021-03-12T18:30:00Z

Draft Plan:

  • First week:
    • Configuring the webpack production build
    • Dockerizing the frontend
  • Second week:
    • Putting the dockerized frontend into the minikube cluster as a new pod
    • Exposing frontend through ingress via the path /
    • Exposing auth-server through ingress using the path auth/
  • Optional:
    • Catching the 401 errors and redirecting into window.location/auth//oauth2/authorization/linkedin

@YohanAvishke Can you please see to this and finalise the sprint plan properly?
I won’t be available from this week to March 18th because of my exams

3

Setting up the kubernetes cluster

I went through the readme file and build the project just like it says. but this needs a higher processing power and there is a problem with the scholarx-app.

As you can see in the screenshot below it throws an error and keep restarting the MySQL pod. I tried deleting the scholarx-app and tried api/todos/:id APIs which is in the auth-server and it works the way we want. but I tried to access the endpoints via the app it doesn’t work and takes so much processing power even the kubectl get all command times out.

Here’s the log:

timeout

image
image1526×614 80.8 KB

multiple SQL pod restarts

image
image1658×540 83.6 KB

Possible solution:
Creating an one pod which contains the resources and the authentication.

We need to have a call regarding this ASAP.

1 Like
4

@anjisvj thank you soo much for the suggestion. What will be the pros and cons of using a singular pod for auth and resources other than the usage of limited processing power?

1 Like