apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T07:09:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-34-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-34.ec2.internal
      uid: 50a7554a-c632-47a6-87a3-d2a609abd04c
    resourceVersion: "15492"
    uid: 940a5451-8c4c-40ea-8765-f47b5ffe496a
  spec:
    sourcePod: network-check-source-6f8b768455-8hc6w
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T07:16:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.077988ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:16:25Z"
    - latency: 1.531668ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:15:25Z"
    - latency: 1.221996ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:14:25Z"
    - latency: 1.133807ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:13:25Z"
    - latency: 732.538µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:12:25Z"
    - latency: 969.001µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:11:25Z"
    - latency: 1.063246ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:10:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T07:09:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-34-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-34.ec2.internal
      uid: 50a7554a-c632-47a6-87a3-d2a609abd04c
    resourceVersion: "17629"
    uid: a6072bc0-1a29-4dca-8e60-8a05106a2d07
  spec:
    sourcePod: network-check-source-6f8b768455-8hc6w
    targetEndpoint: af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T07:15:25Z"
      message: 'load-balancer-api-external: tcp connection to af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.376323ms
      message: 'load-balancer-api-external: tcp connection to af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:21:25Z"
    - latency: 11.219659ms
      message: 'load-balancer-api-external: resolved host name af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T07:21:25Z"
    - latency: 4.57099ms
      message: 'load-balancer-api-external: tcp connection to af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:20:25Z"
    - latency: 7.974559ms
      message: 'load-balancer-api-external: resolved host name af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T07:20:25Z"
    - latency: 4.703925ms
      message: 'load-balancer-api-external: tcp connection to af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:19:25Z"
    - latency: 8.132411ms
      message: 'load-balancer-api-external: resolved host name af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T07:19:25Z"
    - latency: 5.001005ms
      message: 'load-balancer-api-external: tcp connection to af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:18:25Z"
    - latency: 13.921579ms
      message: 'load-balancer-api-external: resolved host name af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T07:18:25Z"
    - latency: 5.002901ms
      message: 'load-balancer-api-external: tcp connection to af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:17:25Z"
    - latency: 8.149569ms
      message: 'load-balancer-api-external: resolved host name af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T07:17:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T07:09:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-34-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-34.ec2.internal
      uid: 50a7554a-c632-47a6-87a3-d2a609abd04c
    resourceVersion: "17630"
    uid: 07749452-822d-47e6-9f8d-9edfb4b131f7
  spec:
    sourcePod: network-check-source-6f8b768455-8hc6w
    targetEndpoint: af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T07:15:25Z"
      message: 'load-balancer-api-internal: tcp connection to af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.375487ms
      message: 'load-balancer-api-internal: tcp connection to af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:21:25Z"
    - latency: 11.304848ms
      message: 'load-balancer-api-internal: resolved host name af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T07:21:25Z"
    - latency: 4.366366ms
      message: 'load-balancer-api-internal: tcp connection to af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:20:25Z"
    - latency: 7.942869ms
      message: 'load-balancer-api-internal: resolved host name af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T07:20:25Z"
    - latency: 4.930352ms
      message: 'load-balancer-api-internal: tcp connection to af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:19:25Z"
    - latency: 8.092815ms
      message: 'load-balancer-api-internal: resolved host name af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T07:19:25Z"
    - latency: 4.999626ms
      message: 'load-balancer-api-internal: tcp connection to af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:18:25Z"
    - latency: 13.962569ms
      message: 'load-balancer-api-internal: resolved host name af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T07:18:25Z"
    - latency: 4.986714ms
      message: 'load-balancer-api-internal: tcp connection to af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:17:25Z"
    - latency: 8.113693ms
      message: 'load-balancer-api-internal: resolved host name af38224cf05f44a61bcda63ed21750f0-fbdbac3577f5cc01.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T07:17:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T07:09:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-34-to-network-check-target-ip-10-0-132-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-34.ec2.internal
      uid: 50a7554a-c632-47a6-87a3-d2a609abd04c
    resourceVersion: "15489"
    uid: 7a817d56-10d0-4e01-98cc-59c7fdad28ef
  spec:
    sourcePod: network-check-source-6f8b768455-8hc6w
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T07:16:25Z"
      message: 'network-check-target-ip-10-0-132-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.490558ms
      message: 'network-check-target-ip-10-0-132-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:16:25Z"
    - latency: 855.688µs
      message: 'network-check-target-ip-10-0-132-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:15:25Z"
    - latency: 861.73µs
      message: 'network-check-target-ip-10-0-132-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:14:25Z"
    - latency: 1.438911ms
      message: 'network-check-target-ip-10-0-132-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:13:25Z"
    - latency: 905.208µs
      message: 'network-check-target-ip-10-0-132-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:12:25Z"
    - latency: 796.441µs
      message: 'network-check-target-ip-10-0-132-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:11:25Z"
    - latency: 1.800997ms
      message: 'network-check-target-ip-10-0-132-34: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:10:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T07:09:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-34-to-network-check-target-ip-10-0-132-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-34.ec2.internal
      uid: 50a7554a-c632-47a6-87a3-d2a609abd04c
    resourceVersion: "15490"
    uid: 70a89379-b229-4d01-bc44-7c017ab87393
  spec:
    sourcePod: network-check-source-6f8b768455-8hc6w
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T07:16:25Z"
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.222291ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:16:25Z"
    - latency: 2.182649ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:15:25Z"
    - latency: 2.544508ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:14:25Z"
    - latency: 2.249369ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:13:25Z"
    - latency: 2.270622ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:12:25Z"
    - latency: 2.107607ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:11:25Z"
    - latency: 2.201839ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:10:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T07:09:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-34-to-network-check-target-ip-10-0-139-18
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-34.ec2.internal
      uid: 50a7554a-c632-47a6-87a3-d2a609abd04c
    resourceVersion: "15491"
    uid: d102110a-095e-4830-bd8b-7b44551f3b3d
  spec:
    sourcePod: network-check-source-6f8b768455-8hc6w
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T07:16:25Z"
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.327461ms
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:16:25Z"
    - latency: 2.087125ms
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:15:25Z"
    - latency: 2.548944ms
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:14:25Z"
    - latency: 2.464435ms
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:13:25Z"
    - latency: 2.487839ms
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:12:25Z"
    - latency: 2.292238ms
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:11:25Z"
    - latency: 2.842083ms
      message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:10:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T07:09:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-34-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-34.ec2.internal
      uid: 50a7554a-c632-47a6-87a3-d2a609abd04c
    resourceVersion: "17628"
    uid: c5e98eca-2af9-4c65-8a5f-1cafc8f97de7
  spec:
    sourcePod: network-check-source-6f8b768455-8hc6w
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T07:15:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.032597ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:21:25Z"
    - latency: 1.910238ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T07:21:25Z"
    - latency: 817.081µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:20:25Z"
    - latency: 1.707207ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T07:20:25Z"
    - latency: 1.198725ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:19:25Z"
    - latency: 1.733473ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T07:19:25Z"
    - latency: 856.353µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:18:25Z"
    - latency: 1.818917ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T07:18:25Z"
    - latency: 749.502µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T07:17:25Z"
    - latency: 1.823997ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T07:17:25Z"
kind: List
metadata:
  resourceVersion: ""