apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T04:43:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-241-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-241.ec2.internal
      uid: eb873a32-d027-4609-b683-0aa29bf43228
    resourceVersion: "23515"
    uid: f0bf1d62-ff2a-44dd-bdff-efabad000526
  spec:
    sourcePod: network-check-source-8894fc9bd-5cxvc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T04:50:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.124669ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:50:04Z"
    - latency: 3.230892ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:49:04Z"
    - latency: 914.423µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:48:04Z"
    - latency: 1.721907ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:47:04Z"
    - latency: 805.432µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:46:04Z"
    - latency: 1.018257ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:45:04Z"
    - latency: 1.035186ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:44:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T04:43:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-241-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-241.ec2.internal
      uid: eb873a32-d027-4609-b683-0aa29bf43228
    resourceVersion: "22331"
    uid: 8d603af4-a692-449d-ba95-56edf2d71168
  spec:
    sourcePod: network-check-source-8894fc9bd-5cxvc
    targetEndpoint: a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T04:49:04Z"
      message: 'load-balancer-api-external: tcp connection to a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.306539ms
      message: 'load-balancer-api-external: tcp connection to a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:49:04Z"
    - latency: 11.451611ms
      message: 'load-balancer-api-external: resolved host name a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:49:04Z"
    - latency: 4.656451ms
      message: 'load-balancer-api-external: tcp connection to a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:48:04Z"
    - latency: 11.765662ms
      message: 'load-balancer-api-external: resolved host name a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:48:04Z"
    - latency: 4.80854ms
      message: 'load-balancer-api-external: tcp connection to a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:47:04Z"
    - latency: 15.938066ms
      message: 'load-balancer-api-external: resolved host name a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:47:04Z"
    - latency: 3.746607ms
      message: 'load-balancer-api-external: tcp connection to a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:46:04Z"
    - latency: 10.028996ms
      message: 'load-balancer-api-external: resolved host name a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:46:04Z"
    - latency: 4.420489ms
      message: 'load-balancer-api-external: tcp connection to a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:45:04Z"
    - latency: 8.817299ms
      message: 'load-balancer-api-external: resolved host name a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:45:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T04:43:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-241-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-241.ec2.internal
      uid: eb873a32-d027-4609-b683-0aa29bf43228
    resourceVersion: "22330"
    uid: 1b42d6a3-5f40-4ed0-9cd5-516681ed1b16
  spec:
    sourcePod: network-check-source-8894fc9bd-5cxvc
    targetEndpoint: a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T04:49:04Z"
      message: 'load-balancer-api-internal: tcp connection to a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.872847ms
      message: 'load-balancer-api-internal: tcp connection to a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:49:04Z"
    - latency: 15.478737ms
      message: 'load-balancer-api-internal: resolved host name a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:49:04Z"
    - latency: 3.862025ms
      message: 'load-balancer-api-internal: tcp connection to a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:48:04Z"
    - latency: 11.680046ms
      message: 'load-balancer-api-internal: resolved host name a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:48:04Z"
    - latency: 4.543514ms
      message: 'load-balancer-api-internal: tcp connection to a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:47:04Z"
    - latency: 15.853698ms
      message: 'load-balancer-api-internal: resolved host name a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:47:04Z"
    - latency: 3.524953ms
      message: 'load-balancer-api-internal: tcp connection to a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:46:04Z"
    - latency: 10.014137ms
      message: 'load-balancer-api-internal: resolved host name a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:46:04Z"
    - latency: 4.416646ms
      message: 'load-balancer-api-internal: tcp connection to a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:45:04Z"
    - latency: 8.828084ms
      message: 'load-balancer-api-internal: resolved host name a4cb060c08a3c4ae9b4f4de2ea8c9afc-760c9af5c26787ab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:45:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T04:43:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-241-to-network-check-target-ip-10-0-135-122
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-241.ec2.internal
      uid: eb873a32-d027-4609-b683-0aa29bf43228
    resourceVersion: "23513"
    uid: 865e82fa-0a21-4824-8f4a-6f57170b4f6c
  spec:
    sourcePod: network-check-source-8894fc9bd-5cxvc
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T04:50:04Z"
      message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.42849ms
      message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:50:04Z"
    - latency: 2.368215ms
      message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:49:04Z"
    - latency: 2.146088ms
      message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:48:04Z"
    - latency: 2.956324ms
      message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:47:04Z"
    - latency: 2.115708ms
      message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:46:04Z"
    - latency: 2.271398ms
      message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:45:04Z"
    - latency: 2.23874ms
      message: 'network-check-target-ip-10-0-135-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:44:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T04:43:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-241-to-network-check-target-ip-10-0-140-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-241.ec2.internal
      uid: eb873a32-d027-4609-b683-0aa29bf43228
    resourceVersion: "23514"
    uid: 90b8fc7c-483a-41da-8cc0-938a9225fcb2
  spec:
    sourcePod: network-check-source-8894fc9bd-5cxvc
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T04:50:04Z"
      message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.16885ms
      message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:50:04Z"
    - latency: 3.246573ms
      message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:49:04Z"
    - latency: 2.078126ms
      message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:48:04Z"
    - latency: 3.037772ms
      message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:47:04Z"
    - latency: 1.898487ms
      message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:46:04Z"
    - latency: 2.403848ms
      message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:45:04Z"
    - latency: 2.15893ms
      message: 'network-check-target-ip-10-0-140-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:44:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T04:43:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-241-to-network-check-target-ip-10-0-141-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-241.ec2.internal
      uid: eb873a32-d027-4609-b683-0aa29bf43228
    resourceVersion: "23512"
    uid: 2fad5b34-f55a-440c-9d5f-c80058fd57d0
  spec:
    sourcePod: network-check-source-8894fc9bd-5cxvc
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T04:50:04Z"
      message: 'network-check-target-ip-10-0-141-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 870.821µs
      message: 'network-check-target-ip-10-0-141-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:50:04Z"
    - latency: 3.391352ms
      message: 'network-check-target-ip-10-0-141-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:49:04Z"
    - latency: 844.338µs
      message: 'network-check-target-ip-10-0-141-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:48:04Z"
    - latency: 1.025979ms
      message: 'network-check-target-ip-10-0-141-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:47:04Z"
    - latency: 744.178µs
      message: 'network-check-target-ip-10-0-141-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:46:04Z"
    - latency: 1.396222ms
      message: 'network-check-target-ip-10-0-141-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:45:04Z"
    - latency: 1.471231ms
      message: 'network-check-target-ip-10-0-141-241: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:44:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T04:43:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-241-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-241.ec2.internal
      uid: eb873a32-d027-4609-b683-0aa29bf43228
    resourceVersion: "22329"
    uid: a265d2fc-82c7-4d2f-ae9f-f9e5ab9c75ee
  spec:
    sourcePod: network-check-source-8894fc9bd-5cxvc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T04:49:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 878.76µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:49:04Z"
    - latency: 3.129856ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:49:04Z"
    - latency: 812.984µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:48:04Z"
    - latency: 1.57224ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:48:04Z"
    - latency: 1.115739ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:47:04Z"
    - latency: 2.277323ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:47:04Z"
    - latency: 737.342µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:46:04Z"
    - latency: 1.70611ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:46:04Z"
    - latency: 916.801µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T04:45:04Z"
    - latency: 2.082122ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T04:45:04Z"
kind: List
metadata:
  resourceVersion: ""