apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:31:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-196-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-196.ec2.internal
      uid: 6cabd81d-0a06-47e5-a7b0-70b1ecd0acd6
    resourceVersion: "32540"
    uid: 0da877bf-40eb-4aec-87a2-edf46f3a202c
  spec:
    sourcePod: network-check-source-6f8b768455-rtb2c
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:38:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 951.079µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:13:11Z"
    - latency: 1.602747ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:12:11Z"
    - latency: 1.466642ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:11:11Z"
    - latency: 1.012423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:10:11Z"
    - latency: 1.088631ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:09:11Z"
    - latency: 945.412µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:08:11Z"
    - latency: 1.192089ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:07:11Z"
    - latency: 941.646µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:06:11Z"
    - latency: 1.132414ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:05:11Z"
    - latency: 986.318µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:04:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:31:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-196-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-196.ec2.internal
      uid: 6cabd81d-0a06-47e5-a7b0-70b1ecd0acd6
    resourceVersion: "32542"
    uid: a21c3dd9-99b5-49c1-a282-6f272f3b948e
  spec:
    sourcePod: network-check-source-6f8b768455-rtb2c
    targetEndpoint: a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:37:11Z"
      message: 'load-balancer-api-external: tcp connection to a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.02002ms
      message: 'load-balancer-api-external: tcp connection to a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:13:11Z"
    - latency: 7.739623ms
      message: 'load-balancer-api-external: resolved host name a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:13:11Z"
    - latency: 4.725443ms
      message: 'load-balancer-api-external: tcp connection to a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:12:11Z"
    - latency: 8.947703ms
      message: 'load-balancer-api-external: resolved host name a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:12:11Z"
    - latency: 5.38265ms
      message: 'load-balancer-api-external: tcp connection to a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:11:11Z"
    - latency: 8.396827ms
      message: 'load-balancer-api-external: resolved host name a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:11:11Z"
    - latency: 5.208997ms
      message: 'load-balancer-api-external: tcp connection to a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:10:11Z"
    - latency: 8.969309ms
      message: 'load-balancer-api-external: resolved host name a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:10:11Z"
    - latency: 4.549366ms
      message: 'load-balancer-api-external: tcp connection to a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:09:11Z"
    - latency: 9.124384ms
      message: 'load-balancer-api-external: resolved host name a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:09:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:31:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-196-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-196.ec2.internal
      uid: 6cabd81d-0a06-47e5-a7b0-70b1ecd0acd6
    resourceVersion: "32541"
    uid: 82d1b140-a4e8-43d2-86a9-e1e7fa391593
  spec:
    sourcePod: network-check-source-6f8b768455-rtb2c
    targetEndpoint: a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:37:11Z"
      message: 'load-balancer-api-internal: tcp connection to a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.75048ms
      message: 'load-balancer-api-internal: tcp connection to a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:13:11Z"
    - latency: 7.674891ms
      message: 'load-balancer-api-internal: resolved host name a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:13:11Z"
    - latency: 4.458571ms
      message: 'load-balancer-api-internal: tcp connection to a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:12:11Z"
    - latency: 8.936604ms
      message: 'load-balancer-api-internal: resolved host name a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:12:11Z"
    - latency: 5.416847ms
      message: 'load-balancer-api-internal: tcp connection to a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:11:11Z"
    - latency: 8.330954ms
      message: 'load-balancer-api-internal: resolved host name a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:11:11Z"
    - latency: 5.213972ms
      message: 'load-balancer-api-internal: tcp connection to a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:10:11Z"
    - latency: 8.832804ms
      message: 'load-balancer-api-internal: resolved host name a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:10:11Z"
    - latency: 4.570451ms
      message: 'load-balancer-api-internal: tcp connection to a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:09:11Z"
    - latency: 9.229928ms
      message: 'load-balancer-api-internal: resolved host name a7198ea60af2147e1a720135ec94cecc-763e631fbe6e0553.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:09:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:31:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-196-to-network-check-target-ip-10-0-128-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-196.ec2.internal
      uid: 6cabd81d-0a06-47e5-a7b0-70b1ecd0acd6
    resourceVersion: "32538"
    uid: 665fa0d6-cd0b-40bb-957f-820f08bc28eb
  spec:
    sourcePod: network-check-source-6f8b768455-rtb2c
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:38:11Z"
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.471855ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:13:11Z"
    - latency: 2.422027ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:12:11Z"
    - latency: 2.740646ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:11:11Z"
    - latency: 2.592396ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:10:11Z"
    - latency: 2.232881ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:09:11Z"
    - latency: 2.357638ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:08:11Z"
    - latency: 2.277961ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:07:11Z"
    - latency: 2.218529ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:06:11Z"
    - latency: 2.438788ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:05:11Z"
    - latency: 2.517042ms
      message: 'network-check-target-ip-10-0-128-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:04:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:31:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-196-to-network-check-target-ip-10-0-134-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-196.ec2.internal
      uid: 6cabd81d-0a06-47e5-a7b0-70b1ecd0acd6
    resourceVersion: "32536"
    uid: 67c7b8fc-dffb-42b4-9ca3-1f2231aa9e48
  spec:
    sourcePod: network-check-source-6f8b768455-rtb2c
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:38:11Z"
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.312183ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:13:11Z"
    - latency: 2.136195ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:12:11Z"
    - latency: 2.256675ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:11:11Z"
    - latency: 2.35741ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:10:11Z"
    - latency: 2.247498ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:09:11Z"
    - latency: 2.265819ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:08:11Z"
    - latency: 1.979274ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:07:11Z"
    - latency: 2.443646ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:06:11Z"
    - latency: 2.344672ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:05:11Z"
    - latency: 2.396903ms
      message: 'network-check-target-ip-10-0-134-77: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:04:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:31:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-196-to-network-check-target-ip-10-0-142-196
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-196.ec2.internal
      uid: 6cabd81d-0a06-47e5-a7b0-70b1ecd0acd6
    resourceVersion: "32537"
    uid: f6bbbf81-86d5-46a1-ad2a-fcc1aeeb47e0
  spec:
    sourcePod: network-check-source-6f8b768455-rtb2c
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:38:11Z"
      message: 'network-check-target-ip-10-0-142-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.720108ms
      message: 'network-check-target-ip-10-0-142-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:13:11Z"
    - latency: 1.782802ms
      message: 'network-check-target-ip-10-0-142-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:12:11Z"
    - latency: 1.668187ms
      message: 'network-check-target-ip-10-0-142-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:11:11Z"
    - latency: 1.413267ms
      message: 'network-check-target-ip-10-0-142-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:10:11Z"
    - latency: 962.894µs
      message: 'network-check-target-ip-10-0-142-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:09:11Z"
    - latency: 1.00679ms
      message: 'network-check-target-ip-10-0-142-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:08:11Z"
    - latency: 839.294µs
      message: 'network-check-target-ip-10-0-142-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:07:11Z"
    - latency: 917.617µs
      message: 'network-check-target-ip-10-0-142-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:06:11Z"
    - latency: 945.586µs
      message: 'network-check-target-ip-10-0-142-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:05:11Z"
    - latency: 911.507µs
      message: 'network-check-target-ip-10-0-142-196: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:04:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:31:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-196-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-196.ec2.internal
      uid: 6cabd81d-0a06-47e5-a7b0-70b1ecd0acd6
    resourceVersion: "32539"
    uid: 7887a1c7-27dc-411d-af95-e7f1d8a3bf38
  spec:
    sourcePod: network-check-source-6f8b768455-rtb2c
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:37:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.609337ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:13:11Z"
    - latency: 1.919468ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:13:11Z"
    - latency: 715.979µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:12:11Z"
    - latency: 2.248747ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:12:11Z"
    - latency: 1.19351ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:11:11Z"
    - latency: 1.758239ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:11:11Z"
    - latency: 1.306241ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:10:11Z"
    - latency: 2.163322ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:10:11Z"
    - latency: 887.917µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:09:11Z"
    - latency: 1.73442ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:09:11Z"
kind: List
metadata:
  resourceVersion: ""