chore(nri-metadata): remove limitation (#1485)

Author: paologallinaharbur

test/k8s-canaries/helm/agent-control.yml

@@ -16,11 +16,6 @@ agent-control-deployment:
         type: newrelic/com.newrelic.infrastructure:0.1.0
         content:
           chart_version: "*" # Use latest
-          chart_values:
-            nri-metadata-injection:
-              # TODO we are currently disabling the metadata injection since if enabled it breaks when installed
-              # together with the gatewayRESE
-              enabled: false
       prometheus:
         type: newrelic/com.newrelic.prometheus:0.1.0
         content:

test/k8s-e2e/fleet-control/e2e-fleet-control.yml

@@ -29,7 +29,3 @@ scenarios:
         #     customAttributes:
         #       cluster_name: ${nr-env:NR_CLUSTER_NAME}
         #       config_origin: remote
-        #   nri-metadata-injection:
-        #     # TODO we are currently disabling the metadata injection since if enabled it breaks when installed
-        #     # together with the gateway
-        #     enabled: false

test/k8s-e2e/infra/ac-values-infra.yml

@@ -20,10 +20,6 @@ agent-control-deployment:
             global: # add 'cluster_name' (nri-kubernetes events have 'clusterName' attribute)
               customAttributes:
                 cluster_name: ${nr-env:NR_CLUSTER_NAME}
-            nri-metadata-injection:
-              # TODO we are currently disabling the metadata injection since if enabled it breaks when installed
-              # together with the gateway
-              enabled: false
       prometheus:
         type: newrelic/com.newrelic.prometheus:0.1.0
         content: