apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:04:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-66-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-66.ec2.internal
      uid: d4ded396-5f1b-4588-b2c0-9a72e16e711a
    resourceVersion: "15391"
    uid: 5dc1b054-4804-4de5-a16d-3621d0827a70
  spec:
    sourcePod: network-check-source-dbd9cf844-lkgzv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T22:11:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.019521ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:11:28Z"
    - latency: 1.063713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:10:28Z"
    - latency: 977.063µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:09:28Z"
    - latency: 1.019896ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:08:28Z"
    - latency: 915.866µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:07:28Z"
    - latency: 935.448µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:06:28Z"
    - latency: 1.098019ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:05:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:04:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-66-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-66.ec2.internal
      uid: d4ded396-5f1b-4588-b2c0-9a72e16e711a
    resourceVersion: "15017"
    uid: f24171ff-6cb8-462b-b70e-823e0fad53d7
  spec:
    sourcePod: network-check-source-dbd9cf844-lkgzv
    targetEndpoint: ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T22:10:28Z"
      message: 'load-balancer-api-external: tcp connection to ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.066408ms
      message: 'load-balancer-api-external: tcp connection to ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:10:28Z"
    - latency: 8.595589ms
      message: 'load-balancer-api-external: resolved host name ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:10:28Z"
    - latency: 4.10934ms
      message: 'load-balancer-api-external: tcp connection to ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:09:28Z"
    - latency: 9.488086ms
      message: 'load-balancer-api-external: resolved host name ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:09:28Z"
    - latency: 4.179183ms
      message: 'load-balancer-api-external: tcp connection to ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:08:28Z"
    - latency: 8.335291ms
      message: 'load-balancer-api-external: resolved host name ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:08:28Z"
    - latency: 4.946882ms
      message: 'load-balancer-api-external: tcp connection to ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:07:28Z"
    - latency: 8.599746ms
      message: 'load-balancer-api-external: resolved host name ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:07:28Z"
    - latency: 4.018349ms
      message: 'load-balancer-api-external: tcp connection to ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:06:28Z"
    - latency: 7.931375ms
      message: 'load-balancer-api-external: resolved host name ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:06:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:04:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-66-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-66.ec2.internal
      uid: d4ded396-5f1b-4588-b2c0-9a72e16e711a
    resourceVersion: "15018"
    uid: 27c245f9-3253-4e1d-9b91-e347958d2259
  spec:
    sourcePod: network-check-source-dbd9cf844-lkgzv
    targetEndpoint: ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T22:10:28Z"
      message: 'load-balancer-api-internal: tcp connection to ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.853185ms
      message: 'load-balancer-api-internal: tcp connection to ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:10:28Z"
    - latency: 8.660537ms
      message: 'load-balancer-api-internal: resolved host name ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:10:28Z"
    - latency: 4.144017ms
      message: 'load-balancer-api-internal: tcp connection to ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:09:28Z"
    - latency: 9.392132ms
      message: 'load-balancer-api-internal: resolved host name ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:09:28Z"
    - latency: 4.161734ms
      message: 'load-balancer-api-internal: tcp connection to ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:08:28Z"
    - latency: 8.397148ms
      message: 'load-balancer-api-internal: resolved host name ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:08:28Z"
    - latency: 4.945764ms
      message: 'load-balancer-api-internal: tcp connection to ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:07:28Z"
    - latency: 8.678135ms
      message: 'load-balancer-api-internal: resolved host name ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:07:28Z"
    - latency: 4.035321ms
      message: 'load-balancer-api-internal: tcp connection to ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:06:28Z"
    - latency: 7.847651ms
      message: 'load-balancer-api-internal: resolved host name ab2a999b74f014533a03bfa5625418ba-fc1741f5165f6bad.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:06:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:04:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-66-to-network-check-target-ip-10-0-128-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-66.ec2.internal
      uid: d4ded396-5f1b-4588-b2c0-9a72e16e711a
    resourceVersion: "15389"
    uid: b6b2e8ee-6cdd-4e82-82bd-ef100f67f1e1
  spec:
    sourcePod: network-check-source-dbd9cf844-lkgzv
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T22:11:28Z"
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.52786ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:11:28Z"
    - latency: 2.252192ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:10:28Z"
    - latency: 2.330997ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:09:28Z"
    - latency: 2.277435ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:08:28Z"
    - latency: 2.491813ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:07:28Z"
    - latency: 2.2653ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:06:28Z"
    - latency: 2.517081ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:05:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:04:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-66-to-network-check-target-ip-10-0-130-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-66.ec2.internal
      uid: d4ded396-5f1b-4588-b2c0-9a72e16e711a
    resourceVersion: "15390"
    uid: c5ac6135-c9d6-4ad2-948e-1a59464d06d2
  spec:
    sourcePod: network-check-source-dbd9cf844-lkgzv
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T22:11:28Z"
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.241648ms
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:11:28Z"
    - latency: 2.556765ms
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:10:28Z"
    - latency: 2.288263ms
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:09:28Z"
    - latency: 11.133104ms
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:08:28Z"
    - latency: 2.577392ms
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:07:28Z"
    - latency: 2.339379ms
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:06:28Z"
    - latency: 2.682167ms
      message: 'network-check-target-ip-10-0-130-65: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:05:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:04:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-66-to-network-check-target-ip-10-0-140-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-66.ec2.internal
      uid: d4ded396-5f1b-4588-b2c0-9a72e16e711a
    resourceVersion: "15388"
    uid: 7373472f-2eec-4748-bb2f-5f226c87f97d
  spec:
    sourcePod: network-check-source-dbd9cf844-lkgzv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T22:11:28Z"
      message: 'network-check-target-ip-10-0-140-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 838.962µs
      message: 'network-check-target-ip-10-0-140-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:11:28Z"
    - latency: 1.16461ms
      message: 'network-check-target-ip-10-0-140-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:10:28Z"
    - latency: 919.194µs
      message: 'network-check-target-ip-10-0-140-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:09:28Z"
    - latency: 913.322µs
      message: 'network-check-target-ip-10-0-140-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:08:28Z"
    - latency: 856.653µs
      message: 'network-check-target-ip-10-0-140-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:07:28Z"
    - latency: 1.277721ms
      message: 'network-check-target-ip-10-0-140-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:06:28Z"
    - latency: 1.626552ms
      message: 'network-check-target-ip-10-0-140-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:05:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T22:04:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-66-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-66.ec2.internal
      uid: d4ded396-5f1b-4588-b2c0-9a72e16e711a
    resourceVersion: "15016"
    uid: 9d566ec4-8c9b-49e9-995c-e7a68ed43f49
  spec:
    sourcePod: network-check-source-dbd9cf844-lkgzv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T22:10:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.243753ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:10:28Z"
    - latency: 1.931281ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:10:28Z"
    - latency: 1.050547ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:09:28Z"
    - latency: 2.076442ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:09:28Z"
    - latency: 770.216µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:08:28Z"
    - latency: 1.624159ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:08:28Z"
    - latency: 1.00923ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:07:28Z"
    - latency: 1.706793ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:07:28Z"
    - latency: 1.214112ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T22:06:28Z"
    - latency: 1.690475ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T22:06:28Z"
kind: List
metadata:
  resourceVersion: ""