apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:41:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-65-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-65.ec2.internal
      uid: df3fb418-f549-4ae6-a28b-5d2a576521fa
    resourceVersion: "56637"
    uid: b05d3c2a-9f80-4719-850c-79fd4f83ea60
  spec:
    sourcePod: network-check-source-989f8b8dc-tnw86
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:48: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.150541ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:26Z"
    - latency: 1.005182ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:26Z"
    - latency: 1.519321ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:26Z"
    - latency: 1.23915ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:26Z"
    - latency: 913.347µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:12:26Z"
    - latency: 957.744µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:11:26Z"
    - latency: 960.754µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:10:26Z"
    - latency: 1.054975ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:09:26Z"
    - latency: 1.155957ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:08:26Z"
    - latency: 1.030033ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:07:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:41:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-65-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-65.ec2.internal
      uid: df3fb418-f549-4ae6-a28b-5d2a576521fa
    resourceVersion: "57648"
    uid: 5bcc61c1-3b95-43a5-834b-fe2ba4aa202a
  spec:
    sourcePod: network-check-source-989f8b8dc-tnw86
    targetEndpoint: abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:47:26Z"
      message: 'load-balancer-api-external: tcp connection to abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.766208ms
      message: 'load-balancer-api-external: tcp connection to abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:17:26Z"
    - latency: 9.066354ms
      message: 'load-balancer-api-external: resolved host name abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:17:26Z"
    - latency: 3.976998ms
      message: 'load-balancer-api-external: tcp connection to abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:26Z"
    - latency: 9.643634ms
      message: 'load-balancer-api-external: resolved host name abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:16:26Z"
    - latency: 7.393525ms
      message: 'load-balancer-api-external: tcp connection to abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:26Z"
    - latency: 8.314837ms
      message: 'load-balancer-api-external: resolved host name abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:15:26Z"
    - latency: 3.15023ms
      message: 'load-balancer-api-external: tcp connection to abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:26Z"
    - latency: 8.037508ms
      message: 'load-balancer-api-external: resolved host name abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:14:26Z"
    - latency: 4.724095ms
      message: 'load-balancer-api-external: tcp connection to abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:26Z"
    - latency: 8.304981ms
      message: 'load-balancer-api-external: resolved host name abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:13:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:41:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-65-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-65.ec2.internal
      uid: df3fb418-f549-4ae6-a28b-5d2a576521fa
    resourceVersion: "57649"
    uid: e09c9cd1-21d8-4a92-ab7a-5583e217dcfa
  spec:
    sourcePod: network-check-source-989f8b8dc-tnw86
    targetEndpoint: abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:47:26Z"
      message: 'load-balancer-api-internal: tcp connection to abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.471784ms
      message: 'load-balancer-api-internal: tcp connection to abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:17:26Z"
    - latency: 9.008951ms
      message: 'load-balancer-api-internal: resolved host name abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:17:26Z"
    - latency: 4.865884ms
      message: 'load-balancer-api-internal: tcp connection to abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:26Z"
    - latency: 9.718151ms
      message: 'load-balancer-api-internal: resolved host name abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:16:26Z"
    - latency: 7.269451ms
      message: 'load-balancer-api-internal: tcp connection to abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:26Z"
    - latency: 8.354076ms
      message: 'load-balancer-api-internal: resolved host name abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:15:26Z"
    - latency: 4.194824ms
      message: 'load-balancer-api-internal: tcp connection to abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:26Z"
    - latency: 7.957254ms
      message: 'load-balancer-api-internal: resolved host name abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:14:26Z"
    - latency: 3.844325ms
      message: 'load-balancer-api-internal: tcp connection to abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:26Z"
    - latency: 8.224628ms
      message: 'load-balancer-api-internal: resolved host name abdf7481711e64bbfb23abcbbcc3edbf-ccf07e45c4dd3388.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:13:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:41:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-65-to-network-check-target-ip-10-0-128-115
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-65.ec2.internal
      uid: df3fb418-f549-4ae6-a28b-5d2a576521fa
    resourceVersion: "56636"
    uid: a8c007f1-c40d-4d57-bed8-8a02e19e455e
  spec:
    sourcePod: network-check-source-989f8b8dc-tnw86
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:48:26Z"
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.212781ms
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:26Z"
    - latency: 2.40193ms
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:26Z"
    - latency: 2.121375ms
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:26Z"
    - latency: 2.201417ms
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:26Z"
    - latency: 2.173806ms
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:12:26Z"
    - latency: 2.332309ms
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:11:26Z"
    - latency: 2.570108ms
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:10:26Z"
    - latency: 2.353318ms
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:09:26Z"
    - latency: 1.967668ms
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:08:26Z"
    - latency: 2.398059ms
      message: 'network-check-target-ip-10-0-128-115: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:07:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:41:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-65-to-network-check-target-ip-10-0-129-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-65.ec2.internal
      uid: df3fb418-f549-4ae6-a28b-5d2a576521fa
    resourceVersion: "56634"
    uid: 0a0f1686-c0b4-41a6-8548-be18063d4fc0
  spec:
    sourcePod: network-check-source-989f8b8dc-tnw86
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:48:26Z"
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.369836ms
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:26Z"
    - latency: 1.170983ms
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:26Z"
    - latency: 845.322µs
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:26Z"
    - latency: 974.51µs
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:26Z"
    - latency: 768.185µs
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:12:26Z"
    - latency: 886.752µs
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:11:26Z"
    - latency: 944.644µs
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:10:26Z"
    - latency: 900.984µs
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:09:26Z"
    - latency: 915.66µs
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:08:26Z"
    - latency: 1.410688ms
      message: 'network-check-target-ip-10-0-129-65: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:07:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:41:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-65-to-network-check-target-ip-10-0-134-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-65.ec2.internal
      uid: df3fb418-f549-4ae6-a28b-5d2a576521fa
    resourceVersion: "56635"
    uid: 4429f51f-0731-46e2-941f-c876d1a48d41
  spec:
    sourcePod: network-check-source-989f8b8dc-tnw86
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:48:26Z"
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.655122ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:26Z"
    - latency: 2.673662ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:26Z"
    - latency: 2.214862ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:26Z"
    - latency: 2.005123ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:26Z"
    - latency: 2.522249ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:12:26Z"
    - latency: 2.264688ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:11:26Z"
    - latency: 2.600014ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:10:26Z"
    - latency: 2.514055ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:09:26Z"
    - latency: 2.556727ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:08:26Z"
    - latency: 2.409252ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:07:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T17:41:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-65-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-65.ec2.internal
      uid: df3fb418-f549-4ae6-a28b-5d2a576521fa
    resourceVersion: "57647"
    uid: 31f61679-61d9-4fca-93c1-f4dae7474374
  spec:
    sourcePod: network-check-source-989f8b8dc-tnw86
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T17:47:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.325446ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:17:26Z"
    - latency: 1.728506ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:17:26Z"
    - latency: 1.345821ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:26Z"
    - latency: 2.281272ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:16:26Z"
    - latency: 900.732µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:26Z"
    - latency: 1.786658ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:15:26Z"
    - latency: 880.25µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:26Z"
    - latency: 1.699683ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:14:26Z"
    - latency: 1.033468ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:26Z"
    - latency: 1.774584ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:13:26Z"
kind: List
metadata:
  resourceVersion: ""