apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-25T00:43:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-9-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-9.ec2.internal
      uid: 8366f20a-0bf8-4861-a382-f2467ca456ac
    resourceVersion: "72636"
    uid: 537573ed-5caf-45be-9501-40d325467616
  spec:
    sourcePod: network-check-source-7d88cb55d8-khdsb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-25T00:50:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.167436ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:32:51Z"
    - latency: 1.184601ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:31:51Z"
    - latency: 1.017488ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:30:51Z"
    - latency: 1.051216ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:29:51Z"
    - latency: 1.099191ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:28:51Z"
    - latency: 1.264828ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:27:51Z"
    - latency: 1.03712ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:26:51Z"
    - latency: 1.453977ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:25:51Z"
    - latency: 1.456824ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:24:51Z"
    - latency: 923.008µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:23:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-25T00:43:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-9-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-9.ec2.internal
      uid: 8366f20a-0bf8-4861-a382-f2467ca456ac
    resourceVersion: "71548"
    uid: 0aabd116-3f4c-4acf-b05a-6d6b95d59cf0
  spec:
    sourcePod: network-check-source-7d88cb55d8-khdsb
    targetEndpoint: a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-25T00:49:51Z"
      message: 'load-balancer-api-external: tcp connection to a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.500111ms
      message: 'load-balancer-api-external: tcp connection to a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:31:51Z"
    - latency: 7.024766ms
      message: 'load-balancer-api-external: resolved host name a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-25T01:31:51Z"
    - latency: 3.74701ms
      message: 'load-balancer-api-external: tcp connection to a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:30:51Z"
    - latency: 7.649713ms
      message: 'load-balancer-api-external: resolved host name a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-25T01:30:51Z"
    - latency: 4.246227ms
      message: 'load-balancer-api-external: tcp connection to a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:29:51Z"
    - latency: 7.272737ms
      message: 'load-balancer-api-external: resolved host name a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-25T01:29:51Z"
    - latency: 4.700587ms
      message: 'load-balancer-api-external: tcp connection to a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:28:51Z"
    - latency: 7.043317ms
      message: 'load-balancer-api-external: resolved host name a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-25T01:28:51Z"
    - latency: 3.771944ms
      message: 'load-balancer-api-external: tcp connection to a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:27:51Z"
    - latency: 6.323643ms
      message: 'load-balancer-api-external: resolved host name a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-25T01:27:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-25T00:43:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-9-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-9.ec2.internal
      uid: 8366f20a-0bf8-4861-a382-f2467ca456ac
    resourceVersion: "71547"
    uid: b08c2a46-f4f8-4cac-be4e-35e8af7bd10e
  spec:
    sourcePod: network-check-source-7d88cb55d8-khdsb
    targetEndpoint: a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-25T00:49:51Z"
      message: 'load-balancer-api-internal: tcp connection to a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.483999ms
      message: 'load-balancer-api-internal: tcp connection to a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:31:51Z"
    - latency: 7.008905ms
      message: 'load-balancer-api-internal: resolved host name a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-25T01:31:51Z"
    - latency: 3.742172ms
      message: 'load-balancer-api-internal: tcp connection to a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:30:51Z"
    - latency: 7.597554ms
      message: 'load-balancer-api-internal: resolved host name a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-25T01:30:51Z"
    - latency: 4.213192ms
      message: 'load-balancer-api-internal: tcp connection to a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:29:51Z"
    - latency: 7.252513ms
      message: 'load-balancer-api-internal: resolved host name a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-25T01:29:51Z"
    - latency: 4.754183ms
      message: 'load-balancer-api-internal: tcp connection to a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:28:51Z"
    - latency: 7.059833ms
      message: 'load-balancer-api-internal: resolved host name a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-25T01:28:51Z"
    - latency: 3.823667ms
      message: 'load-balancer-api-internal: tcp connection to a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:27:51Z"
    - latency: 6.263128ms
      message: 'load-balancer-api-internal: resolved host name a3a774fc6e4a14210a7052df5311a846-85ee8da77f2aef71.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-25T01:27:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-25T01:01:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-9-to-network-check-target-ip-10-0-136-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-9.ec2.internal
      uid: 8366f20a-0bf8-4861-a382-f2467ca456ac
    resourceVersion: "68555"
    uid: 8ac94f14-de83-4142-82e0-96ae58ad5b0d
  spec:
    sourcePod: network-check-source-7d88cb55d8-khdsb
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-25T01:08:13Z"
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.141497ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:29:13Z"
    - latency: 932.686µs
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:28:13Z"
    - latency: 917.296µs
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:27:13Z"
    - latency: 1.189335ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:26:13Z"
    - latency: 936.662µs
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:25:13Z"
    - latency: 1.123204ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:24:13Z"
    - latency: 1.10332ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:23:13Z"
    - latency: 860.182µs
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:22:13Z"
    - latency: 1.04449ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:21:13Z"
    - latency: 1.180044ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:20:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-25T00:43:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-9-to-network-check-target-ip-10-0-140-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-9.ec2.internal
      uid: 8366f20a-0bf8-4861-a382-f2467ca456ac
    resourceVersion: "72635"
    uid: c4b205d4-98a7-4015-9693-c2da0c2f9192
  spec:
    sourcePod: network-check-source-7d88cb55d8-khdsb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-25T00:50:51Z"
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.008686ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:32:51Z"
    - latency: 1.955287ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:31:51Z"
    - latency: 1.967086ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:30:51Z"
    - latency: 2.208093ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:29:51Z"
    - latency: 2.146212ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:28:51Z"
    - latency: 2.336131ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:27:51Z"
    - latency: 2.234501ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:26:51Z"
    - latency: 2.636387ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:25:51Z"
    - latency: 2.238701ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:24:51Z"
    - latency: 2.300564ms
      message: 'network-check-target-ip-10-0-140-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:23:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-25T00:43:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-9-to-network-check-target-ip-10-0-141-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-9.ec2.internal
      uid: 8366f20a-0bf8-4861-a382-f2467ca456ac
    resourceVersion: "72634"
    uid: 9eaf2aab-87f1-49f0-a633-e3d994e343bd
  spec:
    sourcePod: network-check-source-7d88cb55d8-khdsb
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-25T00:50:51Z"
      message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.47333ms
      message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:32:51Z"
    - latency: 2.205313ms
      message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:31:51Z"
    - latency: 2.508958ms
      message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:30:51Z"
    - latency: 2.358679ms
      message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:29:51Z"
    - latency: 2.180486ms
      message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:28:51Z"
    - latency: 2.779594ms
      message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:27:51Z"
    - latency: 2.527879ms
      message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:26:51Z"
    - latency: 2.313432ms
      message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:25:51Z"
    - latency: 2.931652ms
      message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:24:51Z"
    - latency: 1.901026ms
      message: 'network-check-target-ip-10-0-141-233: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:23:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-25T00:43:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-9-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-9.ec2.internal
      uid: 8366f20a-0bf8-4861-a382-f2467ca456ac
    resourceVersion: "71545"
    uid: 8da8f777-0aa1-4ca4-9374-a1291c57a2a7
  spec:
    sourcePod: network-check-source-7d88cb55d8-khdsb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-25T00:49:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 875.657µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:31:51Z"
    - latency: 2.073502ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-25T01:31:51Z"
    - latency: 890.64µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:30:51Z"
    - latency: 2.185571ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-25T01:30:51Z"
    - latency: 984.731µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:29:51Z"
    - latency: 1.678034ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-25T01:29:51Z"
    - latency: 1.17899ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:28:51Z"
    - latency: 1.555663ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-25T01:28:51Z"
    - latency: 1.334001ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-25T01:27:51Z"
    - latency: 1.809263ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-25T01:27:51Z"
kind: List
metadata:
  resourceVersion: ""