apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T19:18:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 20052836-9d7f-4725-8795-34d878bb81d4
    resourceVersion: "63258"
    uid: 21d1ccd6-a230-44ab-a583-1675f804a366
  spec:
    sourcePod: network-check-source-869dcfcdcd-tt2st
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:25:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.138299ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:00:27Z"
    - latency: 1.583997ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:59:27Z"
    - latency: 1.307075ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:58:27Z"
    - latency: 1.27136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:57:27Z"
    - latency: 1.024669ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:56:27Z"
    - latency: 919.837µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:55:27Z"
    - latency: 1.482602ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:54:27Z"
    - latency: 1.707319ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:53:27Z"
    - latency: 841.544µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:52:27Z"
    - latency: 1.402787ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:51:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T19:18:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 20052836-9d7f-4725-8795-34d878bb81d4
    resourceVersion: "63259"
    uid: e3019e09-8f2a-4f29-b923-241610f4d13c
  spec:
    sourcePod: network-check-source-869dcfcdcd-tt2st
    targetEndpoint: a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:24:27Z"
      message: 'load-balancer-api-external: tcp connection to a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.009478ms
      message: 'load-balancer-api-external: tcp connection to a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:00:27Z"
    - latency: 8.727783ms
      message: 'load-balancer-api-external: resolved host name a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:00:27Z"
    - latency: 5.229868ms
      message: 'load-balancer-api-external: tcp connection to a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:59:27Z"
    - latency: 7.898588ms
      message: 'load-balancer-api-external: resolved host name a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:59:27Z"
    - latency: 4.397087ms
      message: 'load-balancer-api-external: tcp connection to a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:58:27Z"
    - latency: 7.059318ms
      message: 'load-balancer-api-external: resolved host name a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:58:27Z"
    - latency: 6.388779ms
      message: 'load-balancer-api-external: tcp connection to a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:57:27Z"
    - latency: 6.750097ms
      message: 'load-balancer-api-external: resolved host name a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:57:27Z"
    - latency: 4.03463ms
      message: 'load-balancer-api-external: tcp connection to a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:56:27Z"
    - latency: 6.504201ms
      message: 'load-balancer-api-external: resolved host name a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:56:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T19:18:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 20052836-9d7f-4725-8795-34d878bb81d4
    resourceVersion: "63260"
    uid: b257a406-3887-49a7-b0dd-7ae5e1fef131
  spec:
    sourcePod: network-check-source-869dcfcdcd-tt2st
    targetEndpoint: a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:24:27Z"
      message: 'load-balancer-api-internal: tcp connection to a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.988463ms
      message: 'load-balancer-api-internal: tcp connection to a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:00:27Z"
    - latency: 8.752678ms
      message: 'load-balancer-api-internal: resolved host name a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:00:27Z"
    - latency: 5.665736ms
      message: 'load-balancer-api-internal: tcp connection to a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:59:27Z"
    - latency: 7.843581ms
      message: 'load-balancer-api-internal: resolved host name a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:59:27Z"
    - latency: 4.427621ms
      message: 'load-balancer-api-internal: tcp connection to a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:58:27Z"
    - latency: 7.022101ms
      message: 'load-balancer-api-internal: resolved host name a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:58:27Z"
    - latency: 6.381379ms
      message: 'load-balancer-api-internal: tcp connection to a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:57:27Z"
    - latency: 6.690871ms
      message: 'load-balancer-api-internal: resolved host name a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:57:27Z"
    - latency: 3.576144ms
      message: 'load-balancer-api-internal: tcp connection to a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:56:27Z"
    - latency: 6.513983ms
      message: 'load-balancer-api-internal: resolved host name a883d2caf48624532a604971d48162b0-126a3cca2d2f3592.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:56:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T19:18:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-network-check-target-ip-10-0-128-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 20052836-9d7f-4725-8795-34d878bb81d4
    resourceVersion: "63254"
    uid: 49863626-99b7-4c5e-92ed-3c3dea7347b2
  spec:
    sourcePod: network-check-source-869dcfcdcd-tt2st
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:25:27Z"
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 924.82µs
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:00:27Z"
    - latency: 960.557µs
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:59:27Z"
    - latency: 920.277µs
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:58:27Z"
    - latency: 1.111271ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:57:27Z"
    - latency: 1.194419ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:56:27Z"
    - latency: 852.233µs
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:55:27Z"
    - latency: 946.8µs
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:54:27Z"
    - latency: 894.677µs
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:53:27Z"
    - latency: 1.000912ms
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:52:27Z"
    - latency: 964.375µs
      message: 'network-check-target-ip-10-0-128-74: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:51:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T19:18:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-network-check-target-ip-10-0-129-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 20052836-9d7f-4725-8795-34d878bb81d4
    resourceVersion: "63256"
    uid: d494297a-aa76-4dac-87a9-835e4bbf13f9
  spec:
    sourcePod: network-check-source-869dcfcdcd-tt2st
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:25:27Z"
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.498858ms
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:00:27Z"
    - latency: 2.286114ms
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:59:27Z"
    - latency: 2.521357ms
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:58:27Z"
    - latency: 2.157684ms
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:57:27Z"
    - latency: 2.54915ms
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:56:27Z"
    - latency: 2.325956ms
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:55:27Z"
    - latency: 2.596697ms
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:54:27Z"
    - latency: 2.803673ms
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:53:27Z"
    - latency: 2.128944ms
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:52:27Z"
    - latency: 2.243532ms
      message: 'network-check-target-ip-10-0-129-23: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:51:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T19:18:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-network-check-target-ip-10-0-138-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 20052836-9d7f-4725-8795-34d878bb81d4
    resourceVersion: "63255"
    uid: f22c0075-c302-448c-85a2-2e83f77043ff
  spec:
    sourcePod: network-check-source-869dcfcdcd-tt2st
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:25:27Z"
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.368924ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:00:27Z"
    - latency: 2.454071ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:59:27Z"
    - latency: 2.446198ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:58:27Z"
    - latency: 2.146257ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:57:27Z"
    - latency: 2.35924ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:56:27Z"
    - latency: 2.39117ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:55:27Z"
    - latency: 2.473624ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:54:27Z"
    - latency: 2.374769ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:53:27Z"
    - latency: 2.224685ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:52:27Z"
    - latency: 2.252232ms
      message: 'network-check-target-ip-10-0-138-70: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:51:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T19:18:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-74-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-74.ec2.internal
      uid: 20052836-9d7f-4725-8795-34d878bb81d4
    resourceVersion: "63257"
    uid: 6d941fe2-aa21-41e4-880d-4a4af39e830d
  spec:
    sourcePod: network-check-source-869dcfcdcd-tt2st
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T19:24:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 887.607µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T20:00:27Z"
    - latency: 1.69291ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T20:00:27Z"
    - latency: 912.619µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:59:27Z"
    - latency: 2.419395ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:59:27Z"
    - latency: 1.275022ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:58:27Z"
    - latency: 2.024717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:58:27Z"
    - latency: 942.872µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:57:27Z"
    - latency: 1.769735ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:57:27Z"
    - latency: 1.307458ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T19:56:27Z"
    - latency: 1.798888ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T19:56:27Z"
kind: List
metadata:
  resourceVersion: ""