apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:53:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-55-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-55.ec2.internal
      uid: 68a5a2c1-7e7b-4c48-8c74-edeb78dc508b
    resourceVersion: "54238"
    uid: ae92470f-e84f-4e8a-a981-990a14acfe79
  spec:
    sourcePod: network-check-source-6f8b768455-bm485
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:00:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.213307ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:21:42Z"
    - latency: 1.450375ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:20:42Z"
    - latency: 1.199443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:19:42Z"
    - latency: 1.214978ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:18:42Z"
    - latency: 1.206211ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:17:42Z"
    - latency: 1.644183ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:16:42Z"
    - latency: 1.042932ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:15:42Z"
    - latency: 1.15053ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:14:42Z"
    - latency: 1.305941ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:13:42Z"
    - latency: 1.545533ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:12:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:53:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-55-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-55.ec2.internal
      uid: 68a5a2c1-7e7b-4c48-8c74-edeb78dc508b
    resourceVersion: "55818"
    uid: 82734761-a771-4e76-a437-4560f1c89e52
  spec:
    sourcePod: network-check-source-6f8b768455-bm485
    targetEndpoint: ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:59:42Z"
      message: 'load-balancer-api-external: tcp connection to ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.794477ms
      message: 'load-balancer-api-external: tcp connection to ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:23:42Z"
    - latency: 6.850667ms
      message: 'load-balancer-api-external: resolved host name ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:23:42Z"
    - latency: 5.741051ms
      message: 'load-balancer-api-external: tcp connection to ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:22:42Z"
    - latency: 8.124003ms
      message: 'load-balancer-api-external: resolved host name ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:22:42Z"
    - latency: 5.417351ms
      message: 'load-balancer-api-external: tcp connection to ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:21:42Z"
    - latency: 7.405139ms
      message: 'load-balancer-api-external: resolved host name ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:21:42Z"
    - latency: 4.33998ms
      message: 'load-balancer-api-external: tcp connection to ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:20:42Z"
    - latency: 7.253458ms
      message: 'load-balancer-api-external: resolved host name ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:20:42Z"
    - latency: 4.897422ms
      message: 'load-balancer-api-external: tcp connection to ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:19:42Z"
    - latency: 6.328073ms
      message: 'load-balancer-api-external: resolved host name ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:19:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:53:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-55-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-55.ec2.internal
      uid: 68a5a2c1-7e7b-4c48-8c74-edeb78dc508b
    resourceVersion: "55819"
    uid: 9e94d0be-141b-47af-9dc9-068401484311
  spec:
    sourcePod: network-check-source-6f8b768455-bm485
    targetEndpoint: ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:59:42Z"
      message: 'load-balancer-api-internal: tcp connection to ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.038524ms
      message: 'load-balancer-api-internal: tcp connection to ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:23:42Z"
    - latency: 6.637729ms
      message: 'load-balancer-api-internal: resolved host name ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:23:42Z"
    - latency: 4.323483ms
      message: 'load-balancer-api-internal: tcp connection to ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:22:42Z"
    - latency: 7.905848ms
      message: 'load-balancer-api-internal: resolved host name ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:22:42Z"
    - latency: 5.461725ms
      message: 'load-balancer-api-internal: tcp connection to ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:21:42Z"
    - latency: 7.329004ms
      message: 'load-balancer-api-internal: resolved host name ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:21:42Z"
    - latency: 4.35201ms
      message: 'load-balancer-api-internal: tcp connection to ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:20:42Z"
    - latency: 7.178259ms
      message: 'load-balancer-api-internal: resolved host name ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:20:42Z"
    - latency: 4.958505ms
      message: 'load-balancer-api-internal: tcp connection to ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:19:42Z"
    - latency: 6.241463ms
      message: 'load-balancer-api-internal: resolved host name ae3231136bc6b48cc9897586386462a8-c11735daaf2c9ea6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:19:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:53:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-55-to-network-check-target-ip-10-0-128-225
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-55.ec2.internal
      uid: 68a5a2c1-7e7b-4c48-8c74-edeb78dc508b
    resourceVersion: "54236"
    uid: 3209a980-5e0a-44fa-8a47-3079370a4904
  spec:
    sourcePod: network-check-source-6f8b768455-bm485
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:00:42Z"
      message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.076991ms
      message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:21:42Z"
    - latency: 3.066957ms
      message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:20:42Z"
    - latency: 2.375062ms
      message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:19:42Z"
    - latency: 2.310615ms
      message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:18:42Z"
    - latency: 2.928631ms
      message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:17:42Z"
    - latency: 2.410607ms
      message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:16:42Z"
    - latency: 2.05677ms
      message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:15:42Z"
    - latency: 2.035815ms
      message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:14:42Z"
    - latency: 1.896903ms
      message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:13:42Z"
    - latency: 1.972526ms
      message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:12:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:53:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-55-to-network-check-target-ip-10-0-136-247
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-55.ec2.internal
      uid: 68a5a2c1-7e7b-4c48-8c74-edeb78dc508b
    resourceVersion: "54235"
    uid: 7445fd22-bcfe-47e8-8528-5f1ec857ef27
  spec:
    sourcePod: network-check-source-6f8b768455-bm485
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:00:42Z"
      message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.147787ms
      message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:21:42Z"
    - latency: 2.514001ms
      message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:20:42Z"
    - latency: 2.581603ms
      message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:19:42Z"
    - latency: 2.376801ms
      message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:18:42Z"
    - latency: 2.264499ms
      message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:17:42Z"
    - latency: 2.568527ms
      message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:16:42Z"
    - latency: 2.203576ms
      message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:15:42Z"
    - latency: 2.517042ms
      message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:14:42Z"
    - latency: 2.080149ms
      message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:13:42Z"
    - latency: 2.398868ms
      message: 'network-check-target-ip-10-0-136-247: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:12:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:53:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-55-to-network-check-target-ip-10-0-136-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-55.ec2.internal
      uid: 68a5a2c1-7e7b-4c48-8c74-edeb78dc508b
    resourceVersion: "54237"
    uid: 07705462-c0fa-420b-9ae3-9799dcdbe24f
  spec:
    sourcePod: network-check-source-6f8b768455-bm485
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T13:00:42Z"
      message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.300768ms
      message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:21:42Z"
    - latency: 1.075926ms
      message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:20:42Z"
    - latency: 936.735µs
      message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:19:42Z"
    - latency: 1.317513ms
      message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:18:42Z"
    - latency: 1.04217ms
      message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:17:42Z"
    - latency: 1.556115ms
      message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:16:42Z"
    - latency: 942.864µs
      message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:15:42Z"
    - latency: 905.596µs
      message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:14:42Z"
    - latency: 934.457µs
      message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:13:42Z"
    - latency: 1.084685ms
      message: 'network-check-target-ip-10-0-136-55: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:12:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T12:53:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-55-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-55.ec2.internal
      uid: 68a5a2c1-7e7b-4c48-8c74-edeb78dc508b
    resourceVersion: "55817"
    uid: 148e0727-dc83-4863-930f-300f784566cd
  spec:
    sourcePod: network-check-source-6f8b768455-bm485
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T12:59:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 954.403µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:23:42Z"
    - latency: 1.932884ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:23:42Z"
    - latency: 818.229µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:22:42Z"
    - latency: 2.608917ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:22:42Z"
    - latency: 1.141215ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:21:42Z"
    - latency: 2.076732ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:21:42Z"
    - latency: 987.105µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:20:42Z"
    - latency: 2.042933ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:20:42Z"
    - latency: 977.363µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T13:19:42Z"
    - latency: 1.801559ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T13:19:42Z"
kind: List
metadata:
  resourceVersion: ""