apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T10:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-82-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-82.ec2.internal
      uid: 1b203a1c-3ed5-4a3d-81f4-450be5729ea5
    resourceVersion: "54814"
    uid: d1cd80cf-0be8-4506-a861-558d27a997e7
  spec:
    sourcePod: network-check-source-869dcfcdcd-w59l6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T10:11:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.097409ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:39:33Z"
    - latency: 1.208382ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:38:33Z"
    - latency: 965.808µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:37:33Z"
    - latency: 1.812577ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:36:33Z"
    - latency: 968.339µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:35:33Z"
    - latency: 1.505291ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:34:33Z"
    - latency: 1.19853ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:33:33Z"
    - latency: 1.275985ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:32:33Z"
    - latency: 1.108225ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:31:33Z"
    - latency: 1.123545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:30:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T10:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-82-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-82.ec2.internal
      uid: 1b203a1c-3ed5-4a3d-81f4-450be5729ea5
    resourceVersion: "55769"
    uid: 0abb1bba-720f-4a67-9e73-5c0f2959547c
  spec:
    sourcePod: network-check-source-869dcfcdcd-w59l6
    targetEndpoint: a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T10:10:33Z"
      message: 'load-balancer-api-external: tcp connection to a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.420879ms
      message: 'load-balancer-api-external: tcp connection to a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:40:33Z"
    - latency: 8.766163ms
      message: 'load-balancer-api-external: resolved host name a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:40:33Z"
    - latency: 4.793589ms
      message: 'load-balancer-api-external: tcp connection to a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:39:33Z"
    - latency: 10.63757ms
      message: 'load-balancer-api-external: resolved host name a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:39:33Z"
    - latency: 4.999643ms
      message: 'load-balancer-api-external: tcp connection to a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:38:33Z"
    - latency: 13.18313ms
      message: 'load-balancer-api-external: resolved host name a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:38:33Z"
    - latency: 5.189165ms
      message: 'load-balancer-api-external: tcp connection to a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:37:33Z"
    - latency: 8.330191ms
      message: 'load-balancer-api-external: resolved host name a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:37:33Z"
    - latency: 5.144928ms
      message: 'load-balancer-api-external: tcp connection to a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:36:33Z"
    - latency: 10.902186ms
      message: 'load-balancer-api-external: resolved host name a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:36:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T10:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-82-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-82.ec2.internal
      uid: 1b203a1c-3ed5-4a3d-81f4-450be5729ea5
    resourceVersion: "55768"
    uid: d4f60797-0bb9-4448-9e6c-86d4e9788c2b
  spec:
    sourcePod: network-check-source-869dcfcdcd-w59l6
    targetEndpoint: a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T10:10:33Z"
      message: 'load-balancer-api-internal: tcp connection to a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.41185ms
      message: 'load-balancer-api-internal: tcp connection to a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:40:33Z"
    - latency: 8.813891ms
      message: 'load-balancer-api-internal: resolved host name a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:40:33Z"
    - latency: 4.798588ms
      message: 'load-balancer-api-internal: tcp connection to a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:39:33Z"
    - latency: 10.572095ms
      message: 'load-balancer-api-internal: resolved host name a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:39:33Z"
    - latency: 5.988959ms
      message: 'load-balancer-api-internal: tcp connection to a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:38:33Z"
    - latency: 13.221947ms
      message: 'load-balancer-api-internal: resolved host name a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:38:33Z"
    - latency: 4.809594ms
      message: 'load-balancer-api-internal: tcp connection to a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:37:33Z"
    - latency: 8.379035ms
      message: 'load-balancer-api-internal: resolved host name a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:37:33Z"
    - latency: 4.931038ms
      message: 'load-balancer-api-internal: tcp connection to a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:36:33Z"
    - latency: 10.864333ms
      message: 'load-balancer-api-internal: resolved host name a191cd2b7036f4b88ab21b4a1b033494-c8ad9fb560985c6f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:36:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T10:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-82-to-network-check-target-ip-10-0-132-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-82.ec2.internal
      uid: 1b203a1c-3ed5-4a3d-81f4-450be5729ea5
    resourceVersion: "54813"
    uid: 5dc05280-87fe-4dd5-94fd-3897c8304476
  spec:
    sourcePod: network-check-source-869dcfcdcd-w59l6
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T10:11:33Z"
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.640174ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:39:33Z"
    - latency: 2.353201ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:38:33Z"
    - latency: 2.464256ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:37:33Z"
    - latency: 2.105843ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:36:33Z"
    - latency: 2.585503ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:35:33Z"
    - latency: 2.563629ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:34:33Z"
    - latency: 2.269237ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:33:33Z"
    - latency: 2.218567ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:32:33Z"
    - latency: 1.89487ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:31:33Z"
    - latency: 2.606605ms
      message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:30:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T10:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-82-to-network-check-target-ip-10-0-139-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-82.ec2.internal
      uid: 1b203a1c-3ed5-4a3d-81f4-450be5729ea5
    resourceVersion: "54810"
    uid: d03eb93e-971c-4543-b326-c6d42fbf2e33
  spec:
    sourcePod: network-check-source-869dcfcdcd-w59l6
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T10:11:33Z"
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 952.581µs
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:39:33Z"
    - latency: 1.618379ms
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:38:33Z"
    - latency: 977.23µs
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:37:33Z"
    - latency: 1.103572ms
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:36:33Z"
    - latency: 936.842µs
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:35:33Z"
    - latency: 1.158766ms
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:34:33Z"
    - latency: 972.707µs
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:33:33Z"
    - latency: 1.771806ms
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:32:33Z"
    - latency: 874.457µs
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:31:33Z"
    - latency: 922.27µs
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:30:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T10:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-82-to-network-check-target-ip-10-0-141-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-82.ec2.internal
      uid: 1b203a1c-3ed5-4a3d-81f4-450be5729ea5
    resourceVersion: "54811"
    uid: 45955068-a0de-4a3d-b5a6-3b5ca7e84f6a
  spec:
    sourcePod: network-check-source-869dcfcdcd-w59l6
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T10:11:33Z"
      message: 'network-check-target-ip-10-0-141-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.333229ms
      message: 'network-check-target-ip-10-0-141-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:39:33Z"
    - latency: 2.325638ms
      message: 'network-check-target-ip-10-0-141-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:38:33Z"
    - latency: 2.37118ms
      message: 'network-check-target-ip-10-0-141-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:37:33Z"
    - latency: 2.334072ms
      message: 'network-check-target-ip-10-0-141-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:36:33Z"
    - latency: 2.219064ms
      message: 'network-check-target-ip-10-0-141-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:35:33Z"
    - latency: 2.310772ms
      message: 'network-check-target-ip-10-0-141-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:34:33Z"
    - latency: 2.25802ms
      message: 'network-check-target-ip-10-0-141-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:33:33Z"
    - latency: 2.209157ms
      message: 'network-check-target-ip-10-0-141-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:32:33Z"
    - latency: 2.029075ms
      message: 'network-check-target-ip-10-0-141-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:31:33Z"
    - latency: 2.067508ms
      message: 'network-check-target-ip-10-0-141-78: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:30:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T10:04:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-82-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-82.ec2.internal
      uid: 1b203a1c-3ed5-4a3d-81f4-450be5729ea5
    resourceVersion: "55766"
    uid: c12cc9ba-8ed3-4373-8995-73a02c9f6959
  spec:
    sourcePod: network-check-source-869dcfcdcd-w59l6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T10:10:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.069247ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:40:33Z"
    - latency: 2.505103ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:40:33Z"
    - latency: 1.106691ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:39:33Z"
    - latency: 1.755343ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:39:33Z"
    - latency: 929.771µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:38:33Z"
    - latency: 2.123508ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:38:33Z"
    - latency: 846.305µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:37:33Z"
    - latency: 2.590899ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:37:33Z"
    - latency: 1.076438ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T10:36:33Z"
    - latency: 2.701583ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T10:36:33Z"
kind: List
metadata:
  resourceVersion: ""