doks | Build a custom , production-ready documentation website | Theme library

I need to implement a Job Application Platform for a fictive company in a University Project.

The Website is for a single company, not multiple companies like indeed.

Every potential applicant has to make an account and then he is able to apply for the jobs he wants to.

I came up with a model for the database and wanted to ask for feedback and potential improvement since I am very uncertain if it is good enough.

https://i.stack.imgur.com/5DVWB.png

The tables are in German so here is a translation:

Job advertisements (upper left)

1. ID (PK)
2. Department
3. title
4. Startdate of application time (if this date is reached the advertisement is visible on the website)
5. Enddate (if this date is reached it automatically gets hidden)
6. Description
7. Type of job (internship, full-time etc)
8. isActive (boolean if the adv. is visible)
9. Location
10. contact
11. CV
12. Anschreiben, Zeugnisse & weitere Doks is a boolean
    -> when it is true those documents are required
    -> release (HR has to check every advertisement and has to release them)

• Employees (upper middle)

1. ID
2. Firstname
3. Lastname
4. Email
5. role

• External registrations (upper left - all accounts who register for the job portal)

1. ID
2. Firstname
3. Lastname
4. email
5. phonenumber

• Applications (lower middle table)

1. ID (PK)
2. Job advertisement ID (FK)
3. Applicant ID (FK - ID from external registrations)
4. Firstname
5. Lastname
6. email
7. phonenumber
8. status (shows if applications is being looked at and stuff)
9. Files (boolean to check if a zip file was uploaded with the application)

So my thought behind this model were that if some applies for a job & fills out the application form the userID of this account & the advertisement ID of the particular job get saved into the database "applications". This way it is always identifiable who applied to which job.

I have set up a k8s cluster (1 node cluster) using DOKS. The service is running fine with nodeport config. However, I am unable to access it using http://${NodeIP}:${NodePort} from browsers. I have even tried to add the firewall rule, but i am getting error response from backend while trying to add a new inbound TCP rule. Not a useful error message!

Curl and Telnet are failing as well.

Please find below my dockerfile, deployment and service yaml files.

Dockerfile

I'm running Jenkins on Kubernetes with a dynamic slave pod provisioning setup.

It used to work well for a long time but somehow started to giving this issue from yesterday.

This is the log that I'm getting from the slave pods

I'm trying to deploy an UDP-based application on kubernetes, but I'm having troubles finding a suitable cloud provider that has an UDP loadbalancer with IP-based sticky sessions.

I have tried using DigitalOcean Kubernetes Service (DOKS) but they don't support UDP loadbalancers.

EKS (AWS' kubernetes service) provides UDP support with NLB for example, but they don't seem to have sticky sessions on that type of loadbalancer, only on the classic LB.

Is there another cloud provider (I'm thinking of GCE or Azure) that provides my required functionalities out of the box?

I'm asking this here to know if anyone else has had the same problem and maybe has already tried various solutions, and has already found the perfect fit.

I am having a problem where I am trying to restrict a deployment to work on avoid a specific node pool and nodeAffinity and nodeAntiAffinity don't seem to be working.

• We are running DOKS (Digital Ocean Managed Kubernetes) v1.19.3
• We have two node pools: infra and clients, with nodes on both labelled as such
• In this case, we would like to avoid deploying to the nodes labelled "infra"

For whatever reason, it seems like no matter what configuration I use, Kubernetes seems to schedule randomly across both node pools.

See configuration below, and the results of scheduling

deployment.yaml snippet