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

Added support to set retry-policy on App Mesh routes #65

Closed
wants to merge 3 commits into from

Conversation

kiranmeduri
Copy link
Collaborator

Issue #, if available:

Description of changes:
A retry policy enables clients to protect themselves from intermittent network failures or server-side failures. With retry policy definition user can control the retry logic used by Envoy proxies.

App Mesh CRD update checklist

  • Update aws-go-sdk in go.mod
  • Update CRD schema in deploy/all.yaml
  • Update CRD structs in pkg/apis/appmesh/v1beta1/types.go
  • Update deepcopy functions using make code-gen
  • Update App Mesh client wrapper pkg/aws/appmesh.go
  • Update controller(s) under pkg/controller/

Testing

  • Add e2e example to aws-app-mesh-examples and attach DRAFT PR

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

aws-sdk-go@v1.23.2

1. Added health-check for VirtualNode.Listener
2. Add http-headers and priority support to Route.HttpRoute
A retry policy enables clients to protect themselves from intermittent
network failures or server-side failures. With retry policy definition
user can control the retry logic used by Envoy proxies.

This change includes

1. Update aws-go-sdk v1.23.18
2. Update VirtualService CRD definition to capture retry-policy via
3. Update controller to reconcile retry-policy with App Mesh resource
@kiranmeduri kiranmeduri deleted the retry-policy branch September 10, 2019 15:34
@kiranmeduri kiranmeduri restored the retry-policy branch September 10, 2019 15:35
@kiranmeduri kiranmeduri deleted the retry-policy branch September 10, 2019 15:36
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 this pull request may close these issues.

1 participant