apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T21:03:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-38-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-38.ec2.internal
      uid: 447668db-a148-45f2-bc26-277707321e0d
    resourceVersion: "64010"
    uid: 81db8028-1945-4f13-bdee-fababa302d40
  spec:
    sourcePod: network-check-source-7bc5b6bf85-28cjp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T21:10:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 905.515µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:45:40Z"
    - latency: 1.374272ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:44:40Z"
    - latency: 885.886µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:43:40Z"
    - latency: 1.217842ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:42:40Z"
    - latency: 1.271088ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:41:40Z"
    - latency: 894.58µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:40:40Z"
    - latency: 1.912603ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:39:40Z"
    - latency: 1.0008ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:38:40Z"
    - latency: 835.219µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:37:40Z"
    - latency: 1.095689ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:36:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T21:03:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-38-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-38.ec2.internal
      uid: 447668db-a148-45f2-bc26-277707321e0d
    resourceVersion: "64012"
    uid: 991fccd9-5e40-4cdf-ac52-7f6db8acde39
  spec:
    sourcePod: network-check-source-7bc5b6bf85-28cjp
    targetEndpoint: a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T21:09:40Z"
      message: 'load-balancer-api-external: tcp connection to a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.819572ms
      message: 'load-balancer-api-external: tcp connection to a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:45:40Z"
    - latency: 8.090668ms
      message: 'load-balancer-api-external: resolved host name a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T21:45:40Z"
    - latency: 4.915441ms
      message: 'load-balancer-api-external: tcp connection to a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:44:40Z"
    - latency: 6.818685ms
      message: 'load-balancer-api-external: resolved host name a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T21:44:40Z"
    - latency: 4.79787ms
      message: 'load-balancer-api-external: tcp connection to a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:43:40Z"
    - latency: 6.777794ms
      message: 'load-balancer-api-external: resolved host name a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T21:43:40Z"
    - latency: 3.356208ms
      message: 'load-balancer-api-external: tcp connection to a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:42:40Z"
    - latency: 7.205439ms
      message: 'load-balancer-api-external: resolved host name a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T21:42:40Z"
    - latency: 4.089118ms
      message: 'load-balancer-api-external: tcp connection to a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:41:40Z"
    - latency: 6.619938ms
      message: 'load-balancer-api-external: resolved host name a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T21:41:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T21:03:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-38-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-38.ec2.internal
      uid: 447668db-a148-45f2-bc26-277707321e0d
    resourceVersion: "64011"
    uid: ed17b041-4cff-4785-967b-5819c45c06a5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-28cjp
    targetEndpoint: a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T21:09:40Z"
      message: 'load-balancer-api-internal: tcp connection to a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.218721ms
      message: 'load-balancer-api-internal: tcp connection to a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:45:40Z"
    - latency: 8.028859ms
      message: 'load-balancer-api-internal: resolved host name a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T21:45:40Z"
    - latency: 4.929129ms
      message: 'load-balancer-api-internal: tcp connection to a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:44:40Z"
    - latency: 6.729597ms
      message: 'load-balancer-api-internal: resolved host name a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T21:44:40Z"
    - latency: 3.696548ms
      message: 'load-balancer-api-internal: tcp connection to a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:43:40Z"
    - latency: 6.651237ms
      message: 'load-balancer-api-internal: resolved host name a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T21:43:40Z"
    - latency: 3.733885ms
      message: 'load-balancer-api-internal: tcp connection to a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:42:40Z"
    - latency: 7.257825ms
      message: 'load-balancer-api-internal: resolved host name a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T21:42:40Z"
    - latency: 4.050256ms
      message: 'load-balancer-api-internal: tcp connection to a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:41:40Z"
    - latency: 6.473283ms
      message: 'load-balancer-api-internal: resolved host name a4c47421356534bf6b938bc821bdba9b-f64a2c9861f62a6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T21:41:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T21:03:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-38-to-network-check-target-ip-10-0-131-38
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-38.ec2.internal
      uid: 447668db-a148-45f2-bc26-277707321e0d
    resourceVersion: "64006"
    uid: fc1dd19f-0355-4bca-96fc-d4ccab4d603d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-28cjp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T21:10:40Z"
      message: 'network-check-target-ip-10-0-131-38: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.013877ms
      message: 'network-check-target-ip-10-0-131-38: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:45:40Z"
    - latency: 1.015885ms
      message: 'network-check-target-ip-10-0-131-38: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:44:40Z"
    - latency: 912.394µs
      message: 'network-check-target-ip-10-0-131-38: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:43:40Z"
    - latency: 940.691µs
      message: 'network-check-target-ip-10-0-131-38: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:42:40Z"
    - latency: 1.008293ms
      message: 'network-check-target-ip-10-0-131-38: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:41:40Z"
    - latency: 1.194552ms
      message: 'network-check-target-ip-10-0-131-38: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:40:40Z"
    - latency: 1.950629ms
      message: 'network-check-target-ip-10-0-131-38: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:39:40Z"
    - latency: 1.193969ms
      message: 'network-check-target-ip-10-0-131-38: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:38:40Z"
    - latency: 821.093µs
      message: 'network-check-target-ip-10-0-131-38: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:37:40Z"
    - latency: 1.388717ms
      message: 'network-check-target-ip-10-0-131-38: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:36:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T21:03:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-38-to-network-check-target-ip-10-0-133-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-38.ec2.internal
      uid: 447668db-a148-45f2-bc26-277707321e0d
    resourceVersion: "64007"
    uid: 9494b610-44db-427a-a9c9-2bec0225f3fb
  spec:
    sourcePod: network-check-source-7bc5b6bf85-28cjp
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T21:10:40Z"
      message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.360666ms
      message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:45:40Z"
    - latency: 1.980128ms
      message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:44:40Z"
    - latency: 1.876871ms
      message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:43:40Z"
    - latency: 1.83483ms
      message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:42:40Z"
    - latency: 2.296107ms
      message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:41:40Z"
    - latency: 2.259039ms
      message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:40:40Z"
    - latency: 2.68093ms
      message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:39:40Z"
    - latency: 2.098697ms
      message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:38:40Z"
    - latency: 1.83036ms
      message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:37:40Z"
    - latency: 2.265078ms
      message: 'network-check-target-ip-10-0-133-4: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:36:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T21:03:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-38-to-network-check-target-ip-10-0-141-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-38.ec2.internal
      uid: 447668db-a148-45f2-bc26-277707321e0d
    resourceVersion: "64008"
    uid: 1e4e1311-41da-44ff-b235-8d44a4aeaa77
  spec:
    sourcePod: network-check-source-7bc5b6bf85-28cjp
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T21:10:40Z"
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.42ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:45:40Z"
    - latency: 2.293374ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:44:40Z"
    - latency: 2.035799ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:43:40Z"
    - latency: 2.636398ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:42:40Z"
    - latency: 2.24004ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:41:40Z"
    - latency: 2.292445ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:40:40Z"
    - latency: 2.680133ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:39:40Z"
    - latency: 2.247312ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:38:40Z"
    - latency: 2.060138ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:37:40Z"
    - latency: 2.321577ms
      message: 'network-check-target-ip-10-0-141-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:36:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T21:03:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-38-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-38.ec2.internal
      uid: 447668db-a148-45f2-bc26-277707321e0d
    resourceVersion: "64009"
    uid: 9efc2c52-063d-49e7-a436-ed4c06c41c34
  spec:
    sourcePod: network-check-source-7bc5b6bf85-28cjp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T21:09:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.303708ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:45:40Z"
    - latency: 2.251359ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T21:45:40Z"
    - latency: 1.421183ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:44:40Z"
    - latency: 1.821501ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T21:44:40Z"
    - latency: 1.019454ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:43:40Z"
    - latency: 1.800124ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T21:43:40Z"
    - latency: 945.553µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:42:40Z"
    - latency: 1.972589ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T21:42:40Z"
    - latency: 1.048581ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T21:41:40Z"
    - latency: 1.737771ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T21:41:40Z"
kind: List
metadata:
  resourceVersion: ""