Add a service with local internal traffic policy for traces and dogstatsd. #375
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
L3n41c
force-pushed
the
lenaic/internal-traffic-policy
branch
4 times, most recently
from
9949708 to
aba7f81
Compare
L3n41c
force-pushed
the
lenaic/internal-traffic-policy
branch
from
aba7f81 to
2aebdd0
Compare
L3n41c
force-pushed
the
lenaic/internal-traffic-policy
branch
from
38fefbe to
2c77b21
Compare
Codecov Report
@@ Coverage Diff @@
## main #375 +/- ##
=======================================
Coverage 61.05% 61.05%
=======================================
Files 3 3
Lines 95 95
=======================================
Hits 58 58
Misses 25 25
Partials 12 12
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
|
Also maybe it will require to update the Network policy to allow the traffic on this service? |
for traces and dogstatsd.
L3n41c
force-pushed
the
lenaic/internal-traffic-policy
branch
from
2c77b21 to
67f8570
Compare
I’ve just updated the PR to implement here the equivalent of DataDog/helm-charts#434 which includes a way to force the service creation.
I don’t think so because Network Policies apply to pods. Reaching a pod directly or through a Service doesn’t make any difference for the Network policy. |
What does this PR do?
Add a service which leverages internal traffic policy for traces and dogstatsd.
Motivation
Ease the use of dogstatsd and APM as an application could use a kubernetes service instead of having to rely on the downward API to target the local node agent.
Additional Notes
Anything else we should know when reviewing?
Describe your test plan
Deploy the agent with the operator on kubernetes 1.22+ cluster and check that a new service targeting the nodes agent with local internal traffic policy has been created.