apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T22:10:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-154-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-154.ec2.internal
      uid: b26c2378-6891-45a3-98a1-9940f7d6993c
    resourceVersion: "44988"
    uid: 138fb039-6868-44d5-a7d6-253e1ad73b84
  spec:
    sourcePod: network-check-source-8894fc9bd-dbcsp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T22:17:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 969.659µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:38:37Z"
    - latency: 1.051122ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:37:37Z"
    - latency: 958.732µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:36:37Z"
    - latency: 788.684µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:35:37Z"
    - latency: 766.378µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:34:37Z"
    - latency: 976.726µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:33:37Z"
    - latency: 1.124541ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:32:37Z"
    - latency: 1.131346ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:31:37Z"
    - latency: 812.161µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:30:37Z"
    - latency: 1.213667ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:29:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T22:10:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-154-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-154.ec2.internal
      uid: b26c2378-6891-45a3-98a1-9940f7d6993c
    resourceVersion: "40340"
    uid: 05991b3b-ad44-4360-a12e-a465c72583a4
  spec:
    sourcePod: network-check-source-8894fc9bd-dbcsp
    targetEndpoint: a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T22:16:37Z"
      message: 'load-balancer-api-external: tcp connection to a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.232418ms
      message: 'load-balancer-api-external: tcp connection to a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:34:37Z"
    - latency: 8.198489ms
      message: 'load-balancer-api-external: resolved host name a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:34:37Z"
    - latency: 3.693227ms
      message: 'load-balancer-api-external: tcp connection to a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:33:37Z"
    - latency: 8.551014ms
      message: 'load-balancer-api-external: resolved host name a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:33:37Z"
    - latency: 4.163482ms
      message: 'load-balancer-api-external: tcp connection to a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:32:37Z"
    - latency: 8.482807ms
      message: 'load-balancer-api-external: resolved host name a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:32:37Z"
    - latency: 4.772382ms
      message: 'load-balancer-api-external: tcp connection to a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:31:37Z"
    - latency: 12.927372ms
      message: 'load-balancer-api-external: resolved host name a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:31:37Z"
    - latency: 4.840808ms
      message: 'load-balancer-api-external: tcp connection to a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:30:37Z"
    - latency: 9.019945ms
      message: 'load-balancer-api-external: resolved host name a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:30:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T22:10:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-154-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-154.ec2.internal
      uid: b26c2378-6891-45a3-98a1-9940f7d6993c
    resourceVersion: "40339"
    uid: f0e34e5d-ecf0-4908-ae50-a7f3da3e10fb
  spec:
    sourcePod: network-check-source-8894fc9bd-dbcsp
    targetEndpoint: a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T22:16:37Z"
      message: 'load-balancer-api-internal: tcp connection to a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.191761ms
      message: 'load-balancer-api-internal: tcp connection to a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:34:37Z"
    - latency: 8.252688ms
      message: 'load-balancer-api-internal: resolved host name a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:34:37Z"
    - latency: 3.820954ms
      message: 'load-balancer-api-internal: tcp connection to a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:33:37Z"
    - latency: 8.623708ms
      message: 'load-balancer-api-internal: resolved host name a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:33:37Z"
    - latency: 4.836458ms
      message: 'load-balancer-api-internal: tcp connection to a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:32:37Z"
    - latency: 8.538469ms
      message: 'load-balancer-api-internal: resolved host name a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:32:37Z"
    - latency: 5.118407ms
      message: 'load-balancer-api-internal: tcp connection to a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:31:37Z"
    - latency: 12.955751ms
      message: 'load-balancer-api-internal: resolved host name a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:31:37Z"
    - latency: 4.868627ms
      message: 'load-balancer-api-internal: tcp connection to a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:30:37Z"
    - latency: 9.066494ms
      message: 'load-balancer-api-internal: resolved host name a33553628b42d4412b797911746cfcd1-0ca1cfb29e31f886.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:30:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T22:10:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-154-to-network-check-target-ip-10-0-129-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-154.ec2.internal
      uid: b26c2378-6891-45a3-98a1-9940f7d6993c
    resourceVersion: "44987"
    uid: 071b3c09-8117-424b-a14a-871ca2d036e5
  spec:
    sourcePod: network-check-source-8894fc9bd-dbcsp
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T22:17:37Z"
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.250962ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:38:37Z"
    - latency: 2.236358ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:37:37Z"
    - latency: 1.885774ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:36:37Z"
    - latency: 2.068326ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:35:37Z"
    - latency: 2.137803ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:34:37Z"
    - latency: 2.162029ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:33:37Z"
    - latency: 2.007025ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:32:37Z"
    - latency: 2.186578ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:31:37Z"
    - latency: 2.08739ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:30:37Z"
    - latency: 2.231856ms
      message: 'network-check-target-ip-10-0-129-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:29:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T22:10:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-154-to-network-check-target-ip-10-0-130-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-154.ec2.internal
      uid: b26c2378-6891-45a3-98a1-9940f7d6993c
    resourceVersion: "44986"
    uid: d73b7cb3-acd3-4ee8-83e2-da8e54eaaebe
  spec:
    sourcePod: network-check-source-8894fc9bd-dbcsp
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T22:17:37Z"
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.515684ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:38:37Z"
    - latency: 1.963019ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:37:37Z"
    - latency: 1.69738ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:36:37Z"
    - latency: 1.934869ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:35:37Z"
    - latency: 1.832586ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:34:37Z"
    - latency: 1.858293ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:33:37Z"
    - latency: 2.099243ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:32:37Z"
    - latency: 2.243543ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:31:37Z"
    - latency: 1.6962ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:30:37Z"
    - latency: 1.865197ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:29:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T22:10:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-154-to-network-check-target-ip-10-0-138-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-154.ec2.internal
      uid: b26c2378-6891-45a3-98a1-9940f7d6993c
    resourceVersion: "44985"
    uid: f3cbff42-4c32-4304-8bb7-3b4ff010add9
  spec:
    sourcePod: network-check-source-8894fc9bd-dbcsp
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T22:17:37Z"
      message: 'network-check-target-ip-10-0-138-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.36427ms
      message: 'network-check-target-ip-10-0-138-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:38:37Z"
    - latency: 1.365537ms
      message: 'network-check-target-ip-10-0-138-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:37:37Z"
    - latency: 1.109904ms
      message: 'network-check-target-ip-10-0-138-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:36:37Z"
    - latency: 792.419µs
      message: 'network-check-target-ip-10-0-138-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:35:37Z"
    - latency: 769.499µs
      message: 'network-check-target-ip-10-0-138-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:34:37Z"
    - latency: 808.707µs
      message: 'network-check-target-ip-10-0-138-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:33:37Z"
    - latency: 1.348695ms
      message: 'network-check-target-ip-10-0-138-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:32:37Z"
    - latency: 1.397553ms
      message: 'network-check-target-ip-10-0-138-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:31:37Z"
    - latency: 615.93µs
      message: 'network-check-target-ip-10-0-138-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:30:37Z"
    - latency: 1.309973ms
      message: 'network-check-target-ip-10-0-138-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:29:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T22:10:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-154-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-154.ec2.internal
      uid: b26c2378-6891-45a3-98a1-9940f7d6993c
    resourceVersion: "40338"
    uid: e59e3bae-73b0-49f6-ac73-30a889540636
  spec:
    sourcePod: network-check-source-8894fc9bd-dbcsp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T22:16:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 897.29µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:34:37Z"
    - latency: 2.051425ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:34:37Z"
    - latency: 809.802µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:33:37Z"
    - latency: 1.95797ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:33:37Z"
    - latency: 835.752µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:32:37Z"
    - latency: 1.953003ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:32:37Z"
    - latency: 873.152µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:31:37Z"
    - latency: 1.627645ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:31:37Z"
    - latency: 779.627µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T22:30:37Z"
    - latency: 2.161898ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T22:30:37Z"
kind: List
metadata:
  resourceVersion: ""