apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:54:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-216-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-216.ec2.internal
      uid: bd0108ee-0399-408b-bfbd-0b90b8faba97
    resourceVersion: "20363"
    uid: 4cca4560-6d29-4ae0-ab9d-4c83e7df6f8d
  spec:
    sourcePod: network-check-source-6f78d59f99-dl2m4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T15:01:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.004445ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:01:49Z"
    - latency: 1.142711ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:00:49Z"
    - latency: 760.561µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:59:49Z"
    - latency: 991.073µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:58:49Z"
    - latency: 863.734µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:57:49Z"
    - latency: 855.984µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:56:49Z"
    - latency: 1.146677ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:55:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:54:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-216-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-216.ec2.internal
      uid: bd0108ee-0399-408b-bfbd-0b90b8faba97
    resourceVersion: "18780"
    uid: 2d21a353-7a6e-461c-839d-99517fcbb85f
  spec:
    sourcePod: network-check-source-6f78d59f99-dl2m4
    targetEndpoint: a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T15:00:50Z"
      message: 'load-balancer-api-external: tcp connection to a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.301168ms
      message: 'load-balancer-api-external: tcp connection to a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:00:50Z"
    - latency: 22.339848ms
      message: 'load-balancer-api-external: resolved host name a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:00:49Z"
    - latency: 16.541856ms
      message: 'load-balancer-api-external: tcp connection to a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:59:49Z"
    - latency: 7.289325ms
      message: 'load-balancer-api-external: resolved host name a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:59:49Z"
    - latency: 17.450696ms
      message: 'load-balancer-api-external: tcp connection to a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:58:49Z"
    - latency: 10.28072ms
      message: 'load-balancer-api-external: resolved host name a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:58:49Z"
    - latency: 15.289351ms
      message: 'load-balancer-api-external: tcp connection to a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:57:49Z"
    - latency: 7.870646ms
      message: 'load-balancer-api-external: resolved host name a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:57:49Z"
    - latency: 18.77496ms
      message: 'load-balancer-api-external: tcp connection to a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:56:49Z"
    - latency: 7.688146ms
      message: 'load-balancer-api-external: resolved host name a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:56:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:54:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-216-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-216.ec2.internal
      uid: bd0108ee-0399-408b-bfbd-0b90b8faba97
    resourceVersion: "18781"
    uid: 31d20615-2ab0-4f93-97c4-e562194c8538
  spec:
    sourcePod: network-check-source-6f78d59f99-dl2m4
    targetEndpoint: a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T15:00:50Z"
      message: 'load-balancer-api-internal: tcp connection to a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.423166ms
      message: 'load-balancer-api-internal: tcp connection to a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:00:50Z"
    - latency: 22.262407ms
      message: 'load-balancer-api-internal: resolved host name a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:00:49Z"
    - latency: 17.188214ms
      message: 'load-balancer-api-internal: tcp connection to a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:59:49Z"
    - latency: 7.223708ms
      message: 'load-balancer-api-internal: resolved host name a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:59:49Z"
    - latency: 17.671666ms
      message: 'load-balancer-api-internal: tcp connection to a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:58:49Z"
    - latency: 10.368965ms
      message: 'load-balancer-api-internal: resolved host name a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:58:49Z"
    - latency: 16.644065ms
      message: 'load-balancer-api-internal: tcp connection to a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:57:49Z"
    - latency: 7.785325ms
      message: 'load-balancer-api-internal: resolved host name a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:57:49Z"
    - latency: 18.416221ms
      message: 'load-balancer-api-internal: tcp connection to a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:56:49Z"
    - latency: 7.608582ms
      message: 'load-balancer-api-internal: resolved host name a94d71876d3c64f1abc61c3427e2258d-42b7376e2e7951f0.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:56:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:54:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-216-to-network-check-target-ip-10-0-131-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-216.ec2.internal
      uid: bd0108ee-0399-408b-bfbd-0b90b8faba97
    resourceVersion: "20361"
    uid: 04a5db08-5961-463d-ae98-71c295b61eb9
  spec:
    sourcePod: network-check-source-6f78d59f99-dl2m4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T15:01:49Z"
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.132252ms
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:01:49Z"
    - latency: 17.151917ms
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:00:49Z"
    - latency: 2.192746ms
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:59:49Z"
    - latency: 2.247848ms
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:58:49Z"
    - latency: 2.504934ms
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:57:49Z"
    - latency: 2.12073ms
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:56:49Z"
    - latency: 2.331511ms
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:55:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:54:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-216-to-network-check-target-ip-10-0-133-216
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-216.ec2.internal
      uid: bd0108ee-0399-408b-bfbd-0b90b8faba97
    resourceVersion: "20362"
    uid: 98c9d3fb-be2a-4fb8-bc3f-6f802185a22c
  spec:
    sourcePod: network-check-source-6f78d59f99-dl2m4
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T15:01:49Z"
      message: 'network-check-target-ip-10-0-133-216: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.1674ms
      message: 'network-check-target-ip-10-0-133-216: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:01:49Z"
    - latency: 846.036µs
      message: 'network-check-target-ip-10-0-133-216: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:00:49Z"
    - latency: 1.061558ms
      message: 'network-check-target-ip-10-0-133-216: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:59:49Z"
    - latency: 1.23707ms
      message: 'network-check-target-ip-10-0-133-216: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:58:49Z"
    - latency: 1.662433ms
      message: 'network-check-target-ip-10-0-133-216: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:57:49Z"
    - latency: 1.145223ms
      message: 'network-check-target-ip-10-0-133-216: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:56:49Z"
    - latency: 1.354191ms
      message: 'network-check-target-ip-10-0-133-216: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:55:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:54:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-216-to-network-check-target-ip-10-0-143-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-216.ec2.internal
      uid: bd0108ee-0399-408b-bfbd-0b90b8faba97
    resourceVersion: "20360"
    uid: 5e2c02ad-6ace-4331-bb2e-4d757d7ab798
  spec:
    sourcePod: network-check-source-6f78d59f99-dl2m4
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T15:01:49Z"
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.6882ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:01:49Z"
    - latency: 1.56726ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:00:49Z"
    - latency: 1.797602ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:59:49Z"
    - latency: 2.198151ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:58:49Z"
    - latency: 1.908793ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:57:49Z"
    - latency: 1.703779ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:56:49Z"
    - latency: 2.208635ms
      message: 'network-check-target-ip-10-0-143-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:55:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T14:54:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-216-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-216.ec2.internal
      uid: bd0108ee-0399-408b-bfbd-0b90b8faba97
    resourceVersion: "18779"
    uid: 723661ff-debb-4eea-9c53-a4da001eafaf
  spec:
    sourcePod: network-check-source-6f78d59f99-dl2m4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T15:00:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 897.964µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:00:49Z"
    - latency: 17.143345ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:00:49Z"
    - latency: 1.14499ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:59:49Z"
    - latency: 1.729947ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:59:49Z"
    - latency: 784.955µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:58:49Z"
    - latency: 1.627485ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:58:49Z"
    - latency: 829.787µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:57:49Z"
    - latency: 2.422028ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:57:49Z"
    - latency: 914.583µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:56:49Z"
    - latency: 1.793441ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T14:56:49Z"
kind: List
metadata:
  resourceVersion: ""