NLB-7285: Add dataplane_api_key as an optional #1012
+474
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
UseCase
We need
dataplane_api_keyin authorization header to make api call toDataplane API. We want to makeapi_endpointvalue as dataplane api which is proxy/copy of nginx plus api that we use as part of NGINXaaS for Azure.So, when the VMSS (azure scaling group) scales out/scales in,
nginx-asg-syncmake api calls to dataplane api which updates the upstream servers.Upstream server update logs
Load balancing incase of 2 instances
Manually scaled to 4 instances
Load balancing after upstream servers updated by nginx-asg-sync
Checklist
Before creating a PR, run through this checklist and mark each as complete.