apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:29:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-145-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-145.ec2.internal
      uid: bcc537a3-61af-46d8-b73e-e84193358996
    resourceVersion: "63759"
    uid: 12790d73-8d04-4179-8b7f-0d5db7b0ec29
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5lcl4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:36:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.407µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:11:30Z"
    - latency: 1.64166ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:10:30Z"
    - latency: 1.023535ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:09:30Z"
    - latency: 1.222817ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:08:30Z"
    - latency: 916.557µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:07:30Z"
    - latency: 1.180032ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:06:30Z"
    - latency: 1.174694ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:05:30Z"
    - latency: 844.837µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:04:30Z"
    - latency: 1.313354ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:03:30Z"
    - latency: 1.397962ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:02:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:29:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-145-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-145.ec2.internal
      uid: bcc537a3-61af-46d8-b73e-e84193358996
    resourceVersion: "63761"
    uid: f5370161-df4e-4864-8c58-84dd44e027a1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5lcl4
    targetEndpoint: a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:35:30Z"
      message: 'load-balancer-api-external: tcp connection to a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.225565ms
      message: 'load-balancer-api-external: tcp connection to a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:11:30Z"
    - latency: 7.657528ms
      message: 'load-balancer-api-external: resolved host name a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:11:30Z"
    - latency: 4.072197ms
      message: 'load-balancer-api-external: tcp connection to a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:10:30Z"
    - latency: 10.301394ms
      message: 'load-balancer-api-external: resolved host name a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:10:30Z"
    - latency: 3.98967ms
      message: 'load-balancer-api-external: tcp connection to a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:09:30Z"
    - latency: 8.599419ms
      message: 'load-balancer-api-external: resolved host name a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:09:30Z"
    - latency: 3.167356ms
      message: 'load-balancer-api-external: tcp connection to a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:08:30Z"
    - latency: 7.714346ms
      message: 'load-balancer-api-external: resolved host name a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:08:30Z"
    - latency: 3.812142ms
      message: 'load-balancer-api-external: tcp connection to a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:07:30Z"
    - latency: 8.579133ms
      message: 'load-balancer-api-external: resolved host name a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:07:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:29:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-145-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-145.ec2.internal
      uid: bcc537a3-61af-46d8-b73e-e84193358996
    resourceVersion: "63762"
    uid: fc741476-bb3e-4d42-a2a1-340c5308fac6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5lcl4
    targetEndpoint: a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:35:30Z"
      message: 'load-balancer-api-internal: tcp connection to a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.955214ms
      message: 'load-balancer-api-internal: tcp connection to a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:11:30Z"
    - latency: 7.628756ms
      message: 'load-balancer-api-internal: resolved host name a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:11:30Z"
    - latency: 4.428747ms
      message: 'load-balancer-api-internal: tcp connection to a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:10:30Z"
    - latency: 10.282185ms
      message: 'load-balancer-api-internal: resolved host name a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:10:30Z"
    - latency: 4.419399ms
      message: 'load-balancer-api-internal: tcp connection to a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:09:30Z"
    - latency: 8.56246ms
      message: 'load-balancer-api-internal: resolved host name a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:09:30Z"
    - latency: 3.850465ms
      message: 'load-balancer-api-internal: tcp connection to a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:08:30Z"
    - latency: 7.683999ms
      message: 'load-balancer-api-internal: resolved host name a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:08:30Z"
    - latency: 3.80837ms
      message: 'load-balancer-api-internal: tcp connection to a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:07:30Z"
    - latency: 8.557793ms
      message: 'load-balancer-api-internal: resolved host name a5d31421724e94227bfc0b9cff33d391-79dd6d405bc2f82e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:07:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:29:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-145-to-network-check-target-ip-10-0-130-19
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-145.ec2.internal
      uid: bcc537a3-61af-46d8-b73e-e84193358996
    resourceVersion: "63756"
    uid: b64980e0-8a29-4b96-bd7f-b49e9e9292b9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5lcl4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:36:30Z"
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.668069ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:11:30Z"
    - latency: 1.688955ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:10:30Z"
    - latency: 2.060964ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:09:30Z"
    - latency: 2.119283ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:08:30Z"
    - latency: 2.509854ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:07:30Z"
    - latency: 2.094431ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:06:30Z"
    - latency: 1.560588ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:05:30Z"
    - latency: 1.660589ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:04:30Z"
    - latency: 1.922841ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:03:30Z"
    - latency: 2.10329ms
      message: 'network-check-target-ip-10-0-130-19: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:02:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:29:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-145-to-network-check-target-ip-10-0-139-145
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-145.ec2.internal
      uid: bcc537a3-61af-46d8-b73e-e84193358996
    resourceVersion: "63757"
    uid: 190a79f7-c1fa-4cbb-8f49-531dfc2f30a6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5lcl4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:36:30Z"
      message: 'network-check-target-ip-10-0-139-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 799.72µs
      message: 'network-check-target-ip-10-0-139-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:11:30Z"
    - latency: 897.26µs
      message: 'network-check-target-ip-10-0-139-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:10:30Z"
    - latency: 949.128µs
      message: 'network-check-target-ip-10-0-139-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:09:30Z"
    - latency: 884.963µs
      message: 'network-check-target-ip-10-0-139-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:08:30Z"
    - latency: 901.361µs
      message: 'network-check-target-ip-10-0-139-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:07:30Z"
    - latency: 968.339µs
      message: 'network-check-target-ip-10-0-139-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:06:30Z"
    - latency: 808.528µs
      message: 'network-check-target-ip-10-0-139-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:05:30Z"
    - latency: 1.329656ms
      message: 'network-check-target-ip-10-0-139-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:04:30Z"
    - latency: 2.062357ms
      message: 'network-check-target-ip-10-0-139-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:03:30Z"
    - latency: 1.512531ms
      message: 'network-check-target-ip-10-0-139-145: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:02:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:29:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-145-to-network-check-target-ip-10-0-141-150
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-145.ec2.internal
      uid: bcc537a3-61af-46d8-b73e-e84193358996
    resourceVersion: "63760"
    uid: d2a959c0-5ef8-4cb4-96d2-223f54e7ccb0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5lcl4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:36:30Z"
      message: 'network-check-target-ip-10-0-141-150: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.955347ms
      message: 'network-check-target-ip-10-0-141-150: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:11:30Z"
    - latency: 2.08345ms
      message: 'network-check-target-ip-10-0-141-150: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:10:30Z"
    - latency: 2.373867ms
      message: 'network-check-target-ip-10-0-141-150: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:09:30Z"
    - latency: 1.979358ms
      message: 'network-check-target-ip-10-0-141-150: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:08:30Z"
    - latency: 2.931803ms
      message: 'network-check-target-ip-10-0-141-150: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:07:30Z"
    - latency: 1.985169ms
      message: 'network-check-target-ip-10-0-141-150: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:06:30Z"
    - latency: 2.230387ms
      message: 'network-check-target-ip-10-0-141-150: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:05:30Z"
    - latency: 2.165369ms
      message: 'network-check-target-ip-10-0-141-150: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:04:30Z"
    - latency: 2.275237ms
      message: 'network-check-target-ip-10-0-141-150: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:03:30Z"
    - latency: 2.175151ms
      message: 'network-check-target-ip-10-0-141-150: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:02:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T15:29:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-145-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-145.ec2.internal
      uid: bcc537a3-61af-46d8-b73e-e84193358996
    resourceVersion: "63758"
    uid: d8773b0b-ae28-4589-a403-4a88e0526fb1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-5lcl4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T15:35:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 983.105µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:11:30Z"
    - latency: 1.625427ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:11:30Z"
    - latency: 900.518µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:10:30Z"
    - latency: 1.996662ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:10:30Z"
    - latency: 927.017µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:09:30Z"
    - latency: 1.813851ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:09:30Z"
    - latency: 872.869µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:08:30Z"
    - latency: 1.829947ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:08:30Z"
    - latency: 1.434047ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T16:07:30Z"
    - latency: 2.615742ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T16:07:30Z"
kind: List
metadata:
  resourceVersion: ""