apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:54:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-204-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-204.ec2.internal
      uid: 33ad12dd-4ca0-407a-bdac-08b012ac8ff2
    resourceVersion: "69156"
    uid: e6e7ccff-3745-4d38-9564-0637f752aad4
  spec:
    sourcePod: network-check-source-7d88cb55d8-gwjgm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:01: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.148902ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:43:39Z"
    - latency: 1.121098ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:42:39Z"
    - latency: 872.029µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:41:39Z"
    - latency: 1.209636ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:40:39Z"
    - latency: 1.010488ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:39:39Z"
    - latency: 1.317432ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:38:39Z"
    - latency: 1.245974ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:37:39Z"
    - latency: 1.341364ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:36:39Z"
    - latency: 1.247973ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:35:39Z"
    - latency: 963.339µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:34:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:54:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-204-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-204.ec2.internal
      uid: 33ad12dd-4ca0-407a-bdac-08b012ac8ff2
    resourceVersion: "74336"
    uid: c7abac50-9a22-4c1f-b4fb-1f1297e7ac42
  spec:
    sourcePod: network-check-source-7d88cb55d8-gwjgm
    targetEndpoint: a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:00:39Z"
      message: 'load-balancer-api-external: tcp connection to a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.163677ms
      message: 'load-balancer-api-external: tcp connection to a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:48:39Z"
    - latency: 7.988763ms
      message: 'load-balancer-api-external: resolved host name a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:48:39Z"
    - latency: 4.011136ms
      message: 'load-balancer-api-external: tcp connection to a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:47:39Z"
    - latency: 8.348973ms
      message: 'load-balancer-api-external: resolved host name a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:47:39Z"
    - latency: 4.116465ms
      message: 'load-balancer-api-external: tcp connection to a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:46:39Z"
    - latency: 12.121996ms
      message: 'load-balancer-api-external: resolved host name a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:46:39Z"
    - latency: 4.907946ms
      message: 'load-balancer-api-external: tcp connection to a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:45:39Z"
    - latency: 7.652747ms
      message: 'load-balancer-api-external: resolved host name a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:45:39Z"
    - latency: 4.46205ms
      message: 'load-balancer-api-external: tcp connection to a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:44:39Z"
    - latency: 9.362882ms
      message: 'load-balancer-api-external: resolved host name a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:44:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:54:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-204-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-204.ec2.internal
      uid: 33ad12dd-4ca0-407a-bdac-08b012ac8ff2
    resourceVersion: "74335"
    uid: 85af90cd-66ab-4840-84dc-2715703ddd5d
  spec:
    sourcePod: network-check-source-7d88cb55d8-gwjgm
    targetEndpoint: a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:00:39Z"
      message: 'load-balancer-api-internal: tcp connection to a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.148937ms
      message: 'load-balancer-api-internal: tcp connection to a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:48:39Z"
    - latency: 7.866716ms
      message: 'load-balancer-api-internal: resolved host name a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:48:39Z"
    - latency: 4.884045ms
      message: 'load-balancer-api-internal: tcp connection to a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:47:39Z"
    - latency: 8.280735ms
      message: 'load-balancer-api-internal: resolved host name a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:47:39Z"
    - latency: 4.182408ms
      message: 'load-balancer-api-internal: tcp connection to a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:46:39Z"
    - latency: 11.897611ms
      message: 'load-balancer-api-internal: resolved host name a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:46:39Z"
    - latency: 3.937389ms
      message: 'load-balancer-api-internal: tcp connection to a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:45:39Z"
    - latency: 7.681521ms
      message: 'load-balancer-api-internal: resolved host name a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:45:39Z"
    - latency: 5.624125ms
      message: 'load-balancer-api-internal: tcp connection to a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:44:39Z"
    - latency: 9.203318ms
      message: 'load-balancer-api-internal: resolved host name a22dcfb9f480f4429af687f144c00f93-c2f6f638ffdd4fb8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:44:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:54:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-204-to-network-check-target-ip-10-0-132-196
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-204.ec2.internal
      uid: 33ad12dd-4ca0-407a-bdac-08b012ac8ff2
    resourceVersion: "69154"
    uid: e9288cf4-e40d-43c7-8c1f-64093c8976a4
  spec:
    sourcePod: network-check-source-7d88cb55d8-gwjgm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:01:39Z"
      message: 'network-check-target-ip-10-0-132-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.032302ms
      message: 'network-check-target-ip-10-0-132-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:43:39Z"
    - latency: 2.365184ms
      message: 'network-check-target-ip-10-0-132-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:42:39Z"
    - latency: 2.159464ms
      message: 'network-check-target-ip-10-0-132-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:41:39Z"
    - latency: 1.982343ms
      message: 'network-check-target-ip-10-0-132-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:40:39Z"
    - latency: 2.12061ms
      message: 'network-check-target-ip-10-0-132-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:39:39Z"
    - latency: 2.160873ms
      message: 'network-check-target-ip-10-0-132-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:38:39Z"
    - latency: 1.807889ms
      message: 'network-check-target-ip-10-0-132-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:37:39Z"
    - latency: 2.198004ms
      message: 'network-check-target-ip-10-0-132-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:36:39Z"
    - latency: 2.147498ms
      message: 'network-check-target-ip-10-0-132-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:35:39Z"
    - latency: 1.753087ms
      message: 'network-check-target-ip-10-0-132-196: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:34:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:54:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-204-to-network-check-target-ip-10-0-133-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-204.ec2.internal
      uid: 33ad12dd-4ca0-407a-bdac-08b012ac8ff2
    resourceVersion: "69155"
    uid: e03176a5-e7f9-4d46-b75c-ea3c56b87094
  spec:
    sourcePod: network-check-source-7d88cb55d8-gwjgm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:01:39Z"
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.459431ms
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:43:39Z"
    - latency: 2.621419ms
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:42:39Z"
    - latency: 2.502375ms
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:41:39Z"
    - latency: 2.355759ms
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:40:39Z"
    - latency: 2.520242ms
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:39:39Z"
    - latency: 2.406484ms
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:38:39Z"
    - latency: 2.445432ms
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:37:39Z"
    - latency: 2.51446ms
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:36:39Z"
    - latency: 2.488445ms
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:35:39Z"
    - latency: 2.592817ms
      message: 'network-check-target-ip-10-0-133-173: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:34:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:54:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-204-to-network-check-target-ip-10-0-136-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-204.ec2.internal
      uid: 33ad12dd-4ca0-407a-bdac-08b012ac8ff2
    resourceVersion: "69153"
    uid: b65c9825-2b67-43d2-b351-e70f10f7f40e
  spec:
    sourcePod: network-check-source-7d88cb55d8-gwjgm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:01:39Z"
      message: 'network-check-target-ip-10-0-136-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.421415ms
      message: 'network-check-target-ip-10-0-136-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:43:39Z"
    - latency: 1.056342ms
      message: 'network-check-target-ip-10-0-136-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:42:39Z"
    - latency: 1.355979ms
      message: 'network-check-target-ip-10-0-136-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:41:39Z"
    - latency: 1.668091ms
      message: 'network-check-target-ip-10-0-136-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:40:39Z"
    - latency: 1.257025ms
      message: 'network-check-target-ip-10-0-136-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:39:39Z"
    - latency: 1.13239ms
      message: 'network-check-target-ip-10-0-136-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:38:39Z"
    - latency: 1.067579ms
      message: 'network-check-target-ip-10-0-136-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:37:39Z"
    - latency: 1.55195ms
      message: 'network-check-target-ip-10-0-136-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:36:39Z"
    - latency: 1.216513ms
      message: 'network-check-target-ip-10-0-136-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:35:39Z"
    - latency: 1.821118ms
      message: 'network-check-target-ip-10-0-136-204: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:34:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:54:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-204-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-204.ec2.internal
      uid: 33ad12dd-4ca0-407a-bdac-08b012ac8ff2
    resourceVersion: "74334"
    uid: 2dacfc78-6555-4bef-a093-92ff401dc14d
  spec:
    sourcePod: network-check-source-7d88cb55d8-gwjgm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T13:00:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.499µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:48:39Z"
    - latency: 2.378168ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:48:39Z"
    - latency: 894.833µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:47:39Z"
    - latency: 2.200358ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:47:39Z"
    - latency: 3.234062ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:46:39Z"
    - latency: 5.40962ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:46:39Z"
    - latency: 1.154252ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:45:39Z"
    - latency: 2.064446ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:45:39Z"
    - latency: 1.003451ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T13:44:39Z"
    - latency: 1.892296ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T13:44:39Z"
kind: List
metadata:
  resourceVersion: ""