Experience AWS Devops Engineer needed to setup a network policy on kubernetes
Budget: $30 – $250 USD
Statement of problem
We run EKS clusters, and we have a microservice (in multiple pods) that communicates with an external service provider, the service provider has an IP access restriction, in other words, the service provider authorizes requests from some defined IP address. But our microservice IP address used in sending HTTP requests (Outgoing IP) changes when a node is terminated and all pods die.
Expectations
1. We want our microservice in EKS to run on multiple pods to communicate to external services using some static IP address.
2. Even if the Node is terminated and a new one is started automatically, a similar IP address will be used.
Tasks
Milestone 1
- Review the requirements and ask me any relevant questions to understand the requirements
- Setup an EKS cluster on your environment or our environment and implement the requirements
- Deploy an application that communicates to an external service, eg https://requestcatcher.com/, we can give you the application to deploy
- Run a tests
- trigger some calls to https://requestcatcher.com/ to see the IP address received
- Delete the pods so a new one can be started automatically, and trigger another request to https://requestcatcher.com/ to see if the IP address is the same as before
- Finally Terminate the Node so a new one can be started, and new pods are running,
- Then trigger another request to https://requestcatcher.com/ to see if the IP address is the same as before
If the requested IP address is the same or is in a list of the expected IP addresses as predicated,
that means the outgoing IP address is static, and the problem is solved.
- Demo your work
Milestone 2
- Document your work
- Explain your process to the team
We run EKS clusters, and we have a microservice (in multiple pods) that communicates with an external service provider, the service provider has an IP access restriction, in other words, the service provider authorizes requests from some defined IP address. But our microservice IP address used in sending HTTP requests (Outgoing IP) changes when a node is terminated and all pods die.
Expectations
1. We want our microservice in EKS to run on multiple pods to communicate to external services using some static IP address.
2. Even if the Node is terminated and a new one is started automatically, a similar IP address will be used.
Tasks
Milestone 1
- Review the requirements and ask me any relevant questions to understand the requirements
- Setup an EKS cluster on your environment or our environment and implement the requirements
- Deploy an application that communicates to an external service, eg https://requestcatcher.com/, we can give you the application to deploy
- Run a tests
- trigger some calls to https://requestcatcher.com/ to see the IP address received
- Delete the pods so a new one can be started automatically, and trigger another request to https://requestcatcher.com/ to see if the IP address is the same as before
- Finally Terminate the Node so a new one can be started, and new pods are running,
- Then trigger another request to https://requestcatcher.com/ to see if the IP address is the same as before
If the requested IP address is the same or is in a list of the expected IP addresses as predicated,
that means the outgoing IP address is static, and the problem is solved.
- Demo your work
Milestone 2
- Document your work
- Explain your process to the team