apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T06:31:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-165-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-165.ec2.internal
      uid: 92b8805b-ef07-40c2-ad4d-f4dd4a73d6a7
    resourceVersion: "30225"
    uid: 53397968-f293-498d-b9fe-769fc0000c17
  spec:
    sourcePod: network-check-source-6947749cfc-7vcfx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T06:38:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.243956ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:45:30Z"
    - latency: 1.601101ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:44:30Z"
    - latency: 908.31µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:43:30Z"
    - latency: 993.834µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:42:30Z"
    - latency: 1.002592ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:41:30Z"
    - latency: 1.245242ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:40:30Z"
    - latency: 1.46224ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:39:30Z"
    - latency: 1.022103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:38:30Z"
    - latency: 832.853µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:37:30Z"
    - latency: 1.281269ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:36:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T06:31:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-165-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-165.ec2.internal
      uid: 92b8805b-ef07-40c2-ad4d-f4dd4a73d6a7
    resourceVersion: "28968"
    uid: 89456239-ec01-457e-8190-c0f593e00e3d
  spec:
    sourcePod: network-check-source-6947749cfc-7vcfx
    targetEndpoint: a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T06:37:30Z"
      message: 'load-balancer-api-external: tcp connection to a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.308173ms
      message: 'load-balancer-api-external: tcp connection to a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:43:30Z"
    - latency: 8.504379ms
      message: 'load-balancer-api-external: resolved host name a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T06:43:30Z"
    - latency: 4.921637ms
      message: 'load-balancer-api-external: tcp connection to a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:42:30Z"
    - latency: 8.303381ms
      message: 'load-balancer-api-external: resolved host name a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T06:42:30Z"
    - latency: 4.92889ms
      message: 'load-balancer-api-external: tcp connection to a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:41:30Z"
    - latency: 9.547837ms
      message: 'load-balancer-api-external: resolved host name a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T06:41:30Z"
    - latency: 4.827044ms
      message: 'load-balancer-api-external: tcp connection to a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:40:30Z"
    - latency: 9.534049ms
      message: 'load-balancer-api-external: resolved host name a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T06:40:30Z"
    - latency: 4.252775ms
      message: 'load-balancer-api-external: tcp connection to a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:39:30Z"
    - latency: 8.82749ms
      message: 'load-balancer-api-external: resolved host name a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T06:39:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T06:31:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-165-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-165.ec2.internal
      uid: 92b8805b-ef07-40c2-ad4d-f4dd4a73d6a7
    resourceVersion: "28969"
    uid: 1215eecd-72d6-4d31-bda8-91ec3aa680dd
  spec:
    sourcePod: network-check-source-6947749cfc-7vcfx
    targetEndpoint: a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T06:37:30Z"
      message: 'load-balancer-api-internal: tcp connection to a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.345979ms
      message: 'load-balancer-api-internal: tcp connection to a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:43:30Z"
    - latency: 8.576766ms
      message: 'load-balancer-api-internal: resolved host name a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T06:43:30Z"
    - latency: 4.936746ms
      message: 'load-balancer-api-internal: tcp connection to a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:42:30Z"
    - latency: 8.246068ms
      message: 'load-balancer-api-internal: resolved host name a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T06:42:30Z"
    - latency: 4.713671ms
      message: 'load-balancer-api-internal: tcp connection to a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:41:30Z"
    - latency: 9.504107ms
      message: 'load-balancer-api-internal: resolved host name a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T06:41:30Z"
    - latency: 5.015125ms
      message: 'load-balancer-api-internal: tcp connection to a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:40:30Z"
    - latency: 9.463693ms
      message: 'load-balancer-api-internal: resolved host name a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T06:40:30Z"
    - latency: 4.258029ms
      message: 'load-balancer-api-internal: tcp connection to a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:39:30Z"
    - latency: 8.819342ms
      message: 'load-balancer-api-internal: resolved host name a2515b6b4a1814479a4a7cf4bc6d5cea-c78831cfbe164fb4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T06:39:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T06:31:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-165-to-network-check-target-ip-10-0-133-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-165.ec2.internal
      uid: 92b8805b-ef07-40c2-ad4d-f4dd4a73d6a7
    resourceVersion: "30224"
    uid: 71cf63d5-7bba-4afc-84c2-b53947b18477
  spec:
    sourcePod: network-check-source-6947749cfc-7vcfx
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T06:38:30Z"
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.250695ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:45:30Z"
    - latency: 2.102885ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:44:30Z"
    - latency: 2.046929ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:43:30Z"
    - latency: 2.167735ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:42:30Z"
    - latency: 2.077399ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:41:30Z"
    - latency: 2.165426ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:40:30Z"
    - latency: 2.211341ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:39:30Z"
    - latency: 2.26787ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:38:30Z"
    - latency: 1.84945ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:37:30Z"
    - latency: 2.182439ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:36:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T06:31:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-165-to-network-check-target-ip-10-0-134-225
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-165.ec2.internal
      uid: 92b8805b-ef07-40c2-ad4d-f4dd4a73d6a7
    resourceVersion: "30222"
    uid: b31e5312-d290-4b98-b140-b08deaa82419
  spec:
    sourcePod: network-check-source-6947749cfc-7vcfx
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T06:38:30Z"
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.813742ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:45:30Z"
    - latency: 2.047265ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:44:30Z"
    - latency: 1.822994ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:43:30Z"
    - latency: 2.4919ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:42:30Z"
    - latency: 1.910352ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:41:30Z"
    - latency: 1.995827ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:40:30Z"
    - latency: 1.820825ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:39:30Z"
    - latency: 2.135509ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:38:30Z"
    - latency: 1.936165ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:37:30Z"
    - latency: 2.211708ms
      message: 'network-check-target-ip-10-0-134-225: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:36:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T06:31:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-165-to-network-check-target-ip-10-0-140-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-165.ec2.internal
      uid: 92b8805b-ef07-40c2-ad4d-f4dd4a73d6a7
    resourceVersion: "30223"
    uid: 6ac1574d-c3b1-4c19-8bf8-a10697dd87ab
  spec:
    sourcePod: network-check-source-6947749cfc-7vcfx
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T06:38:30Z"
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.185251ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:45:30Z"
    - latency: 913.596µs
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:44:30Z"
    - latency: 983.671µs
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:43:30Z"
    - latency: 875.123µs
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:42:30Z"
    - latency: 931.184µs
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:41:30Z"
    - latency: 1.576132ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:40:30Z"
    - latency: 1.084371ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:39:30Z"
    - latency: 953.116µs
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:38:30Z"
    - latency: 1.190323ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:37:30Z"
    - latency: 1.287367ms
      message: 'network-check-target-ip-10-0-140-165: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:36:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T06:31:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-165-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-165.ec2.internal
      uid: 92b8805b-ef07-40c2-ad4d-f4dd4a73d6a7
    resourceVersion: "28966"
    uid: cd6bff90-11a2-4c39-8e27-ecf952a729ec
  spec:
    sourcePod: network-check-source-6947749cfc-7vcfx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T06:37:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 809.015µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:43:30Z"
    - latency: 1.744085ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T06:43:30Z"
    - latency: 1.083958ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:42:30Z"
    - latency: 1.85861ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T06:42:30Z"
    - latency: 867.887µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:41:30Z"
    - latency: 1.912971ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T06:41:30Z"
    - latency: 788.088µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:40:30Z"
    - latency: 2.106678ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T06:40:30Z"
    - latency: 1.10588ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T06:39:30Z"
    - latency: 1.851611ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T06:39:30Z"
kind: List
metadata:
  resourceVersion: ""