apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:34:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-88-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-88.ec2.internal
      uid: 5b995920-2500-4ef6-be27-3468d89f3095
    resourceVersion: "59338"
    uid: 34a5de43-42d3-4e21-bd88-07f004334a87
  spec:
    sourcePod: network-check-source-685456655f-vh77w
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:41:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 747.232µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:09:09Z"
    - latency: 1.228807ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:08:09Z"
    - latency: 918.476µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:07:09Z"
    - latency: 1.083057ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:06:09Z"
    - latency: 924.12µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:05:09Z"
    - latency: 1.020671ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:04:09Z"
    - latency: 1.151528ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:03:09Z"
    - latency: 1.007814ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:02:09Z"
    - latency: 1.060775ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:01:09Z"
    - latency: 1.165685ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:00:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:34:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-88-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-88.ec2.internal
      uid: 5b995920-2500-4ef6-be27-3468d89f3095
    resourceVersion: "60071"
    uid: 1d6ad923-8277-4602-b4e9-e648394c7b1b
  spec:
    sourcePod: network-check-source-685456655f-vh77w
    targetEndpoint: aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:40:09Z"
      message: 'load-balancer-api-external: tcp connection to aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.347221ms
      message: 'load-balancer-api-external: tcp connection to aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:10:09Z"
    - latency: 9.163325ms
      message: 'load-balancer-api-external: resolved host name aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:10:09Z"
    - latency: 6.221982ms
      message: 'load-balancer-api-external: tcp connection to aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:09:09Z"
    - latency: 9.395627ms
      message: 'load-balancer-api-external: resolved host name aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:09:09Z"
    - latency: 5.266165ms
      message: 'load-balancer-api-external: tcp connection to aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:08:09Z"
    - latency: 9.818363ms
      message: 'load-balancer-api-external: resolved host name aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:08:09Z"
    - latency: 6.931034ms
      message: 'load-balancer-api-external: tcp connection to aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:07:09Z"
    - latency: 8.316298ms
      message: 'load-balancer-api-external: resolved host name aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:07:09Z"
    - latency: 5.436885ms
      message: 'load-balancer-api-external: tcp connection to aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:06:09Z"
    - latency: 8.383755ms
      message: 'load-balancer-api-external: resolved host name aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:06:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:34:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-88-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-88.ec2.internal
      uid: 5b995920-2500-4ef6-be27-3468d89f3095
    resourceVersion: "60070"
    uid: a6cdc584-af61-49c2-aa57-45cb34dc2cd8
  spec:
    sourcePod: network-check-source-685456655f-vh77w
    targetEndpoint: aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:40:09Z"
      message: 'load-balancer-api-internal: tcp connection to aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.318411ms
      message: 'load-balancer-api-internal: tcp connection to aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:10:09Z"
    - latency: 9.054409ms
      message: 'load-balancer-api-internal: resolved host name aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:10:09Z"
    - latency: 6.23022ms
      message: 'load-balancer-api-internal: tcp connection to aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:09:09Z"
    - latency: 9.337043ms
      message: 'load-balancer-api-internal: resolved host name aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:09:09Z"
    - latency: 6.163136ms
      message: 'load-balancer-api-internal: tcp connection to aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:08:09Z"
    - latency: 9.853162ms
      message: 'load-balancer-api-internal: resolved host name aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:08:09Z"
    - latency: 4.598573ms
      message: 'load-balancer-api-internal: tcp connection to aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:07:09Z"
    - latency: 8.289178ms
      message: 'load-balancer-api-internal: resolved host name aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:07:09Z"
    - latency: 5.517405ms
      message: 'load-balancer-api-internal: tcp connection to aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:06:09Z"
    - latency: 8.444347ms
      message: 'load-balancer-api-internal: resolved host name aa44b096a88f041328874f6972342f5e-a064be562302a21d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:06:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:34:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-88-to-network-check-target-ip-10-0-130-88
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-88.ec2.internal
      uid: 5b995920-2500-4ef6-be27-3468d89f3095
    resourceVersion: "59335"
    uid: 248eb06a-8269-4a5c-bacb-2e7bede9ce37
  spec:
    sourcePod: network-check-source-685456655f-vh77w
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:41:09Z"
      message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 961.234µs
      message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:09:09Z"
    - latency: 1.207167ms
      message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:08:09Z"
    - latency: 1.20088ms
      message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:07:09Z"
    - latency: 1.169443ms
      message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:06:09Z"
    - latency: 1.065254ms
      message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:05:09Z"
    - latency: 1.166531ms
      message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:04:09Z"
    - latency: 921.036µs
      message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:03:09Z"
    - latency: 1.081555ms
      message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:02:09Z"
    - latency: 1.355004ms
      message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:01:09Z"
    - latency: 918.186µs
      message: 'network-check-target-ip-10-0-130-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:00:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:34:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-88-to-network-check-target-ip-10-0-133-150
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-88.ec2.internal
      uid: 5b995920-2500-4ef6-be27-3468d89f3095
    resourceVersion: "59336"
    uid: 197a3b3a-3d37-4d43-812a-fa538a35dfea
  spec:
    sourcePod: network-check-source-685456655f-vh77w
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:41:09Z"
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.83618ms
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:09:09Z"
    - latency: 2.259991ms
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:08:09Z"
    - latency: 2.051387ms
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:07:09Z"
    - latency: 2.34532ms
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:06:09Z"
    - latency: 2.077483ms
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:05:09Z"
    - latency: 2.362386ms
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:04:09Z"
    - latency: 2.346796ms
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:03:09Z"
    - latency: 2.325918ms
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:02:09Z"
    - latency: 2.444118ms
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:01:09Z"
    - latency: 2.001085ms
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:00:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:34:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-88-to-network-check-target-ip-10-0-140-169
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-88.ec2.internal
      uid: 5b995920-2500-4ef6-be27-3468d89f3095
    resourceVersion: "59337"
    uid: 9caffa95-3c69-4135-9a09-cff4e68e840c
  spec:
    sourcePod: network-check-source-685456655f-vh77w
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:41:09Z"
      message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.05831ms
      message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:09:09Z"
    - latency: 2.259841ms
      message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:08:09Z"
    - latency: 1.790077ms
      message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:07:09Z"
    - latency: 2.183259ms
      message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:06:09Z"
    - latency: 2.239636ms
      message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:05:09Z"
    - latency: 2.014783ms
      message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:04:09Z"
    - latency: 2.095834ms
      message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:03:09Z"
    - latency: 2.282647ms
      message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:02:09Z"
    - latency: 2.060601ms
      message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:01:09Z"
    - latency: 1.930807ms
      message: 'network-check-target-ip-10-0-140-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:00:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T12:34:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-88-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-88.ec2.internal
      uid: 5b995920-2500-4ef6-be27-3468d89f3095
    resourceVersion: "60069"
    uid: 4b54df43-5a3e-441d-a2a5-8ce034196ceb
  spec:
    sourcePod: network-check-source-685456655f-vh77w
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T12:40:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.024178ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:10:09Z"
    - latency: 1.693506ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:10:09Z"
    - latency: 831.348µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:09:09Z"
    - latency: 1.979031ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:09:09Z"
    - latency: 1.101405ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:08:09Z"
    - latency: 1.727144ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:08:09Z"
    - latency: 917.403µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:07:09Z"
    - latency: 1.93009ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:07:09Z"
    - latency: 867.411µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:06:09Z"
    - latency: 1.831027ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:06:09Z"
kind: List
metadata:
  resourceVersion: ""