Is it possible to pass a Service's external IP (NodePort or LoadBalancer) as an environment variable to a container in a different service's Deployment?

For a concrete example, consider a Kubernetes cluster with namespaces for multiple teammates so they each have their own environment for testing. In a single environment, there are at least two services:

1. An API Gateway service, for routing traffic to other services
2. A service that can register DNS entries to the environment

For Service #2, it needs to know the external IP address of service #1. So far I've only been able to find examples that make use of kubectl to describe service #1 to find this information. I was hoping it would be possible to do something like this:

apiVersion: v1
kind: Service
metadata:
  name: gateway
  namespace: "${ env }"
  labels:
    app: gateway
spec:
  type: LoadBalancer
  ports:
     - port: 8080
  selector:
    app: gateway

and

apiVersion: extensions/v1
kind: Deployment
metadata:
  name: svc2-deployment
  namespace: "${ env }"
  labels:
    app: svc2
spec:
  template:
    metadata:
      labels:
        app: svc2
    spec:
      containers:
        - name: app
          env:
            - name: GATEWAY_IP
              valueFrom:
                fieldRef:
                  fieldPath: service.gateway.----.ingressIp

instead of using say an initContainers with a script that does kubectl things. Especially since I'm very new to Kubernetes :)