apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T23:59:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-246-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-246.ec2.internal
      uid: c2011cb2-d24a-437d-bb99-c837e79d59eb
    resourceVersion: "54801"
    uid: d313791f-aa4b-4864-9132-ea72e3113512
  spec:
    sourcePod: network-check-source-989f8b8dc-qztzd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T00:06:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 972.84µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:34:06Z"
    - latency: 1.158916ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:33:06Z"
    - latency: 1.057997ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:32:06Z"
    - latency: 1.206102ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:31:06Z"
    - latency: 1.276782ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:30:06Z"
    - latency: 899.499µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:29:06Z"
    - latency: 951.796µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:28:06Z"
    - latency: 2.12944ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:27:06Z"
    - latency: 1.395452ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:26:06Z"
    - latency: 1.341123ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:25:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T23:59:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-246-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-246.ec2.internal
      uid: c2011cb2-d24a-437d-bb99-c837e79d59eb
    resourceVersion: "55883"
    uid: b14fea81-7f1c-4098-87d7-9fb6d16b411a
  spec:
    sourcePod: network-check-source-989f8b8dc-qztzd
    targetEndpoint: ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T00:05:06Z"
      message: 'load-balancer-api-external: tcp connection to ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.099813ms
      message: 'load-balancer-api-external: tcp connection to ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:35:06Z"
    - latency: 8.864563ms
      message: 'load-balancer-api-external: resolved host name ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:35:06Z"
    - latency: 4.513645ms
      message: 'load-balancer-api-external: tcp connection to ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:34:06Z"
    - latency: 10.355247ms
      message: 'load-balancer-api-external: resolved host name ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:34:06Z"
    - latency: 4.253956ms
      message: 'load-balancer-api-external: tcp connection to ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:33:06Z"
    - latency: 9.544826ms
      message: 'load-balancer-api-external: resolved host name ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:33:06Z"
    - latency: 5.138518ms
      message: 'load-balancer-api-external: tcp connection to ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:32:06Z"
    - latency: 10.154924ms
      message: 'load-balancer-api-external: resolved host name ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:32:06Z"
    - latency: 5.151122ms
      message: 'load-balancer-api-external: tcp connection to ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:31:06Z"
    - latency: 8.870528ms
      message: 'load-balancer-api-external: resolved host name ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:31:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T23:59:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-246-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-246.ec2.internal
      uid: c2011cb2-d24a-437d-bb99-c837e79d59eb
    resourceVersion: "55882"
    uid: db7164b0-a4e8-4844-8b5e-9361d715d93e
  spec:
    sourcePod: network-check-source-989f8b8dc-qztzd
    targetEndpoint: ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T00:05:06Z"
      message: 'load-balancer-api-internal: tcp connection to ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.08897ms
      message: 'load-balancer-api-internal: tcp connection to ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:35:06Z"
    - latency: 8.8191ms
      message: 'load-balancer-api-internal: resolved host name ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:35:06Z"
    - latency: 3.805518ms
      message: 'load-balancer-api-internal: tcp connection to ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:34:06Z"
    - latency: 10.410308ms
      message: 'load-balancer-api-internal: resolved host name ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:34:06Z"
    - latency: 4.360716ms
      message: 'load-balancer-api-internal: tcp connection to ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:33:06Z"
    - latency: 9.466086ms
      message: 'load-balancer-api-internal: resolved host name ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:33:06Z"
    - latency: 5.15739ms
      message: 'load-balancer-api-internal: tcp connection to ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:32:06Z"
    - latency: 9.9905ms
      message: 'load-balancer-api-internal: resolved host name ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:32:06Z"
    - latency: 5.119785ms
      message: 'load-balancer-api-internal: tcp connection to ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:31:06Z"
    - latency: 8.91339ms
      message: 'load-balancer-api-internal: resolved host name ac3cdbfee3b1f4be6b50c6b3c90faa7e-dbee430001a28b36.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:31:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T23:59:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-246-to-network-check-target-ip-10-0-131-246
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-246.ec2.internal
      uid: c2011cb2-d24a-437d-bb99-c837e79d59eb
    resourceVersion: "54798"
    uid: 3051f3fe-f61c-49ee-98c4-5487133b6a2c
  spec:
    sourcePod: network-check-source-989f8b8dc-qztzd
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T00:06:06Z"
      message: 'network-check-target-ip-10-0-131-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.17392ms
      message: 'network-check-target-ip-10-0-131-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:34:06Z"
    - latency: 1.46146ms
      message: 'network-check-target-ip-10-0-131-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:33:06Z"
    - latency: 859.109µs
      message: 'network-check-target-ip-10-0-131-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:32:06Z"
    - latency: 810.77µs
      message: 'network-check-target-ip-10-0-131-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:31:06Z"
    - latency: 863.425µs
      message: 'network-check-target-ip-10-0-131-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:30:06Z"
    - latency: 963.705µs
      message: 'network-check-target-ip-10-0-131-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:29:06Z"
    - latency: 1.209704ms
      message: 'network-check-target-ip-10-0-131-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:28:06Z"
    - latency: 792.017µs
      message: 'network-check-target-ip-10-0-131-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:27:06Z"
    - latency: 825.441µs
      message: 'network-check-target-ip-10-0-131-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:26:06Z"
    - latency: 1.284034ms
      message: 'network-check-target-ip-10-0-131-246: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:25:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T23:59:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-246-to-network-check-target-ip-10-0-141-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-246.ec2.internal
      uid: c2011cb2-d24a-437d-bb99-c837e79d59eb
    resourceVersion: "54800"
    uid: 53b8ec71-a0b6-4895-bc2d-a0f7c6b5259d
  spec:
    sourcePod: network-check-source-989f8b8dc-qztzd
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T00:06:06Z"
      message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.952988ms
      message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:34:06Z"
    - latency: 2.455022ms
      message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:33:06Z"
    - latency: 2.146834ms
      message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:32:06Z"
    - latency: 2.107861ms
      message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:31:06Z"
    - latency: 2.038992ms
      message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:30:06Z"
    - latency: 2.123585ms
      message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:29:06Z"
    - latency: 2.518359ms
      message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:28:06Z"
    - latency: 3.104766ms
      message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:27:06Z"
    - latency: 2.683944ms
      message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:26:06Z"
    - latency: 2.266955ms
      message: 'network-check-target-ip-10-0-141-102: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:25:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T23:59:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-246-to-network-check-target-ip-10-0-141-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-246.ec2.internal
      uid: c2011cb2-d24a-437d-bb99-c837e79d59eb
    resourceVersion: "54799"
    uid: d6235f1f-79e6-41ea-a735-be3ea1372f81
  spec:
    sourcePod: network-check-source-989f8b8dc-qztzd
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T00:06:06Z"
      message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.959941ms
      message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:34:06Z"
    - latency: 2.098544ms
      message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:33:06Z"
    - latency: 1.871355ms
      message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:32:06Z"
    - latency: 2.179045ms
      message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:31:06Z"
    - latency: 2.190853ms
      message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:30:06Z"
    - latency: 1.931968ms
      message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:29:06Z"
    - latency: 2.063056ms
      message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:28:06Z"
    - latency: 2.140216ms
      message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:27:06Z"
    - latency: 1.773962ms
      message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:26:06Z"
    - latency: 2.013914ms
      message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:25:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T23:59:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-246-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-246.ec2.internal
      uid: c2011cb2-d24a-437d-bb99-c837e79d59eb
    resourceVersion: "55881"
    uid: 4ba39579-ae0c-48a0-880f-b50aa7023b07
  spec:
    sourcePod: network-check-source-989f8b8dc-qztzd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T00:05:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 887.402µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:35:06Z"
    - latency: 1.687006ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:35:06Z"
    - latency: 712.748µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:34:06Z"
    - latency: 2.035681ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:34:06Z"
    - latency: 917.207µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:33:06Z"
    - latency: 2.138658ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:33:06Z"
    - latency: 919.746µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:32:06Z"
    - latency: 1.800203ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:32:06Z"
    - latency: 842.436µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:31:06Z"
    - latency: 1.729073ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:31:06Z"
kind: List
metadata:
  resourceVersion: ""