apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T01:45:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-87-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-87.ec2.internal
      uid: 0ce57b47-9bc1-4872-8390-1d2b98280270
    resourceVersion: "71991"
    uid: 5cbde14d-9b5f-4da3-a831-bc81b368148a
  spec:
    sourcePod: network-check-source-65bdbbff45-wd4qp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T01:52:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.066398ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:34:18Z"
    - latency: 761.985µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:33:18Z"
    - latency: 1.166029ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:32:18Z"
    - latency: 1.335325ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:31:18Z"
    - latency: 1.42399ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:30:18Z"
    - latency: 937.596µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:29:18Z"
    - latency: 1.046211ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:28:18Z"
    - latency: 1.234249ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:27:18Z"
    - latency: 1.305694ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:26:18Z"
    - latency: 1.146925ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:25:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T01:45:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-87-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-87.ec2.internal
      uid: 0ce57b47-9bc1-4872-8390-1d2b98280270
    resourceVersion: "77110"
    uid: aa0e9883-5e2c-436a-9679-a79a7a52549b
  spec:
    sourcePod: network-check-source-65bdbbff45-wd4qp
    targetEndpoint: af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T01:51:18Z"
      message: 'load-balancer-api-external: tcp connection to af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.907658ms
      message: 'load-balancer-api-external: tcp connection to af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:39:18Z"
    - latency: 8.848245ms
      message: 'load-balancer-api-external: resolved host name af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T02:39:18Z"
    - latency: 4.689387ms
      message: 'load-balancer-api-external: tcp connection to af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:38:18Z"
    - latency: 8.491924ms
      message: 'load-balancer-api-external: resolved host name af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T02:38:18Z"
    - latency: 4.765875ms
      message: 'load-balancer-api-external: tcp connection to af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:37:18Z"
    - latency: 8.227899ms
      message: 'load-balancer-api-external: resolved host name af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T02:37:18Z"
    - latency: 3.179425ms
      message: 'load-balancer-api-external: tcp connection to af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:36:18Z"
    - latency: 7.450327ms
      message: 'load-balancer-api-external: resolved host name af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T02:36:18Z"
    - latency: 5.244383ms
      message: 'load-balancer-api-external: tcp connection to af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:35:18Z"
    - latency: 9.298203ms
      message: 'load-balancer-api-external: resolved host name af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T02:35:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T01:45:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-87-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-87.ec2.internal
      uid: 0ce57b47-9bc1-4872-8390-1d2b98280270
    resourceVersion: "77109"
    uid: e19aab76-9fac-4a7a-9e1b-0ffc5b88a512
  spec:
    sourcePod: network-check-source-65bdbbff45-wd4qp
    targetEndpoint: af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T01:51:18Z"
      message: 'load-balancer-api-internal: tcp connection to af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.532468ms
      message: 'load-balancer-api-internal: tcp connection to af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:39:18Z"
    - latency: 8.899831ms
      message: 'load-balancer-api-internal: resolved host name af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T02:39:18Z"
    - latency: 4.601372ms
      message: 'load-balancer-api-internal: tcp connection to af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:38:18Z"
    - latency: 8.558321ms
      message: 'load-balancer-api-internal: resolved host name af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T02:38:18Z"
    - latency: 3.469941ms
      message: 'load-balancer-api-internal: tcp connection to af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:37:18Z"
    - latency: 8.28344ms
      message: 'load-balancer-api-internal: resolved host name af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T02:37:18Z"
    - latency: 4.254434ms
      message: 'load-balancer-api-internal: tcp connection to af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:36:18Z"
    - latency: 7.503057ms
      message: 'load-balancer-api-internal: resolved host name af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T02:36:18Z"
    - latency: 3.298126ms
      message: 'load-balancer-api-internal: tcp connection to af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:35:18Z"
    - latency: 9.360153ms
      message: 'load-balancer-api-internal: resolved host name af8db6ab7e71c4062b30713500d2fc6c-5a4a0ba6209182a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T02:35:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T01:45:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-87-to-network-check-target-ip-10-0-133-91
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-87.ec2.internal
      uid: 0ce57b47-9bc1-4872-8390-1d2b98280270
    resourceVersion: "71988"
    uid: ebc3d98c-6eb0-4ebd-9b6c-0e1da4b6ab6d
  spec:
    sourcePod: network-check-source-65bdbbff45-wd4qp
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T01:52:18Z"
      message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.983432ms
      message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:34:18Z"
    - latency: 2.490075ms
      message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:33:18Z"
    - latency: 2.180817ms
      message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:32:18Z"
    - latency: 2.076492ms
      message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:31:18Z"
    - latency: 2.000827ms
      message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:30:18Z"
    - latency: 2.12004ms
      message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:29:18Z"
    - latency: 2.173149ms
      message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:28:18Z"
    - latency: 2.250033ms
      message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:27:18Z"
    - latency: 2.294304ms
      message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:26:18Z"
    - latency: 2.306969ms
      message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:25:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T01:45:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-87-to-network-check-target-ip-10-0-140-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-87.ec2.internal
      uid: 0ce57b47-9bc1-4872-8390-1d2b98280270
    resourceVersion: "71990"
    uid: 1566d5ea-cd15-4f5f-b99c-a1f2bb795ae8
  spec:
    sourcePod: network-check-source-65bdbbff45-wd4qp
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T01:52:18Z"
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 793.095µs
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:34:18Z"
    - latency: 874.131µs
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:33:18Z"
    - latency: 1.498995ms
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:32:18Z"
    - latency: 1.409634ms
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:31:18Z"
    - latency: 1.17683ms
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:30:18Z"
    - latency: 783.746µs
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:29:18Z"
    - latency: 913.553µs
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:28:18Z"
    - latency: 1.385915ms
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:27:18Z"
    - latency: 1.129364ms
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:26:18Z"
    - latency: 1.311087ms
      message: 'network-check-target-ip-10-0-140-87: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:25:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T01:45:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-87-to-network-check-target-ip-10-0-141-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-87.ec2.internal
      uid: 0ce57b47-9bc1-4872-8390-1d2b98280270
    resourceVersion: "71989"
    uid: e85dd3fb-a9c5-4b17-904d-a3a5e7211263
  spec:
    sourcePod: network-check-source-65bdbbff45-wd4qp
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T01:52:18Z"
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.637446ms
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:34:18Z"
    - latency: 1.696317ms
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:33:18Z"
    - latency: 1.686558ms
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:32:18Z"
    - latency: 1.709337ms
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:31:18Z"
    - latency: 1.634461ms
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:30:18Z"
    - latency: 1.618282ms
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:29:18Z"
    - latency: 1.669264ms
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:28:18Z"
    - latency: 1.815835ms
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:27:18Z"
    - latency: 1.849336ms
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:26:18Z"
    - latency: 1.913321ms
      message: 'network-check-target-ip-10-0-141-142: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:25:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T01:45:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-87-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-87.ec2.internal
      uid: 0ce57b47-9bc1-4872-8390-1d2b98280270
    resourceVersion: "77108"
    uid: 0525f8a1-092b-4917-bd07-03c26b2ed087
  spec:
    sourcePod: network-check-source-65bdbbff45-wd4qp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T01:51:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 619.523µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:39:18Z"
    - latency: 2.113696ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T02:39:18Z"
    - latency: 835.592µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:38:18Z"
    - latency: 1.700468ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T02:38:18Z"
    - latency: 798.621µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:37:18Z"
    - latency: 1.798838ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T02:37:18Z"
    - latency: 724.705µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:36:18Z"
    - latency: 1.769689ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T02:36:18Z"
    - latency: 937.739µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T02:35:18Z"
    - latency: 1.645696ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T02:35:18Z"
kind: List
metadata:
  resourceVersion: ""