apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T11:04:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-230-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-230.ec2.internal
      uid: 980eb1d1-5198-4990-b802-e02623f07d38
    resourceVersion: "63266"
    uid: e30198fd-9853-4722-adb3-60ed5fbf0769
  spec:
    sourcePod: network-check-source-6f8b768455-c8qsb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T11:11:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.335384ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:39:26Z"
    - latency: 1.115519ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:38:26Z"
    - latency: 1.108268ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:37:26Z"
    - latency: 1.504044ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:36:26Z"
    - latency: 1.349666ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:35:26Z"
    - latency: 1.177456ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:34:26Z"
    - latency: 1.242391ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:33:26Z"
    - latency: 1.381463ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:32:26Z"
    - latency: 1.758093ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:31:26Z"
    - latency: 1.560343ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T11:04:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-230-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-230.ec2.internal
      uid: 980eb1d1-5198-4990-b802-e02623f07d38
    resourceVersion: "63985"
    uid: 6d718bf4-b825-406b-b251-5107e2dacbc8
  spec:
    sourcePod: network-check-source-6f8b768455-c8qsb
    targetEndpoint: a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T11:10:26Z"
      message: 'load-balancer-api-external: tcp connection to a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.534731ms
      message: 'load-balancer-api-external: tcp connection to a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:40:26Z"
    - latency: 6.966111ms
      message: 'load-balancer-api-external: resolved host name a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:40:26Z"
    - latency: 5.077778ms
      message: 'load-balancer-api-external: tcp connection to a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:39:26Z"
    - latency: 7.097391ms
      message: 'load-balancer-api-external: resolved host name a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:39:26Z"
    - latency: 4.752447ms
      message: 'load-balancer-api-external: tcp connection to a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:38:26Z"
    - latency: 7.323426ms
      message: 'load-balancer-api-external: resolved host name a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:38:26Z"
    - latency: 5.423841ms
      message: 'load-balancer-api-external: tcp connection to a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:37:26Z"
    - latency: 6.834657ms
      message: 'load-balancer-api-external: resolved host name a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:37:26Z"
    - latency: 4.490517ms
      message: 'load-balancer-api-external: tcp connection to a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:36:26Z"
    - latency: 6.647557ms
      message: 'load-balancer-api-external: resolved host name a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:36:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T11:04:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-230-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-230.ec2.internal
      uid: 980eb1d1-5198-4990-b802-e02623f07d38
    resourceVersion: "63984"
    uid: b4b46a1a-ae32-4f29-b8c1-c272ae93d166
  spec:
    sourcePod: network-check-source-6f8b768455-c8qsb
    targetEndpoint: a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T11:10:26Z"
      message: 'load-balancer-api-internal: tcp connection to a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.463066ms
      message: 'load-balancer-api-internal: tcp connection to a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:40:26Z"
    - latency: 6.864971ms
      message: 'load-balancer-api-internal: resolved host name a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:40:26Z"
    - latency: 5.154184ms
      message: 'load-balancer-api-internal: tcp connection to a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:39:26Z"
    - latency: 6.989508ms
      message: 'load-balancer-api-internal: resolved host name a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:39:26Z"
    - latency: 4.767535ms
      message: 'load-balancer-api-internal: tcp connection to a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:38:26Z"
    - latency: 7.264205ms
      message: 'load-balancer-api-internal: resolved host name a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:38:26Z"
    - latency: 3.664539ms
      message: 'load-balancer-api-internal: tcp connection to a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:37:26Z"
    - latency: 6.716449ms
      message: 'load-balancer-api-internal: resolved host name a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:37:26Z"
    - latency: 4.507283ms
      message: 'load-balancer-api-internal: tcp connection to a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:36:26Z"
    - latency: 6.545639ms
      message: 'load-balancer-api-internal: resolved host name a76918ca9e5814b84991c139a3edae4b-19bae482f448df06.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:36:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T11:04:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-230-to-network-check-target-ip-10-0-137-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-230.ec2.internal
      uid: 980eb1d1-5198-4990-b802-e02623f07d38
    resourceVersion: "63263"
    uid: 5a7d06ee-86b1-49b8-8bb5-559aee14a638
  spec:
    sourcePod: network-check-source-6f8b768455-c8qsb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T11:11:26Z"
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.036633ms
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:39:26Z"
    - latency: 1.031575ms
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:38:26Z"
    - latency: 1.102509ms
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:37:26Z"
    - latency: 1.485782ms
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:36:26Z"
    - latency: 1.30389ms
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:35:26Z"
    - latency: 1.997665ms
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:34:26Z"
    - latency: 1.118463ms
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:33:26Z"
    - latency: 1.804945ms
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:32:26Z"
    - latency: 1.682144ms
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:31:26Z"
    - latency: 1.778676ms
      message: 'network-check-target-ip-10-0-137-230: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T11:04:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-230-to-network-check-target-ip-10-0-143-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-230.ec2.internal
      uid: 980eb1d1-5198-4990-b802-e02623f07d38
    resourceVersion: "63264"
    uid: 0ff50595-99eb-45a0-a7b7-12bf3bf9f340
  spec:
    sourcePod: network-check-source-6f8b768455-c8qsb
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T11:11:26Z"
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.935482ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:39:26Z"
    - latency: 2.504353ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:38:26Z"
    - latency: 2.397136ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:37:26Z"
    - latency: 2.60936ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:36:26Z"
    - latency: 2.556099ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:35:26Z"
    - latency: 2.626429ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:34:26Z"
    - latency: 2.597449ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:33:26Z"
    - latency: 3.391577ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:32:26Z"
    - latency: 2.54581ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:31:26Z"
    - latency: 2.497247ms
      message: 'network-check-target-ip-10-0-143-154: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T11:04:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-230-to-network-check-target-ip-10-0-143-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-230.ec2.internal
      uid: 980eb1d1-5198-4990-b802-e02623f07d38
    resourceVersion: "63265"
    uid: fe02bccc-e1c6-4a7b-af27-80592800c9cc
  spec:
    sourcePod: network-check-source-6f8b768455-c8qsb
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T11:11:26Z"
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.449754ms
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:39:26Z"
    - latency: 2.378519ms
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:38:26Z"
    - latency: 2.135248ms
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:37:26Z"
    - latency: 2.479269ms
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:36:26Z"
    - latency: 2.399744ms
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:35:26Z"
    - latency: 2.638162ms
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:34:26Z"
    - latency: 2.550985ms
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:33:26Z"
    - latency: 3.486717ms
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:32:26Z"
    - latency: 2.368758ms
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:31:26Z"
    - latency: 2.80135ms
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T11:04:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-230-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-230.ec2.internal
      uid: 980eb1d1-5198-4990-b802-e02623f07d38
    resourceVersion: "63983"
    uid: 7c470a59-351b-400d-b974-93a2987f2dc2
  spec:
    sourcePod: network-check-source-6f8b768455-c8qsb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T11:10:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.090111ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:40:26Z"
    - latency: 1.774153ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:40:26Z"
    - latency: 1.350131ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:39:26Z"
    - latency: 1.906599ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:39:26Z"
    - latency: 1.018057ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:38:26Z"
    - latency: 1.994886ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:38:26Z"
    - latency: 1.147482ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:37:26Z"
    - latency: 1.972725ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:37:26Z"
    - latency: 1.39536ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T11:36:26Z"
    - latency: 2.010206ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T11:36:26Z"
kind: List
metadata:
  resourceVersion: ""