apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T23:15:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-8-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-8.ec2.internal
      uid: 9e263630-bb34-4081-ab63-61cbe8039293
    resourceVersion: "22312"
    uid: c32cc72d-36c0-4faa-b9bc-a7f9371e0f89
  spec:
    sourcePod: network-check-source-6f78d59f99-s7fcp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T23:22:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.220223ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:22:08Z"
    - latency: 997.975µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:21:08Z"
    - latency: 1.269188ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:20:08Z"
    - latency: 1.100021ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:19:08Z"
    - latency: 978.36µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:18:08Z"
    - latency: 1.327397ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:17:08Z"
    - latency: 1.045918ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:16:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T23:15:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-8-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-8.ec2.internal
      uid: 9e263630-bb34-4081-ab63-61cbe8039293
    resourceVersion: "35249"
    uid: 2a7a3f6e-011e-4310-afe8-05bb462cd675
  spec:
    sourcePod: network-check-source-6f78d59f99-s7fcp
    targetEndpoint: a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T23:21:08Z"
      message: 'load-balancer-api-external: tcp connection to a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 19.221545ms
      message: 'load-balancer-api-external: tcp connection to a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:27:08Z"
    - latency: 7.235585ms
      message: 'load-balancer-api-external: resolved host name a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:27:08Z"
    - latency: 17.577383ms
      message: 'load-balancer-api-external: tcp connection to a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:26:08Z"
    - latency: 6.944444ms
      message: 'load-balancer-api-external: resolved host name a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:26:08Z"
    - latency: 15.785417ms
      message: 'load-balancer-api-external: tcp connection to a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:25:08Z"
    - latency: 7.628857ms
      message: 'load-balancer-api-external: resolved host name a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:25:08Z"
    - latency: 16.762917ms
      message: 'load-balancer-api-external: tcp connection to a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:24:08Z"
    - latency: 9.044888ms
      message: 'load-balancer-api-external: resolved host name a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:24:08Z"
    - latency: 17.408167ms
      message: 'load-balancer-api-external: tcp connection to a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:23:08Z"
    - latency: 7.154195ms
      message: 'load-balancer-api-external: resolved host name a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:23:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T23:15:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-8-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-8.ec2.internal
      uid: 9e263630-bb34-4081-ab63-61cbe8039293
    resourceVersion: "35251"
    uid: df2a5805-56a6-419e-ab2e-d2e561f5af0e
  spec:
    sourcePod: network-check-source-6f78d59f99-s7fcp
    targetEndpoint: a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T23:21:08Z"
      message: 'load-balancer-api-internal: tcp connection to a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 20.018216ms
      message: 'load-balancer-api-internal: tcp connection to a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:27:08Z"
    - latency: 7.344425ms
      message: 'load-balancer-api-internal: resolved host name a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:27:08Z"
    - latency: 17.557711ms
      message: 'load-balancer-api-internal: tcp connection to a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:26:08Z"
    - latency: 6.901407ms
      message: 'load-balancer-api-internal: resolved host name a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:26:08Z"
    - latency: 15.250947ms
      message: 'load-balancer-api-internal: tcp connection to a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:25:08Z"
    - latency: 7.720432ms
      message: 'load-balancer-api-internal: resolved host name a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:25:08Z"
    - latency: 18.892486ms
      message: 'load-balancer-api-internal: tcp connection to a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:24:08Z"
    - latency: 9.145231ms
      message: 'load-balancer-api-internal: resolved host name a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:24:08Z"
    - latency: 17.577514ms
      message: 'load-balancer-api-internal: tcp connection to a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:23:08Z"
    - latency: 7.613331ms
      message: 'load-balancer-api-internal: resolved host name a09e0534202e04a228672c33fd62a2ef-1479d0e8f2bb4893.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:23:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T23:15:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-8-to-network-check-target-ip-10-0-134-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-8.ec2.internal
      uid: 9e263630-bb34-4081-ab63-61cbe8039293
    resourceVersion: "22309"
    uid: 1fc4f9ac-22af-41fe-9d15-308d1e8d50ee
  spec:
    sourcePod: network-check-source-6f78d59f99-s7fcp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T23:22:08Z"
      message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.469729ms
      message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:22:08Z"
    - latency: 933.137µs
      message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:21:08Z"
    - latency: 1.002914ms
      message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:20:08Z"
    - latency: 1.080335ms
      message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:19:08Z"
    - latency: 844.538µs
      message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:18:08Z"
    - latency: 1.480197ms
      message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:17:08Z"
    - latency: 1.282987ms
      message: 'network-check-target-ip-10-0-134-8: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:16:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T23:15:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-8-to-network-check-target-ip-10-0-137-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-8.ec2.internal
      uid: 9e263630-bb34-4081-ab63-61cbe8039293
    resourceVersion: "22311"
    uid: 58d8b9d5-d3d7-4941-9f02-0cb821ea4608
  spec:
    sourcePod: network-check-source-6f78d59f99-s7fcp
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T23:22:08Z"
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.796376ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:22:08Z"
    - latency: 2.945328ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:21:08Z"
    - latency: 11.035483ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:20:08Z"
    - latency: 2.579629ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:19:08Z"
    - latency: 2.045269ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:18:08Z"
    - latency: 2.262367ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:17:08Z"
    - latency: 2.404617ms
      message: 'network-check-target-ip-10-0-137-132: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:16:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T23:15:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-8-to-network-check-target-ip-10-0-143-10
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-8.ec2.internal
      uid: 9e263630-bb34-4081-ab63-61cbe8039293
    resourceVersion: "22310"
    uid: 9fd2f3f7-1857-42ef-8677-c89891d2bc13
  spec:
    sourcePod: network-check-source-6f78d59f99-s7fcp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T23:22:08Z"
      message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.492501ms
      message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:22:08Z"
    - latency: 2.52524ms
      message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:21:08Z"
    - latency: 11.016875ms
      message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:20:08Z"
    - latency: 2.461661ms
      message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:19:08Z"
    - latency: 2.875198ms
      message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:18:08Z"
    - latency: 2.286844ms
      message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:17:08Z"
    - latency: 2.233908ms
      message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:16:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T23:15:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-8-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-8.ec2.internal
      uid: 9e263630-bb34-4081-ab63-61cbe8039293
    resourceVersion: "35245"
    uid: 549b8e8f-bc78-4776-8636-ec8f5e9568a1
  spec:
    sourcePod: network-check-source-6f78d59f99-s7fcp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T23:21:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.023611ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:27:08Z"
    - latency: 2.374484ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:27:08Z"
    - latency: 1.479797ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:26:08Z"
    - latency: 2.162202ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:26:08Z"
    - latency: 1.175249ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:25:08Z"
    - latency: 1.820777ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:25:08Z"
    - latency: 970.644µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:24:08Z"
    - latency: 2.242734ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:24:08Z"
    - latency: 937.651µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:23:08Z"
    - latency: 2.087686ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:23:08Z"
kind: List
metadata:
  resourceVersion: ""