apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T04:46:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-120-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-120.ec2.internal
      uid: c69383d8-d204-4eaa-bb89-bfc60c4ad88c
    resourceVersion: "18783"
    uid: 993e30b5-11a7-4ef6-af3b-72f819a1f897
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ns6tt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T04:53:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 887.315µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:53:45Z"
    - latency: 1.007688ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:52:45Z"
    - latency: 772.434µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:51:45Z"
    - latency: 976.89µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:50:45Z"
    - latency: 1.567051ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:49:45Z"
    - latency: 1.083023ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:48:45Z"
    - latency: 1.138523ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:47:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T04:46:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-120-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-120.ec2.internal
      uid: c69383d8-d204-4eaa-bb89-bfc60c4ad88c
    resourceVersion: "21040"
    uid: 1fd8d3e2-9462-43ee-9b26-42f94558c7aa
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ns6tt
    targetEndpoint: ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T04:52:46Z"
      message: 'load-balancer-api-external: tcp connection to ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.176563ms
      message: 'load-balancer-api-external: tcp connection to ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:58:46Z"
    - latency: 8.207342ms
      message: 'load-balancer-api-external: resolved host name ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T04:58:45Z"
    - latency: 4.942323ms
      message: 'load-balancer-api-external: tcp connection to ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:57:46Z"
    - latency: 9.535571ms
      message: 'load-balancer-api-external: resolved host name ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T04:57:45Z"
    - latency: 4.866665ms
      message: 'load-balancer-api-external: tcp connection to ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:56:46Z"
    - latency: 8.154385ms
      message: 'load-balancer-api-external: resolved host name ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T04:56:45Z"
    - latency: 4.319749ms
      message: 'load-balancer-api-external: tcp connection to ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:55:46Z"
    - latency: 8.707483ms
      message: 'load-balancer-api-external: resolved host name ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T04:55:45Z"
    - latency: 5.477777ms
      message: 'load-balancer-api-external: tcp connection to ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:54:46Z"
    - latency: 8.299473ms
      message: 'load-balancer-api-external: resolved host name ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T04:54:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T04:46:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-120-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-120.ec2.internal
      uid: c69383d8-d204-4eaa-bb89-bfc60c4ad88c
    resourceVersion: "21041"
    uid: 029aa1eb-2cb7-467a-a057-0deee7237147
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ns6tt
    targetEndpoint: ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T04:52:46Z"
      message: 'load-balancer-api-internal: tcp connection to ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.124763ms
      message: 'load-balancer-api-internal: tcp connection to ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:58:46Z"
    - latency: 8.254022ms
      message: 'load-balancer-api-internal: resolved host name ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T04:58:45Z"
    - latency: 5.035727ms
      message: 'load-balancer-api-internal: tcp connection to ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:57:46Z"
    - latency: 9.48435ms
      message: 'load-balancer-api-internal: resolved host name ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T04:57:45Z"
    - latency: 4.679941ms
      message: 'load-balancer-api-internal: tcp connection to ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:56:46Z"
    - latency: 8.053137ms
      message: 'load-balancer-api-internal: resolved host name ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T04:56:45Z"
    - latency: 2.954429ms
      message: 'load-balancer-api-internal: tcp connection to ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:55:46Z"
    - latency: 8.649242ms
      message: 'load-balancer-api-internal: resolved host name ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T04:55:45Z"
    - latency: 5.488877ms
      message: 'load-balancer-api-internal: tcp connection to ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:54:46Z"
    - latency: 8.216053ms
      message: 'load-balancer-api-internal: resolved host name ab64cbe12d5954dbbb26c1f7e429b5df-5f1a42b09e9ce44e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T04:54:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T04:46:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-120-to-network-check-target-ip-10-0-133-150
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-120.ec2.internal
      uid: c69383d8-d204-4eaa-bb89-bfc60c4ad88c
    resourceVersion: "18782"
    uid: 849665e9-3ac9-4214-96e7-5c54a46f9f74
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ns6tt
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T04:53:46Z"
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.990598ms
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:53:45Z"
    - latency: 2.178288ms
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:52:45Z"
    - latency: 1.975898ms
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:51:45Z"
    - latency: 2.519498ms
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:50:45Z"
    - latency: 2.11019ms
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:49:45Z"
    - latency: 2.159079ms
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:48:45Z"
    - latency: 2.474868ms
      message: 'network-check-target-ip-10-0-133-150: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:47:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T04:46:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-120-to-network-check-target-ip-10-0-139-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-120.ec2.internal
      uid: c69383d8-d204-4eaa-bb89-bfc60c4ad88c
    resourceVersion: "18781"
    uid: cf861804-7df4-42ed-9282-fdd8985c1e7f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ns6tt
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T04:53:46Z"
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.882ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:53:45Z"
    - latency: 2.038725ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:52:45Z"
    - latency: 1.86301ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:51:45Z"
    - latency: 2.13828ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:50:45Z"
    - latency: 1.99619ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:49:45Z"
    - latency: 1.846336ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:48:45Z"
    - latency: 2.160772ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:47:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T04:46:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-120-to-network-check-target-ip-10-0-142-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-120.ec2.internal
      uid: c69383d8-d204-4eaa-bb89-bfc60c4ad88c
    resourceVersion: "18780"
    uid: 2497b506-8fa5-4076-8c0c-4363ffedfa72
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ns6tt
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T04:53:46Z"
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 989.968µs
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:53:45Z"
    - latency: 1.145378ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:52:45Z"
    - latency: 1.444817ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:51:45Z"
    - latency: 935.249µs
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:50:45Z"
    - latency: 996.282µs
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:49:45Z"
    - latency: 818.829µs
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:48:45Z"
    - latency: 1.400392ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:47:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T04:46:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-120-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-120.ec2.internal
      uid: c69383d8-d204-4eaa-bb89-bfc60c4ad88c
    resourceVersion: "21039"
    uid: b75d21ec-0057-4877-a570-067a693b4075
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ns6tt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T04:52:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 785.112µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:58:46Z"
    - latency: 1.745234ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T04:58:45Z"
    - latency: 870.917µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:57:46Z"
    - latency: 1.978242ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T04:57:45Z"
    - latency: 1.187457ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:56:46Z"
    - latency: 1.685588ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T04:56:45Z"
    - latency: 820.811µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:55:46Z"
    - latency: 1.763276ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T04:55:45Z"
    - latency: 686.285µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T04:54:45Z"
    - latency: 1.865382ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T04:54:45Z"
kind: List
metadata:
  resourceVersion: ""