Kubernetes/Openshift Deployment of synthetics-job-manager Without Docker/Bridge Network Dependency

[ppp0]

Description

Currently, synthetics-job-manager wants to connect to a Docker daemon and to create a bridge network upon starting up. In our Openshift environment this is not allowed due to security policies. The worker images (ping, browser, node) are set up according to the Helm charts, they share an own namespace and could also be scalable via deployment/cronJob specs. May be I missed something in the configuration, but having Docker pull, scale up and down and entertain a network is likely redundant on container orchestration platforms. Preferably, the Job manager would make use of the Kubernetes API to control the workers. If this already is a feature, this ticket can be closed

Acceptance Criteria

• New Relic Synthetics private locations can be installed and run on k8s/Openshift without dependency on root user privileges (Depends on https://github.com/newrelic/helm-charts/issues/1347)
• New Relic Synthetics private locations have no further dependency (ie on Docker)
• New Relic Synthetics private locations make use of container orchestration methods to scale up and down workers and to ensure communication between them

Describe Alternatives

n/a

Dependencies

Synthetic tests from private locations would be part of a currently operational comprehensive platform observation. Lack thereof forces us to put other 3rd party products into the mix

Additional context

n/a

Estimates

Difficult to establish without having access to sources, though likely a L-size effort for an experienced engineer

For Maintainers Only or Hero Triaging this bug

Suggested Priority (P1,P2,P3,P4,P5): Suggested T-Shirt size (S, M, L, XL, Unknown):

[workato-integration[bot]]

https://new-relic.atlassian.net/browse/NR-370801

[ppp0]

Newest installation attempt did not show this behaviour. Closing thus