apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T19:49:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-243-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-243.ec2.internal
      uid: 1e92c7ba-db7e-40da-8a43-11bc7c37f68c
    resourceVersion: "61068"
    uid: f6a0ffc5-ec1b-4b43-9a4d-c493b20f3789
  spec:
    sourcePod: network-check-source-869dcfcdcd-nt5s6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:56:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.642594ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:31:27Z"
    - latency: 1.443417ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:30:27Z"
    - latency: 1.269102ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:29:27Z"
    - latency: 937.613µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:28:27Z"
    - latency: 1.450151ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:27:27Z"
    - latency: 1.676165ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:26:27Z"
    - latency: 1.145768ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:25:27Z"
    - latency: 1.164646ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:24:27Z"
    - latency: 1.154419ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:23:27Z"
    - latency: 1.203924ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:22:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T19:49:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-243-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-243.ec2.internal
      uid: 1e92c7ba-db7e-40da-8a43-11bc7c37f68c
    resourceVersion: "61070"
    uid: 5164bd37-0606-42c3-b410-a2d8cdd9c13b
  spec:
    sourcePod: network-check-source-869dcfcdcd-nt5s6
    targetEndpoint: af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:55:27Z"
      message: 'load-balancer-api-external: tcp connection to af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.432582ms
      message: 'load-balancer-api-external: tcp connection to af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:31:27Z"
    - latency: 7.513367ms
      message: 'load-balancer-api-external: resolved host name af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:31:27Z"
    - latency: 6.613949ms
      message: 'load-balancer-api-external: tcp connection to af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:30:27Z"
    - latency: 9.210642ms
      message: 'load-balancer-api-external: resolved host name af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:30:27Z"
    - latency: 4.790628ms
      message: 'load-balancer-api-external: tcp connection to af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:29:27Z"
    - latency: 8.201318ms
      message: 'load-balancer-api-external: resolved host name af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:29:27Z"
    - latency: 5.397733ms
      message: 'load-balancer-api-external: tcp connection to af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:28:27Z"
    - latency: 7.157022ms
      message: 'load-balancer-api-external: resolved host name af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:28:27Z"
    - latency: 4.732559ms
      message: 'load-balancer-api-external: tcp connection to af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:27:27Z"
    - latency: 8.919426ms
      message: 'load-balancer-api-external: resolved host name af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:27:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T19:49:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-243-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-243.ec2.internal
      uid: 1e92c7ba-db7e-40da-8a43-11bc7c37f68c
    resourceVersion: "61071"
    uid: abcdbeed-4fba-4922-aa00-97f7dd0f1238
  spec:
    sourcePod: network-check-source-869dcfcdcd-nt5s6
    targetEndpoint: af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:55:27Z"
      message: 'load-balancer-api-internal: tcp connection to af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.138123ms
      message: 'load-balancer-api-internal: tcp connection to af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:31:27Z"
    - latency: 7.461541ms
      message: 'load-balancer-api-internal: resolved host name af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:31:27Z"
    - latency: 7.127897ms
      message: 'load-balancer-api-internal: tcp connection to af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:30:27Z"
    - latency: 9.119798ms
      message: 'load-balancer-api-internal: resolved host name af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:30:27Z"
    - latency: 4.779826ms
      message: 'load-balancer-api-internal: tcp connection to af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:29:27Z"
    - latency: 8.175475ms
      message: 'load-balancer-api-internal: resolved host name af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:29:27Z"
    - latency: 5.247445ms
      message: 'load-balancer-api-internal: tcp connection to af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:28:27Z"
    - latency: 7.103451ms
      message: 'load-balancer-api-internal: resolved host name af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:28:27Z"
    - latency: 4.714178ms
      message: 'load-balancer-api-internal: tcp connection to af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:27:27Z"
    - latency: 8.894651ms
      message: 'load-balancer-api-internal: resolved host name af75fccb58e3c46f2b66bb220f39c4ae-459156cc022d1666.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:27:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T19:49:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-243-to-network-check-target-ip-10-0-132-184
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-243.ec2.internal
      uid: 1e92c7ba-db7e-40da-8a43-11bc7c37f68c
    resourceVersion: "61066"
    uid: d6b9230b-8f01-4415-9e46-eec81bcce4d4
  spec:
    sourcePod: network-check-source-869dcfcdcd-nt5s6
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:56:27Z"
      message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.179843ms
      message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:31:27Z"
    - latency: 2.12981ms
      message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:30:27Z"
    - latency: 2.030474ms
      message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:29:27Z"
    - latency: 2.286422ms
      message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:28:27Z"
    - latency: 2.106548ms
      message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:27:27Z"
    - latency: 2.374864ms
      message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:26:27Z"
    - latency: 2.656123ms
      message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:25:27Z"
    - latency: 2.425663ms
      message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:24:27Z"
    - latency: 2.109403ms
      message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:23:27Z"
    - latency: 2.183308ms
      message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:22:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T19:49:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-243-to-network-check-target-ip-10-0-133-243
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-243.ec2.internal
      uid: 1e92c7ba-db7e-40da-8a43-11bc7c37f68c
    resourceVersion: "61064"
    uid: 5ed376cf-4c28-4db8-b6be-0947b8063f93
  spec:
    sourcePod: network-check-source-869dcfcdcd-nt5s6
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:56:27Z"
      message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 749.262µs
      message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:31:27Z"
    - latency: 1.347956ms
      message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:30:27Z"
    - latency: 903.78µs
      message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:29:27Z"
    - latency: 1.149001ms
      message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:28:27Z"
    - latency: 1.217574ms
      message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:27:27Z"
    - latency: 832.004µs
      message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:26:27Z"
    - latency: 1.405062ms
      message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:25:27Z"
    - latency: 1.337499ms
      message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:24:27Z"
    - latency: 1.032082ms
      message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:23:27Z"
    - latency: 1.464354ms
      message: 'network-check-target-ip-10-0-133-243: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:22:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T19:49:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-243-to-network-check-target-ip-10-0-140-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-243.ec2.internal
      uid: 1e92c7ba-db7e-40da-8a43-11bc7c37f68c
    resourceVersion: "61065"
    uid: f52f9a5b-3355-4ff6-b354-24cff5e892dc
  spec:
    sourcePod: network-check-source-869dcfcdcd-nt5s6
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:56:27Z"
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.380689ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:31:27Z"
    - latency: 2.140761ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:30:27Z"
    - latency: 2.316568ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:29:27Z"
    - latency: 2.372714ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:28:27Z"
    - latency: 2.403697ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:27:27Z"
    - latency: 2.12969ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:26:27Z"
    - latency: 2.31623ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:25:27Z"
    - latency: 2.425315ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:24:27Z"
    - latency: 2.203876ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:23:27Z"
    - latency: 2.323394ms
      message: 'network-check-target-ip-10-0-140-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:22:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T19:49:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-243-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-243.ec2.internal
      uid: 1e92c7ba-db7e-40da-8a43-11bc7c37f68c
    resourceVersion: "61067"
    uid: 371179e9-f137-4046-96f0-59543615829d
  spec:
    sourcePod: network-check-source-869dcfcdcd-nt5s6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:55:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 968.888µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:31:27Z"
    - latency: 1.687634ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:31:27Z"
    - latency: 1.224824ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:30:27Z"
    - latency: 2.154378ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:30:27Z"
    - latency: 1.104806ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:29:27Z"
    - latency: 1.757744ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:29:27Z"
    - latency: 938.631µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:28:27Z"
    - latency: 2.290215ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:28:27Z"
    - latency: 1.145743ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:27:27Z"
    - latency: 2.184007ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:27:27Z"
kind: List
metadata:
  resourceVersion: ""