apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:36:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-251-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-251.ec2.internal
      uid: 7daba3ef-94a7-479f-992b-df78b4d504dd
    resourceVersion: "68366"
    uid: f3627e21-19ef-4f87-a388-0e8db96625ed
  spec:
    sourcePod: network-check-source-6f8b768455-96fs4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:43:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.552889ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:11:39Z"
    - latency: 1.320976ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:10:39Z"
    - latency: 793.041µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:09:39Z"
    - latency: 929.34µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:08:39Z"
    - latency: 1.459866ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:07:39Z"
    - latency: 1.056336ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:06:39Z"
    - latency: 905.978µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:05:39Z"
    - latency: 1.115888ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:04:39Z"
    - latency: 1.568885ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:03:39Z"
    - latency: 1.176962ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:02:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:36:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-251-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-251.ec2.internal
      uid: 7daba3ef-94a7-479f-992b-df78b4d504dd
    resourceVersion: "69294"
    uid: dbd997e5-3043-4ab1-bfe1-9010a412b9b1
  spec:
    sourcePod: network-check-source-6f8b768455-96fs4
    targetEndpoint: a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:42:39Z"
      message: 'load-balancer-api-external: tcp connection to a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.633997ms
      message: 'load-balancer-api-external: tcp connection to a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:12:39Z"
    - latency: 6.122323ms
      message: 'load-balancer-api-external: resolved host name a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:12:39Z"
    - latency: 5.327298ms
      message: 'load-balancer-api-external: tcp connection to a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:11:39Z"
    - latency: 6.998673ms
      message: 'load-balancer-api-external: resolved host name a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:11:39Z"
    - latency: 4.405289ms
      message: 'load-balancer-api-external: tcp connection to a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:10:39Z"
    - latency: 6.042284ms
      message: 'load-balancer-api-external: resolved host name a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:10:39Z"
    - latency: 4.558307ms
      message: 'load-balancer-api-external: tcp connection to a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:09:39Z"
    - latency: 7.646937ms
      message: 'load-balancer-api-external: resolved host name a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:09:39Z"
    - latency: 4.681437ms
      message: 'load-balancer-api-external: tcp connection to a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:08:39Z"
    - latency: 7.191742ms
      message: 'load-balancer-api-external: resolved host name a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:08:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:36:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-251-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-251.ec2.internal
      uid: 7daba3ef-94a7-479f-992b-df78b4d504dd
    resourceVersion: "69293"
    uid: d03d4687-dde4-4ff0-8c38-68b03166cf65
  spec:
    sourcePod: network-check-source-6f8b768455-96fs4
    targetEndpoint: a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:42:39Z"
      message: 'load-balancer-api-internal: tcp connection to a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.828025ms
      message: 'load-balancer-api-internal: tcp connection to a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:12:39Z"
    - latency: 6.156393ms
      message: 'load-balancer-api-internal: resolved host name a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:12:39Z"
    - latency: 5.320612ms
      message: 'load-balancer-api-internal: tcp connection to a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:11:39Z"
    - latency: 7.035152ms
      message: 'load-balancer-api-internal: resolved host name a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:11:39Z"
    - latency: 4.588818ms
      message: 'load-balancer-api-internal: tcp connection to a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:10:39Z"
    - latency: 6.081127ms
      message: 'load-balancer-api-internal: resolved host name a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:10:39Z"
    - latency: 4.898063ms
      message: 'load-balancer-api-internal: tcp connection to a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:09:39Z"
    - latency: 7.727245ms
      message: 'load-balancer-api-internal: resolved host name a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:09:39Z"
    - latency: 6.468694ms
      message: 'load-balancer-api-internal: tcp connection to a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:08:39Z"
    - latency: 7.248367ms
      message: 'load-balancer-api-internal: resolved host name a53a1697b068b4d4aab463f5c400928a-3d2ab7d2d624e042.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:08:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:36:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-251-to-network-check-target-ip-10-0-130-207
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-251.ec2.internal
      uid: 7daba3ef-94a7-479f-992b-df78b4d504dd
    resourceVersion: "68365"
    uid: 4f7ee7d2-1798-4f63-9cfa-743360fa48e2
  spec:
    sourcePod: network-check-source-6f8b768455-96fs4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:43:39Z"
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.576132ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:11:39Z"
    - latency: 2.204925ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:10:39Z"
    - latency: 1.736246ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:09:39Z"
    - latency: 2.184919ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:08:39Z"
    - latency: 2.335043ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:07:39Z"
    - latency: 2.078696ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:06:39Z"
    - latency: 2.244574ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:05:39Z"
    - latency: 2.299757ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:04:39Z"
    - latency: 2.340078ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:03:39Z"
    - latency: 2.150891ms
      message: 'network-check-target-ip-10-0-130-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:02:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:36:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-251-to-network-check-target-ip-10-0-131-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-251.ec2.internal
      uid: 7daba3ef-94a7-479f-992b-df78b4d504dd
    resourceVersion: "68364"
    uid: 1327e20f-c638-48af-aed2-bf957795aa9e
  spec:
    sourcePod: network-check-source-6f8b768455-96fs4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:43:39Z"
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.109341ms
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:11:39Z"
    - latency: 2.142347ms
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:10:39Z"
    - latency: 2.074087ms
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:09:39Z"
    - latency: 1.996883ms
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:08:39Z"
    - latency: 1.856582ms
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:07:39Z"
    - latency: 2.07964ms
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:06:39Z"
    - latency: 1.888263ms
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:05:39Z"
    - latency: 1.9384ms
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:04:39Z"
    - latency: 2.062311ms
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:03:39Z"
    - latency: 1.992736ms
      message: 'network-check-target-ip-10-0-131-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:02:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:36:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-251-to-network-check-target-ip-10-0-133-251
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-251.ec2.internal
      uid: 7daba3ef-94a7-479f-992b-df78b4d504dd
    resourceVersion: "68363"
    uid: 594ba7fb-dc7b-4793-9347-4c4aea3f38b7
  spec:
    sourcePod: network-check-source-6f8b768455-96fs4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:43:39Z"
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.070534ms
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:11:39Z"
    - latency: 906.414µs
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:10:39Z"
    - latency: 898.232µs
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:09:39Z"
    - latency: 1.24001ms
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:08:39Z"
    - latency: 1.727515ms
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:07:39Z"
    - latency: 1.125453ms
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:06:39Z"
    - latency: 1.687048ms
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:05:39Z"
    - latency: 1.034587ms
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:04:39Z"
    - latency: 998.44µs
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:03:39Z"
    - latency: 1.068376ms
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:02:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:36:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-251-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-251.ec2.internal
      uid: 7daba3ef-94a7-479f-992b-df78b4d504dd
    resourceVersion: "69292"
    uid: 84307ed5-7278-487d-a33f-96002d540cf8
  spec:
    sourcePod: network-check-source-6f8b768455-96fs4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:42:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 773.105µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:12:39Z"
    - latency: 1.766865ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:12:39Z"
    - latency: 899.386µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:11:39Z"
    - latency: 1.983592ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:11:39Z"
    - latency: 936.537µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:10:39Z"
    - latency: 2.097358ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:10:39Z"
    - latency: 888.93µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:09:39Z"
    - latency: 2.353382ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:09:39Z"
    - latency: 739.167µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:08:39Z"
    - latency: 2.14921ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:08:39Z"
kind: List
metadata:
  resourceVersion: ""