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.

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

ingress: add spec for ingress tests #7

Closed
2 of 6 tasks
mayankshah1607 opened this issue Jun 26, 2020 · 1 comment
Closed
2 of 6 tasks

ingress: add spec for ingress tests #7

mayankshah1607 opened this issue Jun 26, 2020 · 1 comment

Comments

@mayankshah1607
Copy link
Contributor

mayankshah1607 commented Jun 26, 2020

This test would be responsible for testing if ingress controller pods injected with Linkerd are are able to correctly rewrite incoming headers to ensure that traffic is proxied correctly. The sample app to be used for this is emojivoto.
Based on the Linkerd docs, the following ingress controllers will be tested:

  • Nginx
  • Traefik
  • GCE
  • Ambassador
  • Gloo
  • Contour

All the required YAML files shall be provided along with the tests. The testing process can be broken down into the following assertions:

  • Checking if the sample app is in a Running state
  • Deploying each of the Ingress controllers and make sure they're in a Running state
  • Ensure the services are reachable via Ingress
  • Inject the Ingress controller's pods and wait for it to come to a Running state. Verify if the proxy container has been injected.
  • Deploy the Ingress resource with the correct rules to rewrite headers to ensure Linkerd's service discovery is working
  • Check if the services are reachable via the Ingress
@mayankshah1607
Copy link
Contributor Author

Closed via #19

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 a pull request may close this issue.

1 participant