apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:08:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-188-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-188.us-west-2.compute.internal
      uid: 3fc4af26-f446-47b2-8f12-81f5f8f53102
    resourceVersion: "10806"
    uid: ae01896f-ae97-4c67-aa3e-d908020d3a81
  spec:
    sourcePod: network-check-source-6f78d59f99-qtf26
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:15:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.131516ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:15:54Z"
    - latency: 899.617µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:14:54Z"
    - latency: 1.063384ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:13:54Z"
    - latency: 1.025201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:12:54Z"
    - latency: 1.179212ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:11:54Z"
    - latency: 1.384127ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:10:54Z"
    - latency: 1.085501ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:09:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:08:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-188-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-188.us-west-2.compute.internal
      uid: 3fc4af26-f446-47b2-8f12-81f5f8f53102
    resourceVersion: "10375"
    uid: 612d48a6-5a31-474f-8985-32d8c68747c8
  spec:
    sourcePod: network-check-source-6f78d59f99-qtf26
    targetEndpoint: aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:14:54Z"
      message: 'load-balancer-api-external: tcp connection to aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 51.902854ms
      message: 'load-balancer-api-external: tcp connection to aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:14:54Z"
    - latency: 7.941051ms
      message: 'load-balancer-api-external: resolved host name aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:14:54Z"
    - latency: 52.171391ms
      message: 'load-balancer-api-external: tcp connection to aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:13:54Z"
    - latency: 8.048412ms
      message: 'load-balancer-api-external: resolved host name aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:13:54Z"
    - latency: 51.820324ms
      message: 'load-balancer-api-external: tcp connection to aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:12:54Z"
    - latency: 6.772489ms
      message: 'load-balancer-api-external: resolved host name aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:12:54Z"
    - latency: 51.68196ms
      message: 'load-balancer-api-external: tcp connection to aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:11:54Z"
    - latency: 8.327184ms
      message: 'load-balancer-api-external: resolved host name aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:11:54Z"
    - latency: 54.965307ms
      message: 'load-balancer-api-external: tcp connection to aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:10:54Z"
    - latency: 7.793613ms
      message: 'load-balancer-api-external: resolved host name aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:10:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:08:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-188-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-188.us-west-2.compute.internal
      uid: 3fc4af26-f446-47b2-8f12-81f5f8f53102
    resourceVersion: "10376"
    uid: c70cc944-6d73-407d-bbcf-40c425892f6a
  spec:
    sourcePod: network-check-source-6f78d59f99-qtf26
    targetEndpoint: aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:14:54Z"
      message: 'load-balancer-api-internal: tcp connection to aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.686609ms
      message: 'load-balancer-api-internal: tcp connection to aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:14:54Z"
    - latency: 7.796714ms
      message: 'load-balancer-api-internal: resolved host name aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:14:54Z"
    - latency: 55.269745ms
      message: 'load-balancer-api-internal: tcp connection to aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:13:54Z"
    - latency: 8.098632ms
      message: 'load-balancer-api-internal: resolved host name aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:13:54Z"
    - latency: 56.005521ms
      message: 'load-balancer-api-internal: tcp connection to aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:12:54Z"
    - latency: 6.712102ms
      message: 'load-balancer-api-internal: resolved host name aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:12:54Z"
    - latency: 51.684917ms
      message: 'load-balancer-api-internal: tcp connection to aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:11:54Z"
    - latency: 8.281134ms
      message: 'load-balancer-api-internal: resolved host name aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:11:54Z"
    - latency: 51.375344ms
      message: 'load-balancer-api-internal: tcp connection to aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:10:54Z"
    - latency: 7.75339ms
      message: 'load-balancer-api-internal: resolved host name aeb4e527937bd4574a1a1ee5ae30d8bd-18bb39833cf7ec80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:10:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:08:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-188-to-network-check-target-ip-10-0-137-207
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-188.us-west-2.compute.internal
      uid: 3fc4af26-f446-47b2-8f12-81f5f8f53102
    resourceVersion: "10804"
    uid: cbd3d7af-944d-483f-bf9e-d21290f7933b
  spec:
    sourcePod: network-check-source-6f78d59f99-qtf26
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:15:54Z"
      message: 'network-check-target-ip-10-0-137-207: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.590801ms
      message: 'network-check-target-ip-10-0-137-207: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:15:54Z"
    - latency: 2.294641ms
      message: 'network-check-target-ip-10-0-137-207: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:14:54Z"
    - latency: 2.189403ms
      message: 'network-check-target-ip-10-0-137-207: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:13:54Z"
    - latency: 2.19336ms
      message: 'network-check-target-ip-10-0-137-207: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:12:54Z"
    - latency: 2.689649ms
      message: 'network-check-target-ip-10-0-137-207: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:11:54Z"
    - latency: 2.509378ms
      message: 'network-check-target-ip-10-0-137-207: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:10:54Z"
    - latency: 2.431729ms
      message: 'network-check-target-ip-10-0-137-207: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:09:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:08:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-188-to-network-check-target-ip-10-0-143-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-188.us-west-2.compute.internal
      uid: 3fc4af26-f446-47b2-8f12-81f5f8f53102
    resourceVersion: "10802"
    uid: 96dfbba5-b4e7-455e-8238-60396a44b1d1
  spec:
    sourcePod: network-check-source-6f78d59f99-qtf26
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:15:54Z"
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.587909ms
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:15:54Z"
    - latency: 855.118µs
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:14:54Z"
    - latency: 951.909µs
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:13:54Z"
    - latency: 804.262µs
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:12:54Z"
    - latency: 1.348492ms
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:11:54Z"
    - latency: 929.875µs
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:10:54Z"
    - latency: 1.289728ms
      message: 'network-check-target-ip-10-0-143-188: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:09:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:08:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-188-to-network-check-target-ip-10-0-143-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-188.us-west-2.compute.internal
      uid: 3fc4af26-f446-47b2-8f12-81f5f8f53102
    resourceVersion: "10803"
    uid: 4b184f90-fccd-40fc-9b83-9b13c0cc4526
  spec:
    sourcePod: network-check-source-6f78d59f99-qtf26
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:15:54Z"
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.282383ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:15:54Z"
    - latency: 2.155111ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:14:54Z"
    - latency: 2.506509ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:13:54Z"
    - latency: 2.0268ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:12:54Z"
    - latency: 2.182115ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:11:54Z"
    - latency: 2.2119ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:10:54Z"
    - latency: 2.278227ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:09:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:08:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-188-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-188.us-west-2.compute.internal
      uid: 3fc4af26-f446-47b2-8f12-81f5f8f53102
    resourceVersion: "10374"
    uid: 6579b9ff-a300-462e-b514-d128bdcc5ca5
  spec:
    sourcePod: network-check-source-6f78d59f99-qtf26
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:14:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.401µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:14:54Z"
    - latency: 2.084217ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:14:54Z"
    - latency: 1.176722ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:13:54Z"
    - latency: 1.648942ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:13:54Z"
    - latency: 903.345µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:12:54Z"
    - latency: 1.768325ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:12:54Z"
    - latency: 920.078µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:11:54Z"
    - latency: 1.75358ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:11:54Z"
    - latency: 930.975µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:10:54Z"
    - latency: 1.976236ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:10:54Z"
kind: List
metadata:
  resourceVersion: ""