apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:24:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-35-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-35.ec2.internal
      uid: 77c47b41-3dec-4a6a-bbb1-17b29bc28be0
    resourceVersion: "52714"
    uid: cf83d504-d3a2-4aa7-a718-f0267b738047
  spec:
    sourcePod: network-check-source-685456655f-rzn7d
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:31:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.139815ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:52:31Z"
    - latency: 1.212078ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:51:31Z"
    - latency: 1.090851ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:50:31Z"
    - latency: 1.56058ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:49:31Z"
    - latency: 1.122045ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:48:31Z"
    - latency: 1.457839ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:47:31Z"
    - latency: 1.925511ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:46:31Z"
    - latency: 1.169164ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:45:31Z"
    - latency: 1.294718ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:44:31Z"
    - latency: 1.28565ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:43:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:24:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-35-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-35.ec2.internal
      uid: 77c47b41-3dec-4a6a-bbb1-17b29bc28be0
    resourceVersion: "54269"
    uid: faf6883b-e237-41db-94c1-243f1476641e
  spec:
    sourcePod: network-check-source-685456655f-rzn7d
    targetEndpoint: a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:30:31Z"
      message: 'load-balancer-api-external: tcp connection to a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.78974ms
      message: 'load-balancer-api-external: tcp connection to a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:54:31Z"
    - latency: 8.814966ms
      message: 'load-balancer-api-external: resolved host name a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:54:31Z"
    - latency: 4.113221ms
      message: 'load-balancer-api-external: tcp connection to a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:53:31Z"
    - latency: 9.802576ms
      message: 'load-balancer-api-external: resolved host name a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:53:31Z"
    - latency: 5.694367ms
      message: 'load-balancer-api-external: tcp connection to a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:52:31Z"
    - latency: 8.950845ms
      message: 'load-balancer-api-external: resolved host name a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:52:31Z"
    - latency: 5.011841ms
      message: 'load-balancer-api-external: tcp connection to a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:51:31Z"
    - latency: 8.891233ms
      message: 'load-balancer-api-external: resolved host name a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:51:31Z"
    - latency: 5.387272ms
      message: 'load-balancer-api-external: tcp connection to a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:50:31Z"
    - latency: 7.32922ms
      message: 'load-balancer-api-external: resolved host name a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:50:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:24:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-35-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-35.ec2.internal
      uid: 77c47b41-3dec-4a6a-bbb1-17b29bc28be0
    resourceVersion: "54268"
    uid: d3c01177-8877-42fc-8906-091320d1a0e0
  spec:
    sourcePod: network-check-source-685456655f-rzn7d
    targetEndpoint: a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:30:31Z"
      message: 'load-balancer-api-internal: tcp connection to a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.831484ms
      message: 'load-balancer-api-internal: tcp connection to a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:54:31Z"
    - latency: 8.730514ms
      message: 'load-balancer-api-internal: resolved host name a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:54:31Z"
    - latency: 4.075735ms
      message: 'load-balancer-api-internal: tcp connection to a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:53:31Z"
    - latency: 9.86173ms
      message: 'load-balancer-api-internal: resolved host name a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:53:31Z"
    - latency: 5.666613ms
      message: 'load-balancer-api-internal: tcp connection to a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:52:31Z"
    - latency: 8.985493ms
      message: 'load-balancer-api-internal: resolved host name a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:52:31Z"
    - latency: 5.420524ms
      message: 'load-balancer-api-internal: tcp connection to a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:51:31Z"
    - latency: 8.947999ms
      message: 'load-balancer-api-internal: resolved host name a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:51:31Z"
    - latency: 6.006593ms
      message: 'load-balancer-api-internal: tcp connection to a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:50:31Z"
    - latency: 7.289184ms
      message: 'load-balancer-api-internal: resolved host name a39ad9db87eb946ac8bfdf9c8be642dd-0a1ea781a4095df1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:50:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:24:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-35-to-network-check-target-ip-10-0-132-149
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-35.ec2.internal
      uid: 77c47b41-3dec-4a6a-bbb1-17b29bc28be0
    resourceVersion: "52713"
    uid: f305380f-7689-44b2-8878-0ba7b671f1f2
  spec:
    sourcePod: network-check-source-685456655f-rzn7d
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:31:31Z"
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.582566ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:52:31Z"
    - latency: 2.429073ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:51:31Z"
    - latency: 2.486676ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:50:31Z"
    - latency: 2.801461ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:49:31Z"
    - latency: 2.879008ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:48:31Z"
    - latency: 2.947339ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:47:31Z"
    - latency: 2.608522ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:46:31Z"
    - latency: 2.794726ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:45:31Z"
    - latency: 2.542628ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:44:31Z"
    - latency: 2.893869ms
      message: 'network-check-target-ip-10-0-132-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:43:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:24:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-35-to-network-check-target-ip-10-0-134-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-35.ec2.internal
      uid: 77c47b41-3dec-4a6a-bbb1-17b29bc28be0
    resourceVersion: "52712"
    uid: 68f17474-9da3-4899-aad4-bf9583b0ae95
  spec:
    sourcePod: network-check-source-685456655f-rzn7d
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:31:31Z"
      message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.636678ms
      message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:52:31Z"
    - latency: 2.330834ms
      message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:51:31Z"
    - latency: 2.653601ms
      message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:50:31Z"
    - latency: 2.733925ms
      message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:49:31Z"
    - latency: 2.9817ms
      message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:48:31Z"
    - latency: 2.304423ms
      message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:47:31Z"
    - latency: 2.664979ms
      message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:46:31Z"
    - latency: 2.791723ms
      message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:45:31Z"
    - latency: 2.723037ms
      message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:44:31Z"
    - latency: 2.403249ms
      message: 'network-check-target-ip-10-0-134-64: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:43:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:24:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-35-to-network-check-target-ip-10-0-139-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-35.ec2.internal
      uid: 77c47b41-3dec-4a6a-bbb1-17b29bc28be0
    resourceVersion: "52711"
    uid: 2f65116b-0bd1-44ec-8159-7c234621b42d
  spec:
    sourcePod: network-check-source-685456655f-rzn7d
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:31:31Z"
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.221348ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:52:31Z"
    - latency: 1.345629ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:51:31Z"
    - latency: 1.24303ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:50:31Z"
    - latency: 1.094677ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:49:31Z"
    - latency: 1.32806ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:48:31Z"
    - latency: 1.242268ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:47:31Z"
    - latency: 1.101005ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:46:31Z"
    - latency: 1.080801ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:45:31Z"
    - latency: 1.422704ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:44:31Z"
    - latency: 1.564695ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:43:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:24:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-35-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-35.ec2.internal
      uid: 77c47b41-3dec-4a6a-bbb1-17b29bc28be0
    resourceVersion: "54267"
    uid: 6cf27b26-df55-4495-af18-dff168691d8e
  spec:
    sourcePod: network-check-source-685456655f-rzn7d
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:30:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 815.245µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:54:31Z"
    - latency: 2.246297ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:54:31Z"
    - latency: 814.605µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:53:31Z"
    - latency: 2.075005ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:53:31Z"
    - latency: 1.104479ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:52:31Z"
    - latency: 2.023304ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:52:31Z"
    - latency: 1.052928ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:51:31Z"
    - latency: 1.846721ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:51:31Z"
    - latency: 1.041132ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:50:31Z"
    - latency: 1.900306ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:50:31Z"
kind: List
metadata:
  resourceVersion: ""