apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:55:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-211-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-211.ec2.internal
      uid: 391c7d46-bd31-463b-b835-f4dc8343665e
    resourceVersion: "62953"
    uid: 0d876413-fb08-437f-9c45-3a91d4fbd385
  spec:
    sourcePod: network-check-source-685456655f-j86lt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T00:02:14Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.076172ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:30:14Z"
    - latency: 852.601µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:29:14Z"
    - latency: 1.063838ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:28:14Z"
    - latency: 987.371µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:27:14Z"
    - latency: 1.021946ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:26:14Z"
    - latency: 1.333592ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:25:14Z"
    - latency: 1.032077ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:24:14Z"
    - latency: 1.774438ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:23:14Z"
    - latency: 983.988µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:22:14Z"
    - latency: 961.731µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:21:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:55:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-211-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-211.ec2.internal
      uid: 391c7d46-bd31-463b-b835-f4dc8343665e
    resourceVersion: "63880"
    uid: fa6fddf9-ed35-45f0-9bb4-268529d35af8
  spec:
    sourcePod: network-check-source-685456655f-j86lt
    targetEndpoint: aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T00:01:14Z"
      message: 'load-balancer-api-external: tcp connection to aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.057189ms
      message: 'load-balancer-api-external: tcp connection to aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:31:14Z"
    - latency: 7.251484ms
      message: 'load-balancer-api-external: resolved host name aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:31:14Z"
    - latency: 6.242962ms
      message: 'load-balancer-api-external: tcp connection to aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:30:14Z"
    - latency: 8.083612ms
      message: 'load-balancer-api-external: resolved host name aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:30:14Z"
    - latency: 5.416752ms
      message: 'load-balancer-api-external: tcp connection to aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:29:14Z"
    - latency: 7.056311ms
      message: 'load-balancer-api-external: resolved host name aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:29:14Z"
    - latency: 5.063858ms
      message: 'load-balancer-api-external: tcp connection to aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:28:14Z"
    - latency: 9.127351ms
      message: 'load-balancer-api-external: resolved host name aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:28:14Z"
    - latency: 5.818108ms
      message: 'load-balancer-api-external: tcp connection to aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:27:14Z"
    - latency: 7.804072ms
      message: 'load-balancer-api-external: resolved host name aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:27:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:55:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-211-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-211.ec2.internal
      uid: 391c7d46-bd31-463b-b835-f4dc8343665e
    resourceVersion: "63881"
    uid: 50087308-f271-446a-8a2a-c91c44986978
  spec:
    sourcePod: network-check-source-685456655f-j86lt
    targetEndpoint: aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T00:01:14Z"
      message: 'load-balancer-api-internal: tcp connection to aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.112981ms
      message: 'load-balancer-api-internal: tcp connection to aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:31:14Z"
    - latency: 7.310303ms
      message: 'load-balancer-api-internal: resolved host name aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:31:14Z"
    - latency: 4.992695ms
      message: 'load-balancer-api-internal: tcp connection to aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:30:14Z"
    - latency: 8.121175ms
      message: 'load-balancer-api-internal: resolved host name aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:30:14Z"
    - latency: 4.656848ms
      message: 'load-balancer-api-internal: tcp connection to aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:29:14Z"
    - latency: 7.174154ms
      message: 'load-balancer-api-internal: resolved host name aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:29:14Z"
    - latency: 3.754275ms
      message: 'load-balancer-api-internal: tcp connection to aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:28:14Z"
    - latency: 9.157501ms
      message: 'load-balancer-api-internal: resolved host name aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:28:14Z"
    - latency: 5.29959ms
      message: 'load-balancer-api-internal: tcp connection to aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:27:14Z"
    - latency: 7.778136ms
      message: 'load-balancer-api-internal: resolved host name aa0dbfb78daad4f239e4284469fa2f51-0026df000898628d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:27:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:55:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-211-to-network-check-target-ip-10-0-128-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-211.ec2.internal
      uid: 391c7d46-bd31-463b-b835-f4dc8343665e
    resourceVersion: "62950"
    uid: 4805c88e-2207-4a2b-90a9-f697cf2f9fef
  spec:
    sourcePod: network-check-source-685456655f-j86lt
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T00:02:14Z"
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.896154ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:30:14Z"
    - latency: 1.872033ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:29:14Z"
    - latency: 1.728028ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:28:14Z"
    - latency: 1.761628ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:27:14Z"
    - latency: 1.783631ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:26:14Z"
    - latency: 2.055271ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:25:14Z"
    - latency: 1.908479ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:24:14Z"
    - latency: 1.97306ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:23:14Z"
    - latency: 1.945536ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:22:14Z"
    - latency: 1.922804ms
      message: 'network-check-target-ip-10-0-128-118: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:21:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:55:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-211-to-network-check-target-ip-10-0-135-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-211.ec2.internal
      uid: 391c7d46-bd31-463b-b835-f4dc8343665e
    resourceVersion: "62951"
    uid: ce1a5a1c-4423-46fe-b293-732027fa1d0c
  spec:
    sourcePod: network-check-source-685456655f-j86lt
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T00:02:14Z"
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.211701ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:30:14Z"
    - latency: 1.962818ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:29:14Z"
    - latency: 2.576888ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:28:14Z"
    - latency: 2.117973ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:27:14Z"
    - latency: 2.287432ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:26:14Z"
    - latency: 2.243845ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:25:14Z"
    - latency: 2.259765ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:24:14Z"
    - latency: 3.114106ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:23:14Z"
    - latency: 2.626816ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:22:14Z"
    - latency: 2.203541ms
      message: 'network-check-target-ip-10-0-135-244: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:21:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:55:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-211-to-network-check-target-ip-10-0-139-211
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-211.ec2.internal
      uid: 391c7d46-bd31-463b-b835-f4dc8343665e
    resourceVersion: "62949"
    uid: d4234d6b-c669-4b11-95e4-a6cd134646d1
  spec:
    sourcePod: network-check-source-685456655f-j86lt
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T00:02:14Z"
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 779.903µs
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:30:14Z"
    - latency: 841.336µs
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:29:14Z"
    - latency: 831.36µs
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:28:14Z"
    - latency: 828.928µs
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:27:14Z"
    - latency: 955.366µs
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:26:14Z"
    - latency: 1.457261ms
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:25:14Z"
    - latency: 1.34882ms
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:24:14Z"
    - latency: 922.863µs
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:23:14Z"
    - latency: 896.783µs
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:22:14Z"
    - latency: 1.092294ms
      message: 'network-check-target-ip-10-0-139-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:21:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:55:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-211-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-211.ec2.internal
      uid: 391c7d46-bd31-463b-b835-f4dc8343665e
    resourceVersion: "63878"
    uid: d3576baf-a156-49cb-8daa-1d1c7346bae3
  spec:
    sourcePod: network-check-source-685456655f-j86lt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T00:01:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 838.609µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:31:14Z"
    - latency: 1.642554ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:31:14Z"
    - latency: 1.036034ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:30:14Z"
    - latency: 1.735387ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:30:14Z"
    - latency: 891.355µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:29:14Z"
    - latency: 1.753086ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:29:14Z"
    - latency: 1.250291ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:28:14Z"
    - latency: 1.772369ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:28:14Z"
    - latency: 1.187174ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T00:27:14Z"
    - latency: 1.769649ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T00:27:14Z"
kind: List
metadata:
  resourceVersion: ""