apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:31:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-133-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-133.ec2.internal
      uid: 2b378007-6566-48a2-bc74-26f7174ba0b6
    resourceVersion: "27071"
    uid: df04e0f3-f10d-480c-881b-fd35efd31530
  spec:
    sourcePod: network-check-source-6f78d59f99-xqg74
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:38:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.265314ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:20:18Z"
    - latency: 894.109µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:19:18Z"
    - latency: 836.297µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:18:18Z"
    - latency: 779.186µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:17:18Z"
    - latency: 1.399698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:16:18Z"
    - latency: 974.14µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:15:18Z"
    - latency: 988.886µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:14:18Z"
    - latency: 1.022671ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:13:18Z"
    - latency: 914.094µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:12:18Z"
    - latency: 1.216513ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:11:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:31:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-133-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-133.ec2.internal
      uid: 2b378007-6566-48a2-bc74-26f7174ba0b6
    resourceVersion: "26236"
    uid: b2ec0031-e075-4e38-a228-06319d67be59
  spec:
    sourcePod: network-check-source-6f78d59f99-xqg74
    targetEndpoint: a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:37:19Z"
      message: 'load-balancer-api-external: tcp connection to a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.247823ms
      message: 'load-balancer-api-external: tcp connection to a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:19:19Z"
    - latency: 10.737188ms
      message: 'load-balancer-api-external: resolved host name a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:19:18Z"
    - latency: 18.063314ms
      message: 'load-balancer-api-external: tcp connection to a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:18:18Z"
    - latency: 8.513427ms
      message: 'load-balancer-api-external: resolved host name a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:18:18Z"
    - latency: 17.50445ms
      message: 'load-balancer-api-external: tcp connection to a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:17:18Z"
    - latency: 9.309039ms
      message: 'load-balancer-api-external: resolved host name a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:17:18Z"
    - latency: 17.325512ms
      message: 'load-balancer-api-external: tcp connection to a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:16:18Z"
    - latency: 8.222244ms
      message: 'load-balancer-api-external: resolved host name a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:16:18Z"
    - latency: 16.642296ms
      message: 'load-balancer-api-external: tcp connection to a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:15:18Z"
    - latency: 8.107081ms
      message: 'load-balancer-api-external: resolved host name a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:15:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:31:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-133-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-133.ec2.internal
      uid: 2b378007-6566-48a2-bc74-26f7174ba0b6
    resourceVersion: "26235"
    uid: 1b0d2ac4-6c93-4504-aa9f-131b7329824a
  spec:
    sourcePod: network-check-source-6f78d59f99-xqg74
    targetEndpoint: a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:37:19Z"
      message: 'load-balancer-api-internal: tcp connection to a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 14.538034ms
      message: 'load-balancer-api-internal: tcp connection to a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:19:19Z"
    - latency: 10.707913ms
      message: 'load-balancer-api-internal: resolved host name a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:19:18Z"
    - latency: 16.868435ms
      message: 'load-balancer-api-internal: tcp connection to a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:18:18Z"
    - latency: 8.486611ms
      message: 'load-balancer-api-internal: resolved host name a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:18:18Z"
    - latency: 17.525249ms
      message: 'load-balancer-api-internal: tcp connection to a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:17:18Z"
    - latency: 9.276146ms
      message: 'load-balancer-api-internal: resolved host name a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:17:18Z"
    - latency: 18.474699ms
      message: 'load-balancer-api-internal: tcp connection to a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:16:18Z"
    - latency: 8.197459ms
      message: 'load-balancer-api-internal: resolved host name a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:16:18Z"
    - latency: 20.03842ms
      message: 'load-balancer-api-internal: tcp connection to a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:15:18Z"
    - latency: 8.066599ms
      message: 'load-balancer-api-internal: resolved host name a0a495eba661044ef948a13d3b2ebfab-e396401b2503e6f8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:15:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:31:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-133-to-network-check-target-ip-10-0-131-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-133.ec2.internal
      uid: 2b378007-6566-48a2-bc74-26f7174ba0b6
    resourceVersion: "27068"
    uid: c6cccbc4-0d27-4dba-9352-af82eab25abd
  spec:
    sourcePod: network-check-source-6f78d59f99-xqg74
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:38:18Z"
      message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.035508ms
      message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:20:18Z"
    - latency: 958.78µs
      message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:19:18Z"
    - latency: 942.208µs
      message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:18:18Z"
    - latency: 1.630199ms
      message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:17:18Z"
    - latency: 781.05µs
      message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:16:18Z"
    - latency: 964.497µs
      message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:15:18Z"
    - latency: 1.657675ms
      message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:14:18Z"
    - latency: 854.412µs
      message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:13:18Z"
    - latency: 1.616379ms
      message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:12:18Z"
    - latency: 938.997µs
      message: 'network-check-target-ip-10-0-131-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:11:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:31:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-133-to-network-check-target-ip-10-0-131-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-133.ec2.internal
      uid: 2b378007-6566-48a2-bc74-26f7174ba0b6
    resourceVersion: "27069"
    uid: 90869b28-4c94-465a-b2f0-f96be7884680
  spec:
    sourcePod: network-check-source-6f78d59f99-xqg74
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:38:18Z"
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.459204ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:20:18Z"
    - latency: 2.301212ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:19:18Z"
    - latency: 2.617949ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:18:18Z"
    - latency: 2.259195ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:17:18Z"
    - latency: 2.397865ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:16:18Z"
    - latency: 2.626976ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:15:18Z"
    - latency: 2.325168ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:14:18Z"
    - latency: 2.303583ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:13:18Z"
    - latency: 2.441111ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:12:18Z"
    - latency: 2.119615ms
      message: 'network-check-target-ip-10-0-131-90: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:11:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:31:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-133-to-network-check-target-ip-10-0-139-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-133.ec2.internal
      uid: 2b378007-6566-48a2-bc74-26f7174ba0b6
    resourceVersion: "27070"
    uid: 04e2f7e3-e3d9-490f-aa24-5354ea67f0af
  spec:
    sourcePod: network-check-source-6f78d59f99-xqg74
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:38:18Z"
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.633496ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:20:18Z"
    - latency: 2.422037ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:19:18Z"
    - latency: 2.014879ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:18:18Z"
    - latency: 2.580962ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:17:18Z"
    - latency: 2.3987ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:16:18Z"
    - latency: 2.173341ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:15:18Z"
    - latency: 2.493933ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:14:18Z"
    - latency: 2.471401ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:13:18Z"
    - latency: 2.670685ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:12:18Z"
    - latency: 2.504834ms
      message: 'network-check-target-ip-10-0-139-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:11:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:31:17Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-133-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-133.ec2.internal
      uid: 2b378007-6566-48a2-bc74-26f7174ba0b6
    resourceVersion: "26234"
    uid: 558b9b8f-a350-45a3-91dd-ef9d751f0edc
  spec:
    sourcePod: network-check-source-6f78d59f99-xqg74
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:37:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.092865ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:19:18Z"
    - latency: 1.797745ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:19:18Z"
    - latency: 1.044494ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:18:18Z"
    - latency: 1.573718ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:18:18Z"
    - latency: 955.85µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:17:18Z"
    - latency: 2.303035ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:17:18Z"
    - latency: 853.709µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:16:18Z"
    - latency: 2.164785ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:16:18Z"
    - latency: 1.033315ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:15:18Z"
    - latency: 1.955408ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:15:18Z"
kind: List
metadata:
  resourceVersion: ""