apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:15:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-73-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-73.ec2.internal
      uid: cb5e4337-881a-41dc-bf2b-e6ffa5731166
    resourceVersion: "19423"
    uid: 6ec5bc55-0eb9-42d0-9082-86f5ba95d8af
  spec:
    sourcePod: network-check-source-685456655f-z7mhl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T11:22:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 879.553µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:36:13Z"
    - latency: 985.612µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:35:13Z"
    - latency: 1.021636ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:34:13Z"
    - latency: 1.056675ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:33:13Z"
    - latency: 882.91µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:32:13Z"
    - latency: 981.109µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:31:13Z"
    - latency: 931.646µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:30:13Z"
    - latency: 1.18218ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:29:13Z"
    - latency: 1.057192ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:28:13Z"
    - latency: 973.54µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:27:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:15:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-73-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-73.ec2.internal
      uid: cb5e4337-881a-41dc-bf2b-e6ffa5731166
    resourceVersion: "18362"
    uid: 8144da6b-1799-411d-bc8b-4421a4d853c4
  spec:
    sourcePod: network-check-source-685456655f-z7mhl
    targetEndpoint: acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T11:21:13Z"
      message: 'load-balancer-api-external: tcp connection to acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.834603ms
      message: 'load-balancer-api-external: tcp connection to acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:33:13Z"
    - latency: 8.20657ms
      message: 'load-balancer-api-external: resolved host name acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:33:13Z"
    - latency: 3.646268ms
      message: 'load-balancer-api-external: tcp connection to acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:32:13Z"
    - latency: 8.11193ms
      message: 'load-balancer-api-external: resolved host name acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:32:13Z"
    - latency: 5.526401ms
      message: 'load-balancer-api-external: tcp connection to acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:31:13Z"
    - latency: 8.306108ms
      message: 'load-balancer-api-external: resolved host name acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:31:13Z"
    - latency: 5.043141ms
      message: 'load-balancer-api-external: tcp connection to acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:30:13Z"
    - latency: 8.2182ms
      message: 'load-balancer-api-external: resolved host name acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:30:13Z"
    - latency: 3.570495ms
      message: 'load-balancer-api-external: tcp connection to acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:29:13Z"
    - latency: 7.171513ms
      message: 'load-balancer-api-external: resolved host name acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:29:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:15:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-73-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-73.ec2.internal
      uid: cb5e4337-881a-41dc-bf2b-e6ffa5731166
    resourceVersion: "18361"
    uid: 94759b99-c725-42b9-9be6-8abd72bdc6d9
  spec:
    sourcePod: network-check-source-685456655f-z7mhl
    targetEndpoint: acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T11:21:13Z"
      message: 'load-balancer-api-internal: tcp connection to acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.796855ms
      message: 'load-balancer-api-internal: tcp connection to acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:33:13Z"
    - latency: 8.253436ms
      message: 'load-balancer-api-internal: resolved host name acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:33:13Z"
    - latency: 3.673303ms
      message: 'load-balancer-api-internal: tcp connection to acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:32:13Z"
    - latency: 8.141194ms
      message: 'load-balancer-api-internal: resolved host name acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:32:13Z"
    - latency: 5.486776ms
      message: 'load-balancer-api-internal: tcp connection to acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:31:13Z"
    - latency: 8.345843ms
      message: 'load-balancer-api-internal: resolved host name acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:31:13Z"
    - latency: 4.530812ms
      message: 'load-balancer-api-internal: tcp connection to acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:30:13Z"
    - latency: 8.276683ms
      message: 'load-balancer-api-internal: resolved host name acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:30:13Z"
    - latency: 6.623518ms
      message: 'load-balancer-api-internal: tcp connection to acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:29:13Z"
    - latency: 7.224547ms
      message: 'load-balancer-api-internal: resolved host name acb8b38b863d1421b8403b1e1c71653d-b4c203c1e767fc27.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:29:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:15:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-73-to-network-check-target-ip-10-0-131-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-73.ec2.internal
      uid: cb5e4337-881a-41dc-bf2b-e6ffa5731166
    resourceVersion: "19422"
    uid: aa376c28-1c6a-42b6-8878-c60067c28766
  spec:
    sourcePod: network-check-source-685456655f-z7mhl
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T11:22:13Z"
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.640648ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:36:13Z"
    - latency: 2.277925ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:35:13Z"
    - latency: 2.399929ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:34:13Z"
    - latency: 2.184602ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:33:13Z"
    - latency: 2.088587ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:32:13Z"
    - latency: 2.244773ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:31:13Z"
    - latency: 2.231145ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:30:13Z"
    - latency: 2.961116ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:29:13Z"
    - latency: 2.346169ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:28:13Z"
    - latency: 1.944528ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:27:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:15:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-73-to-network-check-target-ip-10-0-134-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-73.ec2.internal
      uid: cb5e4337-881a-41dc-bf2b-e6ffa5731166
    resourceVersion: "19420"
    uid: b360b55f-d4bb-4466-a315-23638d331ad9
  spec:
    sourcePod: network-check-source-685456655f-z7mhl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T11:22:13Z"
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 823.223µs
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:36:13Z"
    - latency: 866.202µs
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:35:13Z"
    - latency: 849.961µs
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:34:13Z"
    - latency: 835.316µs
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:33:13Z"
    - latency: 932.276µs
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:32:13Z"
    - latency: 925.475µs
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:31:13Z"
    - latency: 1.49554ms
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:30:13Z"
    - latency: 1.152273ms
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:29:13Z"
    - latency: 1.50304ms
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:28:13Z"
    - latency: 1.482621ms
      message: 'network-check-target-ip-10-0-134-73: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:27:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:15:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-73-to-network-check-target-ip-10-0-138-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-73.ec2.internal
      uid: cb5e4337-881a-41dc-bf2b-e6ffa5731166
    resourceVersion: "19421"
    uid: e61cbb49-f351-43c3-a544-16b5803b8fab
  spec:
    sourcePod: network-check-source-685456655f-z7mhl
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T11:22:13Z"
      message: 'network-check-target-ip-10-0-138-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.086649ms
      message: 'network-check-target-ip-10-0-138-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:36:13Z"
    - latency: 2.043929ms
      message: 'network-check-target-ip-10-0-138-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:35:13Z"
    - latency: 2.28241ms
      message: 'network-check-target-ip-10-0-138-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:34:13Z"
    - latency: 2.235837ms
      message: 'network-check-target-ip-10-0-138-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:33:13Z"
    - latency: 2.114714ms
      message: 'network-check-target-ip-10-0-138-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:32:13Z"
    - latency: 2.74433ms
      message: 'network-check-target-ip-10-0-138-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:31:13Z"
    - latency: 2.269558ms
      message: 'network-check-target-ip-10-0-138-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:30:13Z"
    - latency: 2.392673ms
      message: 'network-check-target-ip-10-0-138-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:29:13Z"
    - latency: 2.417195ms
      message: 'network-check-target-ip-10-0-138-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:28:13Z"
    - latency: 2.020909ms
      message: 'network-check-target-ip-10-0-138-174: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:27:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T11:15:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-73-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-73.ec2.internal
      uid: cb5e4337-881a-41dc-bf2b-e6ffa5731166
    resourceVersion: "18360"
    uid: 71acdfa2-cf5e-4c56-8de1-bd951593bc52
  spec:
    sourcePod: network-check-source-685456655f-z7mhl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T11:21:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 813.155µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:33:13Z"
    - latency: 1.72631ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:33:13Z"
    - latency: 1.114523ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:32:13Z"
    - latency: 1.678011ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:32:13Z"
    - latency: 1.111963ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:31:13Z"
    - latency: 1.763818ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:31:13Z"
    - latency: 792.23µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:30:13Z"
    - latency: 1.706226ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:30:13Z"
    - latency: 844.405µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T11:29:13Z"
    - latency: 1.600682ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T11:29:13Z"
kind: List
metadata:
  resourceVersion: ""