apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:55:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-90-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-90.ec2.internal
      uid: 4866e4af-14fa-40b7-b61f-f822175143cc
    resourceVersion: "15194"
    uid: 6b89c203-4d91-4a03-a2a1-7e4c89ed4cd1
  spec:
    sourcePod: network-check-source-685456655f-z2p28
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T09:02:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.019604ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:02:31Z"
    - latency: 946.143µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:01:31Z"
    - latency: 1.018252ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:00:31Z"
    - latency: 822.278µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:59:31Z"
    - latency: 1.062974ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:58:31Z"
    - latency: 845.866µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:57:31Z"
    - latency: 813.803µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:56:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:55:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-90-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-90.ec2.internal
      uid: 4866e4af-14fa-40b7-b61f-f822175143cc
    resourceVersion: "14789"
    uid: 8ce92d96-2325-4051-bec3-c6c386a7bcf0
  spec:
    sourcePod: network-check-source-685456655f-z2p28
    targetEndpoint: a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T09:01:31Z"
      message: 'load-balancer-api-external: tcp connection to a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.584997ms
      message: 'load-balancer-api-external: tcp connection to a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:01:31Z"
    - latency: 8.063758ms
      message: 'load-balancer-api-external: resolved host name a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T09:01:31Z"
    - latency: 5.949069ms
      message: 'load-balancer-api-external: tcp connection to a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:00:31Z"
    - latency: 9.376138ms
      message: 'load-balancer-api-external: resolved host name a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T09:00:31Z"
    - latency: 4.246238ms
      message: 'load-balancer-api-external: tcp connection to a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:59:31Z"
    - latency: 8.129658ms
      message: 'load-balancer-api-external: resolved host name a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:59:31Z"
    - latency: 4.345555ms
      message: 'load-balancer-api-external: tcp connection to a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:58:31Z"
    - latency: 7.90394ms
      message: 'load-balancer-api-external: resolved host name a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:58:31Z"
    - latency: 4.108275ms
      message: 'load-balancer-api-external: tcp connection to a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:57:31Z"
    - latency: 8.444359ms
      message: 'load-balancer-api-external: resolved host name a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:57:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:55:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-90-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-90.ec2.internal
      uid: 4866e4af-14fa-40b7-b61f-f822175143cc
    resourceVersion: "14790"
    uid: 91ee2c24-3dbc-47e6-89a9-d8d31238ed1e
  spec:
    sourcePod: network-check-source-685456655f-z2p28
    targetEndpoint: a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T09:01:31Z"
      message: 'load-balancer-api-internal: tcp connection to a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.081593ms
      message: 'load-balancer-api-internal: tcp connection to a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:01:31Z"
    - latency: 8.208064ms
      message: 'load-balancer-api-internal: resolved host name a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T09:01:31Z"
    - latency: 5.981199ms
      message: 'load-balancer-api-internal: tcp connection to a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:00:31Z"
    - latency: 9.448348ms
      message: 'load-balancer-api-internal: resolved host name a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T09:00:31Z"
    - latency: 4.434163ms
      message: 'load-balancer-api-internal: tcp connection to a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:59:31Z"
    - latency: 7.985356ms
      message: 'load-balancer-api-internal: resolved host name a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:59:31Z"
    - latency: 4.226236ms
      message: 'load-balancer-api-internal: tcp connection to a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:58:31Z"
    - latency: 7.960343ms
      message: 'load-balancer-api-internal: resolved host name a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:58:31Z"
    - latency: 4.200823ms
      message: 'load-balancer-api-internal: tcp connection to a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:57:31Z"
    - latency: 8.427221ms
      message: 'load-balancer-api-internal: resolved host name a46babf6681e3469c9519edf9efc41a5-386cb4833a0c60b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:57:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:55:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-90-to-network-check-target-ip-10-0-134-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-90.ec2.internal
      uid: 4866e4af-14fa-40b7-b61f-f822175143cc
    resourceVersion: "15191"
    uid: aa1bd018-a2d2-4d24-b7aa-4ce9efb5f7d2
  spec:
    sourcePod: network-check-source-685456655f-z2p28
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T09:02:31Z"
      message: 'network-check-target-ip-10-0-134-5: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.143841ms
      message: 'network-check-target-ip-10-0-134-5: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:02:31Z"
    - latency: 2.4341ms
      message: 'network-check-target-ip-10-0-134-5: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:01:31Z"
    - latency: 2.940508ms
      message: 'network-check-target-ip-10-0-134-5: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:00:31Z"
    - latency: 2.069068ms
      message: 'network-check-target-ip-10-0-134-5: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:59:31Z"
    - latency: 2.185054ms
      message: 'network-check-target-ip-10-0-134-5: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:58:31Z"
    - latency: 2.239078ms
      message: 'network-check-target-ip-10-0-134-5: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:57:31Z"
    - latency: 2.53799ms
      message: 'network-check-target-ip-10-0-134-5: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:56:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:55:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-90-to-network-check-target-ip-10-0-135-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-90.ec2.internal
      uid: 4866e4af-14fa-40b7-b61f-f822175143cc
    resourceVersion: "15192"
    uid: bc941699-663b-494f-a5a5-aef7236915f3
  spec:
    sourcePod: network-check-source-685456655f-z2p28
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T09:02:31Z"
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.245084ms
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:02:31Z"
    - latency: 2.599884ms
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:01:31Z"
    - latency: 2.591669ms
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:00:31Z"
    - latency: 2.165727ms
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:59:31Z"
    - latency: 2.337108ms
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:58:31Z"
    - latency: 2.80534ms
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:57:31Z"
    - latency: 2.31492ms
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:56:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:55:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-90-to-network-check-target-ip-10-0-143-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-90.ec2.internal
      uid: 4866e4af-14fa-40b7-b61f-f822175143cc
    resourceVersion: "15193"
    uid: 9788047e-fb8a-462b-a2e6-410df391be0d
  spec:
    sourcePod: network-check-source-685456655f-z2p28
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T09:02:31Z"
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 927.485µs
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:02:31Z"
    - latency: 1.143058ms
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:01:31Z"
    - latency: 1.78108ms
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:00:31Z"
    - latency: 869.758µs
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:59:31Z"
    - latency: 1.181463ms
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:58:31Z"
    - latency: 1.695949ms
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:57:31Z"
    - latency: 1.200472ms
      message: 'network-check-target-ip-10-0-143-90: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:56:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T08:55:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-90-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-90.ec2.internal
      uid: 4866e4af-14fa-40b7-b61f-f822175143cc
    resourceVersion: "14788"
    uid: 3a5abf2c-8771-4e68-ae2c-b3de6eb824a6
  spec:
    sourcePod: network-check-source-685456655f-z2p28
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T09:01:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 992.702µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:01:31Z"
    - latency: 2.017438ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T09:01:31Z"
    - latency: 1.311251ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T09:00:31Z"
    - latency: 1.878273ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T09:00:31Z"
    - latency: 759.295µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:59:31Z"
    - latency: 2.059652ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:59:31Z"
    - latency: 1.203846ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:58:31Z"
    - latency: 1.693458ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:58:31Z"
    - latency: 1.113625ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T08:57:31Z"
    - latency: 1.969605ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T08:57:31Z"
kind: List
metadata:
  resourceVersion: ""