apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:15:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-204-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-204.ec2.internal
      uid: 04986936-0829-4165-b1ed-82036b32d608
    resourceVersion: "23984"
    uid: 19b9b96a-7b77-4b8c-ae31-9b6ebcda4336
  spec:
    sourcePod: network-check-source-685456655f-9stz9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:22:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.510137ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:22:58Z"
    - latency: 1.168997ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:21:58Z"
    - latency: 1.142421ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:20:58Z"
    - latency: 1.807821ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:19:58Z"
    - latency: 813.611µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:58Z"
    - latency: 848.035µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:58Z"
    - latency: 1.016283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:15:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-204-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-204.ec2.internal
      uid: 04986936-0829-4165-b1ed-82036b32d608
    resourceVersion: "22884"
    uid: 06a3e08f-0f84-4b3f-94b4-7afcd7dc5d2a
  spec:
    sourcePod: network-check-source-685456655f-9stz9
    targetEndpoint: a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:21:58Z"
      message: 'load-balancer-api-external: tcp connection to a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.085915ms
      message: 'load-balancer-api-external: tcp connection to a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:21:58Z"
    - latency: 6.42474ms
      message: 'load-balancer-api-external: resolved host name a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:21:58Z"
    - latency: 5.030551ms
      message: 'load-balancer-api-external: tcp connection to a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:20:58Z"
    - latency: 8.959375ms
      message: 'load-balancer-api-external: resolved host name a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:20:58Z"
    - latency: 4.685485ms
      message: 'load-balancer-api-external: tcp connection to a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:19:58Z"
    - latency: 7.585569ms
      message: 'load-balancer-api-external: resolved host name a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:19:58Z"
    - latency: 4.213707ms
      message: 'load-balancer-api-external: tcp connection to a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:58Z"
    - latency: 11.971055ms
      message: 'load-balancer-api-external: resolved host name a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:18:58Z"
    - latency: 5.468193ms
      message: 'load-balancer-api-external: tcp connection to a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:58Z"
    - latency: 7.49399ms
      message: 'load-balancer-api-external: resolved host name a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:17:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:15:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-204-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-204.ec2.internal
      uid: 04986936-0829-4165-b1ed-82036b32d608
    resourceVersion: "22885"
    uid: 92b70f76-237b-4345-8b44-d2969f07827a
  spec:
    sourcePod: network-check-source-685456655f-9stz9
    targetEndpoint: a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:21:58Z"
      message: 'load-balancer-api-internal: tcp connection to a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.078538ms
      message: 'load-balancer-api-internal: tcp connection to a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:21:58Z"
    - latency: 6.437762ms
      message: 'load-balancer-api-internal: resolved host name a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:21:58Z"
    - latency: 4.687399ms
      message: 'load-balancer-api-internal: tcp connection to a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:20:58Z"
    - latency: 8.977615ms
      message: 'load-balancer-api-internal: resolved host name a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:20:58Z"
    - latency: 4.668223ms
      message: 'load-balancer-api-internal: tcp connection to a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:19:58Z"
    - latency: 7.625664ms
      message: 'load-balancer-api-internal: resolved host name a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:19:58Z"
    - latency: 4.215201ms
      message: 'load-balancer-api-internal: tcp connection to a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:58Z"
    - latency: 12.067772ms
      message: 'load-balancer-api-internal: resolved host name a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:18:58Z"
    - latency: 5.473249ms
      message: 'load-balancer-api-internal: tcp connection to a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:58Z"
    - latency: 7.523228ms
      message: 'load-balancer-api-internal: resolved host name a61a824659e8445eaa13450fa203cd61-cd4cc8cdee030412.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:17:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:15:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-204-to-network-check-target-ip-10-0-132-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-204.ec2.internal
      uid: 04986936-0829-4165-b1ed-82036b32d608
    resourceVersion: "23980"
    uid: 5132780f-8ee3-4059-b7a8-d08f09c16f4b
  spec:
    sourcePod: network-check-source-685456655f-9stz9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:22:58Z"
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.067888ms
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:22:58Z"
    - latency: 983.997µs
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:21:58Z"
    - latency: 852.569µs
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:20:58Z"
    - latency: 956.43µs
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:19:58Z"
    - latency: 1.199728ms
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:58Z"
    - latency: 764.054µs
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:58Z"
    - latency: 1.220397ms
      message: 'network-check-target-ip-10-0-132-204: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:15:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-204-to-network-check-target-ip-10-0-140-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-204.ec2.internal
      uid: 04986936-0829-4165-b1ed-82036b32d608
    resourceVersion: "23981"
    uid: 0c2b922a-4aff-467f-989f-4a6b5a1a3098
  spec:
    sourcePod: network-check-source-685456655f-9stz9
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:22:58Z"
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.027004ms
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:22:58Z"
    - latency: 2.461698ms
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:21:58Z"
    - latency: 2.248679ms
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:20:58Z"
    - latency: 2.435763ms
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:19:58Z"
    - latency: 2.207142ms
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:58Z"
    - latency: 2.123274ms
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:58Z"
    - latency: 2.243504ms
      message: 'network-check-target-ip-10-0-140-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:15:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-204-to-network-check-target-ip-10-0-143-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-204.ec2.internal
      uid: 04986936-0829-4165-b1ed-82036b32d608
    resourceVersion: "23983"
    uid: 12a9246b-7b94-4f13-bea4-2a05955e1315
  spec:
    sourcePod: network-check-source-685456655f-9stz9
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:22:58Z"
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.125193ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:22:58Z"
    - latency: 2.149981ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:21:58Z"
    - latency: 1.888529ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:20:58Z"
    - latency: 1.963749ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:19:58Z"
    - latency: 1.756217ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:58Z"
    - latency: 1.791657ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:58Z"
    - latency: 1.893304ms
      message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:16:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T23:15:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-204-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-204.ec2.internal
      uid: 04986936-0829-4165-b1ed-82036b32d608
    resourceVersion: "22882"
    uid: 3c011c99-9ee5-41b4-9a85-39eb904be701
  spec:
    sourcePod: network-check-source-685456655f-9stz9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T23:21:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 971.657µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:21:58Z"
    - latency: 1.717626ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:21:58Z"
    - latency: 1.153815ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:20:58Z"
    - latency: 1.923574ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:20:58Z"
    - latency: 1.085836ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:19:58Z"
    - latency: 2.258544ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:19:58Z"
    - latency: 1.328613ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:18:58Z"
    - latency: 1.66222ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:18:58Z"
    - latency: 882.627µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T23:17:58Z"
    - latency: 1.783454ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T23:17:58Z"
kind: List
metadata:
  resourceVersion: ""