apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:17:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-116-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-116.ec2.internal
      uid: 2a094a37-76b1-4269-85bf-a2c78d70513a
    resourceVersion: "21339"
    uid: 6653ad56-793e-4aa9-98ca-ec576477e5c7
  spec:
    sourcePod: network-check-source-56499946bc-xxqp4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:24:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.043537ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:38:23Z"
    - latency: 1.285478ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:37:23Z"
    - latency: 1.079826ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:36:23Z"
    - latency: 1.113624ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:35:23Z"
    - latency: 1.556891ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:34:23Z"
    - latency: 996.12µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:33:23Z"
    - latency: 916.187µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:32:23Z"
    - latency: 1.112751ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:31:23Z"
    - latency: 1.018724ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:30:23Z"
    - latency: 1.010359ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:29:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:17:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-116-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-116.ec2.internal
      uid: 2a094a37-76b1-4269-85bf-a2c78d70513a
    resourceVersion: "19935"
    uid: e31466ca-a662-4cbd-aa2f-c43f26dac363
  spec:
    sourcePod: network-check-source-56499946bc-xxqp4
    targetEndpoint: a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:23:23Z"
      message: 'load-balancer-api-external: tcp connection to a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.283245ms
      message: 'load-balancer-api-external: tcp connection to a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:35:23Z"
    - latency: 8.662225ms
      message: 'load-balancer-api-external: resolved host name a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:35:23Z"
    - latency: 5.944162ms
      message: 'load-balancer-api-external: tcp connection to a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:34:23Z"
    - latency: 8.45619ms
      message: 'load-balancer-api-external: resolved host name a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:34:23Z"
    - latency: 4.859989ms
      message: 'load-balancer-api-external: tcp connection to a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:33:23Z"
    - latency: 9.478631ms
      message: 'load-balancer-api-external: resolved host name a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:33:23Z"
    - latency: 6.081687ms
      message: 'load-balancer-api-external: tcp connection to a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:32:23Z"
    - latency: 8.992316ms
      message: 'load-balancer-api-external: resolved host name a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:32:23Z"
    - latency: 6.249283ms
      message: 'load-balancer-api-external: tcp connection to a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:31:23Z"
    - latency: 8.522553ms
      message: 'load-balancer-api-external: resolved host name a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:31:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:17:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-116-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-116.ec2.internal
      uid: 2a094a37-76b1-4269-85bf-a2c78d70513a
    resourceVersion: "19936"
    uid: e11535d6-df34-4ea8-b1bc-965aa5bad599
  spec:
    sourcePod: network-check-source-56499946bc-xxqp4
    targetEndpoint: a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:23:23Z"
      message: 'load-balancer-api-internal: tcp connection to a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.239685ms
      message: 'load-balancer-api-internal: tcp connection to a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:35:23Z"
    - latency: 8.570108ms
      message: 'load-balancer-api-internal: resolved host name a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:35:23Z"
    - latency: 5.922401ms
      message: 'load-balancer-api-internal: tcp connection to a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:34:23Z"
    - latency: 8.548009ms
      message: 'load-balancer-api-internal: resolved host name a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:34:23Z"
    - latency: 4.330946ms
      message: 'load-balancer-api-internal: tcp connection to a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:33:23Z"
    - latency: 9.51347ms
      message: 'load-balancer-api-internal: resolved host name a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:33:23Z"
    - latency: 6.06937ms
      message: 'load-balancer-api-internal: tcp connection to a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:32:23Z"
    - latency: 9.072012ms
      message: 'load-balancer-api-internal: resolved host name a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:32:23Z"
    - latency: 6.212813ms
      message: 'load-balancer-api-internal: tcp connection to a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:31:23Z"
    - latency: 8.460397ms
      message: 'load-balancer-api-internal: resolved host name a51bcb6354156431cbe12ffb5872d8b0-3487de5cbe3c26c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:31:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:17:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-116-to-network-check-target-ip-10-0-128-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-116.ec2.internal
      uid: 2a094a37-76b1-4269-85bf-a2c78d70513a
    resourceVersion: "21336"
    uid: cbdda2d6-87b2-42dc-a084-0bafd8054a4b
  spec:
    sourcePod: network-check-source-56499946bc-xxqp4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:24:23Z"
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.085953ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:38:23Z"
    - latency: 2.24147ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:37:23Z"
    - latency: 2.491027ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:36:23Z"
    - latency: 2.08953ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:35:23Z"
    - latency: 2.327085ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:34:23Z"
    - latency: 2.206295ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:33:23Z"
    - latency: 2.138548ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:32:23Z"
    - latency: 1.998841ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:31:23Z"
    - latency: 2.337146ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:30:23Z"
    - latency: 2.694708ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:29:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:17:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-116-to-network-check-target-ip-10-0-131-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-116.ec2.internal
      uid: 2a094a37-76b1-4269-85bf-a2c78d70513a
    resourceVersion: "21338"
    uid: e5fb4d6a-826e-4fc1-b4b6-734783963fa6
  spec:
    sourcePod: network-check-source-56499946bc-xxqp4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:24:23Z"
      message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.005178ms
      message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:38:23Z"
    - latency: 1.02081ms
      message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:37:23Z"
    - latency: 1.041534ms
      message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:36:23Z"
    - latency: 854.099µs
      message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:35:23Z"
    - latency: 1.830779ms
      message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:34:23Z"
    - latency: 971.732µs
      message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:33:23Z"
    - latency: 951.981µs
      message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:32:23Z"
    - latency: 1.120049ms
      message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:31:23Z"
    - latency: 1.068573ms
      message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:30:23Z"
    - latency: 997.609µs
      message: 'network-check-target-ip-10-0-131-116: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:29:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:17:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-116-to-network-check-target-ip-10-0-141-149
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-116.ec2.internal
      uid: 2a094a37-76b1-4269-85bf-a2c78d70513a
    resourceVersion: "21337"
    uid: 14a94abb-dcd2-4e3f-baae-c016ca6506c9
  spec:
    sourcePod: network-check-source-56499946bc-xxqp4
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:24:23Z"
      message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.133434ms
      message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:38:23Z"
    - latency: 2.225912ms
      message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:37:23Z"
    - latency: 2.582391ms
      message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:36:23Z"
    - latency: 2.122998ms
      message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:35:23Z"
    - latency: 2.583169ms
      message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:34:23Z"
    - latency: 2.136601ms
      message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:33:23Z"
    - latency: 2.535631ms
      message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:32:23Z"
    - latency: 2.424051ms
      message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:31:23Z"
    - latency: 2.407408ms
      message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:30:23Z"
    - latency: 2.272504ms
      message: 'network-check-target-ip-10-0-141-149: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:29:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T13:17:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-116-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-116.ec2.internal
      uid: 2a094a37-76b1-4269-85bf-a2c78d70513a
    resourceVersion: "19934"
    uid: e3de1a3a-2670-47e8-aadb-22a373272636
  spec:
    sourcePod: network-check-source-56499946bc-xxqp4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T13:23:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 907.802µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:35:23Z"
    - latency: 1.798171ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:35:23Z"
    - latency: 977.757µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:34:23Z"
    - latency: 1.863592ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:34:23Z"
    - latency: 847.8µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:33:23Z"
    - latency: 2.033551ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:33:23Z"
    - latency: 1.284477ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:32:23Z"
    - latency: 1.766681ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:32:23Z"
    - latency: 919.685µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T13:31:23Z"
    - latency: 2.109101ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T13:31:23Z"
kind: List
metadata:
  resourceVersion: ""