apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:11:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: b6b1e572-d143-4c5f-b54a-fa033fcab791
    resourceVersion: "62467"
    uid: 90119107-570d-4e07-bd4b-3c157e088d82
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9nf8d
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:18:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.205009ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:53:45Z"
    - latency: 1.092326ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:52:45Z"
    - latency: 913.429µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:51:45Z"
    - latency: 1.072029ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:50:45Z"
    - latency: 1.622312ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:49:45Z"
    - latency: 4.780858ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:48:45Z"
    - latency: 1.072775ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:47:45Z"
    - latency: 1.621219ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:46:45Z"
    - latency: 1.185078ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:45:45Z"
    - latency: 1.033946ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:44:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:11:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: b6b1e572-d143-4c5f-b54a-fa033fcab791
    resourceVersion: "62468"
    uid: 586657b5-ff6d-4b01-9152-94fb3cea3943
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9nf8d
    targetEndpoint: a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:17:45Z"
      message: 'load-balancer-api-external: tcp connection to a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.625524ms
      message: 'load-balancer-api-external: tcp connection to a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:53:45Z"
    - latency: 6.973041ms
      message: 'load-balancer-api-external: resolved host name a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:53:45Z"
    - latency: 5.544276ms
      message: 'load-balancer-api-external: tcp connection to a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:52:45Z"
    - latency: 7.312983ms
      message: 'load-balancer-api-external: resolved host name a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:52:45Z"
    - latency: 5.263565ms
      message: 'load-balancer-api-external: tcp connection to a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:51:45Z"
    - latency: 6.602962ms
      message: 'load-balancer-api-external: resolved host name a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:51:45Z"
    - latency: 3.505933ms
      message: 'load-balancer-api-external: tcp connection to a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:50:45Z"
    - latency: 7.242968ms
      message: 'load-balancer-api-external: resolved host name a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:50:45Z"
    - latency: 5.030361ms
      message: 'load-balancer-api-external: tcp connection to a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:49:45Z"
    - latency: 6.655402ms
      message: 'load-balancer-api-external: resolved host name a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:49:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:11:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: b6b1e572-d143-4c5f-b54a-fa033fcab791
    resourceVersion: "62469"
    uid: 44ba0c9f-4d1d-4702-9c1d-53b98feab162
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9nf8d
    targetEndpoint: a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:17:45Z"
      message: 'load-balancer-api-internal: tcp connection to a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.623129ms
      message: 'load-balancer-api-internal: tcp connection to a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:53:45Z"
    - latency: 7.017452ms
      message: 'load-balancer-api-internal: resolved host name a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:53:45Z"
    - latency: 5.155949ms
      message: 'load-balancer-api-internal: tcp connection to a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:52:45Z"
    - latency: 7.368749ms
      message: 'load-balancer-api-internal: resolved host name a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:52:45Z"
    - latency: 5.270865ms
      message: 'load-balancer-api-internal: tcp connection to a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:51:45Z"
    - latency: 6.687705ms
      message: 'load-balancer-api-internal: resolved host name a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:51:45Z"
    - latency: 3.49722ms
      message: 'load-balancer-api-internal: tcp connection to a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:50:45Z"
    - latency: 7.273083ms
      message: 'load-balancer-api-internal: resolved host name a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:50:45Z"
    - latency: 5.01648ms
      message: 'load-balancer-api-internal: tcp connection to a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:49:45Z"
    - latency: 6.692195ms
      message: 'load-balancer-api-internal: resolved host name a92ef3b968e9e4a299dc9e1bca5818d5-3f5313d665d87054.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:49:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:11:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-network-check-target-ip-10-0-131-21
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: b6b1e572-d143-4c5f-b54a-fa033fcab791
    resourceVersion: "62463"
    uid: 32eb08af-6671-41c1-b397-98111be089af
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9nf8d
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:18:45Z"
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.128µs
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:53:45Z"
    - latency: 1.618342ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:52:45Z"
    - latency: 1.099764ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:51:45Z"
    - latency: 1.327029ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:50:45Z"
    - latency: 1.01656ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:49:45Z"
    - latency: 4.772276ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:48:45Z"
    - latency: 1.051589ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:47:45Z"
    - latency: 1.837304ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:46:45Z"
    - latency: 822.226µs
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:45:45Z"
    - latency: 902.09µs
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:44:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:11:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-network-check-target-ip-10-0-142-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: b6b1e572-d143-4c5f-b54a-fa033fcab791
    resourceVersion: "62466"
    uid: 969fdeb5-1d78-4318-b923-a04b7e58705e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9nf8d
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:18:45Z"
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.428138ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:53:45Z"
    - latency: 3.001629ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:52:45Z"
    - latency: 2.246783ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:51:45Z"
    - latency: 2.141314ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:50:45Z"
    - latency: 3.005341ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:49:45Z"
    - latency: 2.803038ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:48:45Z"
    - latency: 2.419709ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:47:45Z"
    - latency: 2.80502ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:46:45Z"
    - latency: 2.216181ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:45:45Z"
    - latency: 2.296842ms
      message: 'network-check-target-ip-10-0-142-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:44:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:11:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-network-check-target-ip-10-0-143-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: b6b1e572-d143-4c5f-b54a-fa033fcab791
    resourceVersion: "62465"
    uid: 8208eb03-6e5d-42e7-868c-ba7240934275
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9nf8d
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:18:45Z"
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.565764ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:53:45Z"
    - latency: 2.546602ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:52:45Z"
    - latency: 2.095685ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:51:45Z"
    - latency: 2.414907ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:50:45Z"
    - latency: 2.64806ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:49:45Z"
    - latency: 4.055808ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:48:45Z"
    - latency: 2.327003ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:47:45Z"
    - latency: 2.724477ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:46:45Z"
    - latency: 2.221134ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:45:45Z"
    - latency: 2.366322ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:44:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T16:11:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: b6b1e572-d143-4c5f-b54a-fa033fcab791
    resourceVersion: "62464"
    uid: b10b6280-08e9-41da-bcd6-b00a1d1d64f7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-9nf8d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T16:17:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.052012ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:53:45Z"
    - latency: 1.93868ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:53:45Z"
    - latency: 1.263823ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:52:45Z"
    - latency: 1.586993ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:52:45Z"
    - latency: 840.846µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:51:45Z"
    - latency: 2.102406ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:51:45Z"
    - latency: 828.156µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:50:45Z"
    - latency: 1.71211ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:50:45Z"
    - latency: 793.275µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T16:49:45Z"
    - latency: 1.967154ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T16:49:45Z"
kind: List
metadata:
  resourceVersion: ""