apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:48:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-171-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-171.ec2.internal
      uid: 0401b482-bb03-4d63-837e-5faa6315fbd2
    resourceVersion: "21404"
    uid: 324c33b8-ca12-4ef6-99fb-ab062501ea7b
  spec:
    sourcePod: network-check-source-869dcfcdcd-x7x6z
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:55:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 975.426µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:09:56Z"
    - latency: 853.47µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:08:56Z"
    - latency: 837.754µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:07:56Z"
    - latency: 814.952µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:06:56Z"
    - latency: 918.61µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:56Z"
    - latency: 1.237792ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:56Z"
    - latency: 799.671µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:56Z"
    - latency: 1.51897ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:56Z"
    - latency: 870.305µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:01:56Z"
    - latency: 1.091297ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:00:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:48:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-171-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-171.ec2.internal
      uid: 0401b482-bb03-4d63-837e-5faa6315fbd2
    resourceVersion: "20076"
    uid: ebb22bce-6a5a-4653-a5eb-d058bfbcdb5b
  spec:
    sourcePod: network-check-source-869dcfcdcd-x7x6z
    targetEndpoint: a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:54:56Z"
      message: 'load-balancer-api-external: tcp connection to a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.148009ms
      message: 'load-balancer-api-external: tcp connection to a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:06:56Z"
    - latency: 6.094697ms
      message: 'load-balancer-api-external: resolved host name a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:06:56Z"
    - latency: 4.187638ms
      message: 'load-balancer-api-external: tcp connection to a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:56Z"
    - latency: 6.907747ms
      message: 'load-balancer-api-external: resolved host name a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:05:56Z"
    - latency: 4.471507ms
      message: 'load-balancer-api-external: tcp connection to a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:56Z"
    - latency: 6.775251ms
      message: 'load-balancer-api-external: resolved host name a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:04:56Z"
    - latency: 5.338721ms
      message: 'load-balancer-api-external: tcp connection to a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:56Z"
    - latency: 7.620262ms
      message: 'load-balancer-api-external: resolved host name a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:03:56Z"
    - latency: 3.766544ms
      message: 'load-balancer-api-external: tcp connection to a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:56Z"
    - latency: 6.77099ms
      message: 'load-balancer-api-external: resolved host name a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:02:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:48:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-171-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-171.ec2.internal
      uid: 0401b482-bb03-4d63-837e-5faa6315fbd2
    resourceVersion: "20077"
    uid: 94394796-4a93-4ea1-8eb4-2d38065ab39a
  spec:
    sourcePod: network-check-source-869dcfcdcd-x7x6z
    targetEndpoint: a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:54:56Z"
      message: 'load-balancer-api-internal: tcp connection to a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.18836ms
      message: 'load-balancer-api-internal: tcp connection to a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:06:56Z"
    - latency: 6.063677ms
      message: 'load-balancer-api-internal: resolved host name a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:06:56Z"
    - latency: 4.164813ms
      message: 'load-balancer-api-internal: tcp connection to a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:56Z"
    - latency: 6.892716ms
      message: 'load-balancer-api-internal: resolved host name a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:05:56Z"
    - latency: 4.797517ms
      message: 'load-balancer-api-internal: tcp connection to a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:56Z"
    - latency: 6.73271ms
      message: 'load-balancer-api-internal: resolved host name a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:04:56Z"
    - latency: 5.343434ms
      message: 'load-balancer-api-internal: tcp connection to a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:56Z"
    - latency: 7.609547ms
      message: 'load-balancer-api-internal: resolved host name a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:03:56Z"
    - latency: 3.701874ms
      message: 'load-balancer-api-internal: tcp connection to a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:56Z"
    - latency: 6.771005ms
      message: 'load-balancer-api-internal: resolved host name a3c2494d1d027431bbd36cfde6416c07-02d235735e55bb23.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:02:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:48:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-171-to-network-check-target-ip-10-0-134-216
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-171.ec2.internal
      uid: 0401b482-bb03-4d63-837e-5faa6315fbd2
    resourceVersion: "21403"
    uid: 8a52ce34-a994-4fba-a4e4-24a32e7b17c9
  spec:
    sourcePod: network-check-source-869dcfcdcd-x7x6z
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:55:56Z"
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.200118ms
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:09:56Z"
    - latency: 2.455409ms
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:08:56Z"
    - latency: 2.410118ms
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:07:56Z"
    - latency: 2.515158ms
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:06:56Z"
    - latency: 2.644503ms
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:56Z"
    - latency: 2.920989ms
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:56Z"
    - latency: 2.321219ms
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:56Z"
    - latency: 2.420876ms
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:56Z"
    - latency: 2.458207ms
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:01:56Z"
    - latency: 2.620473ms
      message: 'network-check-target-ip-10-0-134-216: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:00:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:48:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-171-to-network-check-target-ip-10-0-138-171
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-171.ec2.internal
      uid: 0401b482-bb03-4d63-837e-5faa6315fbd2
    resourceVersion: "21401"
    uid: 8a7ac6b0-149e-429f-8063-745f6a1f1ce8
  spec:
    sourcePod: network-check-source-869dcfcdcd-x7x6z
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:55:56Z"
      message: 'network-check-target-ip-10-0-138-171: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 829.452µs
      message: 'network-check-target-ip-10-0-138-171: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:09:56Z"
    - latency: 915.38µs
      message: 'network-check-target-ip-10-0-138-171: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:08:56Z"
    - latency: 794.194µs
      message: 'network-check-target-ip-10-0-138-171: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:07:56Z"
    - latency: 823.577µs
      message: 'network-check-target-ip-10-0-138-171: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:06:56Z"
    - latency: 999.056µs
      message: 'network-check-target-ip-10-0-138-171: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:56Z"
    - latency: 1.265757ms
      message: 'network-check-target-ip-10-0-138-171: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:56Z"
    - latency: 1.453408ms
      message: 'network-check-target-ip-10-0-138-171: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:56Z"
    - latency: 836.347µs
      message: 'network-check-target-ip-10-0-138-171: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:56Z"
    - latency: 859.137µs
      message: 'network-check-target-ip-10-0-138-171: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:01:56Z"
    - latency: 824.348µs
      message: 'network-check-target-ip-10-0-138-171: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:00:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:48:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-171-to-network-check-target-ip-10-0-143-121
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-171.ec2.internal
      uid: 0401b482-bb03-4d63-837e-5faa6315fbd2
    resourceVersion: "21402"
    uid: 383bd086-ef81-4817-b106-00704f2eec6b
  spec:
    sourcePod: network-check-source-869dcfcdcd-x7x6z
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:55:56Z"
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.200516ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:09:56Z"
    - latency: 2.129007ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:08:56Z"
    - latency: 1.915809ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:07:56Z"
    - latency: 2.51369ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:06:56Z"
    - latency: 2.188952ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:56Z"
    - latency: 2.216687ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:56Z"
    - latency: 2.582461ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:56Z"
    - latency: 2.51095ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:56Z"
    - latency: 2.08921ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:01:56Z"
    - latency: 2.004392ms
      message: 'network-check-target-ip-10-0-143-121: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:00:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T10:48:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-171-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-171.ec2.internal
      uid: 0401b482-bb03-4d63-837e-5faa6315fbd2
    resourceVersion: "20075"
    uid: 44552a4a-3302-4932-a76d-ca4cfc59d63d
  spec:
    sourcePod: network-check-source-869dcfcdcd-x7x6z
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T10:54:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 845.383µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:06:56Z"
    - latency: 1.809721ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:06:56Z"
    - latency: 1.161919ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:05:56Z"
    - latency: 1.62417ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:05:56Z"
    - latency: 1.221488ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:04:56Z"
    - latency: 1.693304ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:04:56Z"
    - latency: 1.165469ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:03:56Z"
    - latency: 1.519052ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:03:56Z"
    - latency: 865.897µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T11:02:56Z"
    - latency: 1.978598ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T11:02:56Z"
kind: List
metadata:
  resourceVersion: ""