apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:04:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-200-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-200.ec2.internal
      uid: 7edd7326-6365-4985-b78d-3baf697ea628
    resourceVersion: "55519"
    uid: f3a8f0a3-86d7-4b37-9a9a-38b96ec3b94a
  spec:
    sourcePod: network-check-source-869dcfcdcd-2ptnr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:11:21Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.468073ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:39:21Z"
    - latency: 1.021148ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:38:21Z"
    - latency: 749.863µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:37:21Z"
    - latency: 912.333µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:36:21Z"
    - latency: 1.312625ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:35:21Z"
    - latency: 1.446891ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:34:21Z"
    - latency: 856.098µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:33:21Z"
    - latency: 1.173837ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:32:21Z"
    - latency: 871.007µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:31:21Z"
    - latency: 1.226283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:30:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:04:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-200-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-200.ec2.internal
      uid: 7edd7326-6365-4985-b78d-3baf697ea628
    resourceVersion: "56491"
    uid: 64011e49-c054-405b-b0de-196a77f4e9fb
  spec:
    sourcePod: network-check-source-869dcfcdcd-2ptnr
    targetEndpoint: a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:10:21Z"
      message: 'load-balancer-api-external: tcp connection to a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.675007ms
      message: 'load-balancer-api-external: tcp connection to a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:40:21Z"
    - latency: 6.69953ms
      message: 'load-balancer-api-external: resolved host name a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:40:21Z"
    - latency: 4.236417ms
      message: 'load-balancer-api-external: tcp connection to a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:39:21Z"
    - latency: 6.835037ms
      message: 'load-balancer-api-external: resolved host name a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:39:21Z"
    - latency: 4.517922ms
      message: 'load-balancer-api-external: tcp connection to a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:38:21Z"
    - latency: 6.7885ms
      message: 'load-balancer-api-external: resolved host name a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:38:21Z"
    - latency: 3.605638ms
      message: 'load-balancer-api-external: tcp connection to a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:37:21Z"
    - latency: 8.513913ms
      message: 'load-balancer-api-external: resolved host name a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:37:21Z"
    - latency: 5.212532ms
      message: 'load-balancer-api-external: tcp connection to a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:36:21Z"
    - latency: 6.539948ms
      message: 'load-balancer-api-external: resolved host name a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:36:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:04:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-200-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-200.ec2.internal
      uid: 7edd7326-6365-4985-b78d-3baf697ea628
    resourceVersion: "56490"
    uid: e4eea87c-3ac3-45cf-9a89-3009be7d2d4c
  spec:
    sourcePod: network-check-source-869dcfcdcd-2ptnr
    targetEndpoint: a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:10:21Z"
      message: 'load-balancer-api-internal: tcp connection to a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.907432ms
      message: 'load-balancer-api-internal: tcp connection to a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:40:21Z"
    - latency: 6.609735ms
      message: 'load-balancer-api-internal: resolved host name a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:40:21Z"
    - latency: 4.266323ms
      message: 'load-balancer-api-internal: tcp connection to a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:39:21Z"
    - latency: 6.76055ms
      message: 'load-balancer-api-internal: resolved host name a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:39:21Z"
    - latency: 4.49512ms
      message: 'load-balancer-api-internal: tcp connection to a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:38:21Z"
    - latency: 6.810927ms
      message: 'load-balancer-api-internal: resolved host name a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:38:21Z"
    - latency: 4.582828ms
      message: 'load-balancer-api-internal: tcp connection to a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:37:21Z"
    - latency: 8.445443ms
      message: 'load-balancer-api-internal: resolved host name a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:37:21Z"
    - latency: 5.230965ms
      message: 'load-balancer-api-internal: tcp connection to a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:36:21Z"
    - latency: 6.567758ms
      message: 'load-balancer-api-internal: resolved host name a35bbc567d66643948cb9a8fe36e60da-c55ca2afc472d5ee.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:36:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:04:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-200-to-network-check-target-ip-10-0-136-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-200.ec2.internal
      uid: 7edd7326-6365-4985-b78d-3baf697ea628
    resourceVersion: "55516"
    uid: 23ac8e91-7f8b-4fe8-968a-2e6d2b77f350
  spec:
    sourcePod: network-check-source-869dcfcdcd-2ptnr
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:11:21Z"
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.147361ms
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:39:21Z"
    - latency: 934.028µs
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:38:21Z"
    - latency: 1.342443ms
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:37:21Z"
    - latency: 1.002655ms
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:36:21Z"
    - latency: 775.973µs
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:35:21Z"
    - latency: 1.109058ms
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:34:21Z"
    - latency: 658.65µs
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:33:21Z"
    - latency: 875.552µs
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:32:21Z"
    - latency: 933.274µs
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:31:21Z"
    - latency: 1.239793ms
      message: 'network-check-target-ip-10-0-136-200: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:30:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:04:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-200-to-network-check-target-ip-10-0-138-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-200.ec2.internal
      uid: 7edd7326-6365-4985-b78d-3baf697ea628
    resourceVersion: "55518"
    uid: b9608399-0773-4a0e-8de7-9ea7380f849c
  spec:
    sourcePod: network-check-source-869dcfcdcd-2ptnr
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:11:21Z"
      message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.716203ms
      message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:39:21Z"
    - latency: 2.370961ms
      message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:38:21Z"
    - latency: 2.369684ms
      message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:37:21Z"
    - latency: 2.154072ms
      message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:36:21Z"
    - latency: 2.576544ms
      message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:35:21Z"
    - latency: 2.385895ms
      message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:34:21Z"
    - latency: 1.979445ms
      message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:33:21Z"
    - latency: 2.124722ms
      message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:32:21Z"
    - latency: 2.278758ms
      message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:31:21Z"
    - latency: 1.997761ms
      message: 'network-check-target-ip-10-0-138-201: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:30:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:04:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-200-to-network-check-target-ip-10-0-139-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-200.ec2.internal
      uid: 7edd7326-6365-4985-b78d-3baf697ea628
    resourceVersion: "55517"
    uid: 4c4b3787-380a-4e29-8420-1884cf0f5e32
  spec:
    sourcePod: network-check-source-869dcfcdcd-2ptnr
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:11:21Z"
      message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.385325ms
      message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:39:21Z"
    - latency: 2.458543ms
      message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:38:21Z"
    - latency: 2.48127ms
      message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:37:21Z"
    - latency: 2.661908ms
      message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:36:21Z"
    - latency: 2.435867ms
      message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:35:21Z"
    - latency: 2.754409ms
      message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:34:21Z"
    - latency: 1.814726ms
      message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:33:21Z"
    - latency: 2.686428ms
      message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:32:21Z"
    - latency: 2.722795ms
      message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:31:21Z"
    - latency: 2.254541ms
      message: 'network-check-target-ip-10-0-139-9: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:30:21Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:04:20Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-200-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-200.ec2.internal
      uid: 7edd7326-6365-4985-b78d-3baf697ea628
    resourceVersion: "56489"
    uid: 7210bf45-45cc-4084-8b28-a3bed8e6f9a0
  spec:
    sourcePod: network-check-source-869dcfcdcd-2ptnr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:10:21Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.025661ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:40:21Z"
    - latency: 1.64381ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:40:21Z"
    - latency: 1.223345ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:39:21Z"
    - latency: 1.793434ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:39:21Z"
    - latency: 955.687µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:38:21Z"
    - latency: 2.178524ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:38:21Z"
    - latency: 779.474µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:37:21Z"
    - latency: 1.655604ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:37:21Z"
    - latency: 721.906µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T18:36:21Z"
    - latency: 1.591307ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T18:36:21Z"
kind: List
metadata:
  resourceVersion: ""