apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:22:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: c742e2f1-901b-4d6b-9580-0f842fc4ed3d
    resourceVersion: "54797"
    uid: 61905767-e06c-438d-993f-71352f63241d
  spec:
    sourcePod: network-check-source-989f8b8dc-cv75c
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:29:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 854.696µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:57:51Z"
    - latency: 827.78µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:56:51Z"
    - latency: 822.534µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:55:51Z"
    - latency: 964.499µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:54:51Z"
    - latency: 1.10094ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:53:51Z"
    - latency: 1.375754ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:52:51Z"
    - latency: 868.942µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:51:51Z"
    - latency: 931.076µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:50:51Z"
    - latency: 812.432µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:49:51Z"
    - latency: 804.846µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:48:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:22:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: c742e2f1-901b-4d6b-9580-0f842fc4ed3d
    resourceVersion: "55734"
    uid: 4d68d0e4-d6e3-4891-9847-1cc9ef95d044
  spec:
    sourcePod: network-check-source-989f8b8dc-cv75c
    targetEndpoint: a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:28:51Z"
      message: 'load-balancer-api-external: tcp connection to a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.476055ms
      message: 'load-balancer-api-external: tcp connection to a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:58:51Z"
    - latency: 6.758611ms
      message: 'load-balancer-api-external: resolved host name a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:58:51Z"
    - latency: 5.339888ms
      message: 'load-balancer-api-external: tcp connection to a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:57:51Z"
    - latency: 6.985573ms
      message: 'load-balancer-api-external: resolved host name a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:57:51Z"
    - latency: 4.85585ms
      message: 'load-balancer-api-external: tcp connection to a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:56:51Z"
    - latency: 8.020082ms
      message: 'load-balancer-api-external: resolved host name a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:56:51Z"
    - latency: 4.236097ms
      message: 'load-balancer-api-external: tcp connection to a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:55:51Z"
    - latency: 6.6072ms
      message: 'load-balancer-api-external: resolved host name a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:55:51Z"
    - latency: 4.048172ms
      message: 'load-balancer-api-external: tcp connection to a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:54:51Z"
    - latency: 6.565692ms
      message: 'load-balancer-api-external: resolved host name a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:54:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:22:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: c742e2f1-901b-4d6b-9580-0f842fc4ed3d
    resourceVersion: "55733"
    uid: 0454578c-a2bf-4988-9836-bdb41cd94ef0
  spec:
    sourcePod: network-check-source-989f8b8dc-cv75c
    targetEndpoint: a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:28:51Z"
      message: 'load-balancer-api-internal: tcp connection to a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.512552ms
      message: 'load-balancer-api-internal: tcp connection to a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:58:51Z"
    - latency: 6.725426ms
      message: 'load-balancer-api-internal: resolved host name a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:58:51Z"
    - latency: 5.345737ms
      message: 'load-balancer-api-internal: tcp connection to a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:57:51Z"
    - latency: 7.051707ms
      message: 'load-balancer-api-internal: resolved host name a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:57:51Z"
    - latency: 5.375051ms
      message: 'load-balancer-api-internal: tcp connection to a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:56:51Z"
    - latency: 7.967737ms
      message: 'load-balancer-api-internal: resolved host name a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:56:51Z"
    - latency: 4.474419ms
      message: 'load-balancer-api-internal: tcp connection to a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:55:51Z"
    - latency: 6.6365ms
      message: 'load-balancer-api-internal: resolved host name a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:55:51Z"
    - latency: 4.875384ms
      message: 'load-balancer-api-internal: tcp connection to a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:54:51Z"
    - latency: 6.49756ms
      message: 'load-balancer-api-internal: resolved host name a5527b82726ce4e9d84156993fdcd1bb-a6c75966ad253796.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:54:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:22:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-network-check-target-ip-10-0-129-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: c742e2f1-901b-4d6b-9580-0f842fc4ed3d
    resourceVersion: "54796"
    uid: cddb61b8-c8b6-4759-8b9c-bf93c880c910
  spec:
    sourcePod: network-check-source-989f8b8dc-cv75c
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:29:51Z"
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.076657ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:57:51Z"
    - latency: 2.165308ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:56:51Z"
    - latency: 2.237519ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:55:51Z"
    - latency: 1.937589ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:54:51Z"
    - latency: 1.952813ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:53:51Z"
    - latency: 2.6614ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:52:51Z"
    - latency: 2.109653ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:51:51Z"
    - latency: 2.074479ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:50:51Z"
    - latency: 1.995482ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:49:51Z"
    - latency: 2.177377ms
      message: 'network-check-target-ip-10-0-129-174: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:48:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:22:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-network-check-target-ip-10-0-135-243
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: c742e2f1-901b-4d6b-9580-0f842fc4ed3d
    resourceVersion: "54794"
    uid: de14c25d-37af-4e5e-bd16-3b16373c741a
  spec:
    sourcePod: network-check-source-989f8b8dc-cv75c
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:29:51Z"
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.960007ms
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:57:51Z"
    - latency: 2.047125ms
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:56:51Z"
    - latency: 1.941596ms
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:55:51Z"
    - latency: 1.931358ms
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:54:51Z"
    - latency: 1.505366ms
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:53:51Z"
    - latency: 2.0145ms
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:52:51Z"
    - latency: 2.001344ms
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:51:51Z"
    - latency: 1.875175ms
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:50:51Z"
    - latency: 1.88203ms
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:49:51Z"
    - latency: 1.700788ms
      message: 'network-check-target-ip-10-0-135-243: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:48:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:22:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-network-check-target-ip-10-0-136-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: c742e2f1-901b-4d6b-9580-0f842fc4ed3d
    resourceVersion: "54795"
    uid: a93e2f61-b8c5-40f2-8354-51a08b078fb0
  spec:
    sourcePod: network-check-source-989f8b8dc-cv75c
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:29:51Z"
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 722.37µs
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:57:51Z"
    - latency: 732.288µs
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:56:51Z"
    - latency: 933.467µs
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:55:51Z"
    - latency: 970.732µs
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:54:51Z"
    - latency: 1.130325ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:53:51Z"
    - latency: 988.987µs
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:52:51Z"
    - latency: 942.653µs
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:51:51Z"
    - latency: 798.684µs
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:50:51Z"
    - latency: 1.259464ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:49:51Z"
    - latency: 739.239µs
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:48:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:22:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: c742e2f1-901b-4d6b-9580-0f842fc4ed3d
    resourceVersion: "55732"
    uid: cbf6a012-8a48-4518-a06d-11bd373abb45
  spec:
    sourcePod: network-check-source-989f8b8dc-cv75c
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:28:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.093076ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:58:51Z"
    - latency: 1.538247ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:58:51Z"
    - latency: 917.62µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:57:51Z"
    - latency: 1.539561ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:57:51Z"
    - latency: 1.003285ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:56:51Z"
    - latency: 1.661359ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:56:51Z"
    - latency: 978.781µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:55:51Z"
    - latency: 1.771515ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:55:51Z"
    - latency: 1.131871ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:54:51Z"
    - latency: 1.549409ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T16:54:51Z"
kind: List
metadata:
  resourceVersion: ""