apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T21:01:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-24-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-24.ec2.internal
      uid: 349681eb-bc5a-4484-8968-5c0625ccab2a
    resourceVersion: "11122"
    uid: 31c4b6d5-986a-4616-9b5d-d9b555a9326e
  spec:
    sourcePod: network-check-source-685456655f-2cvhw
    targetEndpoint: 172.31.0.1:443
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T21:01:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-24-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-24.ec2.internal
      uid: 349681eb-bc5a-4484-8968-5c0625ccab2a
    resourceVersion: "23000"
    uid: 51a17da2-0cfb-4fd8-b966-cfb8974b03d1
  spec:
    sourcePod: network-check-source-685456655f-2cvhw
    targetEndpoint: ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T21:07:30Z"
      message: 'load-balancer-api-external: tcp connection to ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.408548ms
      message: 'load-balancer-api-external: tcp connection to ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:07:30Z"
    - latency: 15.503361ms
      message: 'load-balancer-api-external: resolved host name ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:07:30Z"
    - latency: 4.968894ms
      message: 'load-balancer-api-external: tcp connection to ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:06:30Z"
    - latency: 7.745596ms
      message: 'load-balancer-api-external: resolved host name ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:06:30Z"
    - latency: 4.616787ms
      message: 'load-balancer-api-external: tcp connection to ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:05:30Z"
    - latency: 8.942134ms
      message: 'load-balancer-api-external: resolved host name ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:05:30Z"
    - latency: 3.643143ms
      message: 'load-balancer-api-external: tcp connection to ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:04:30Z"
    - latency: 7.907823ms
      message: 'load-balancer-api-external: resolved host name ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:04:30Z"
    - latency: 4.081459ms
      message: 'load-balancer-api-external: tcp connection to ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:03:30Z"
    - latency: 7.379378ms
      message: 'load-balancer-api-external: resolved host name ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:03:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T21:01:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-24-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-24.ec2.internal
      uid: 349681eb-bc5a-4484-8968-5c0625ccab2a
    resourceVersion: "23001"
    uid: c986a7cb-10a7-4249-9791-3effc1fe7052
  spec:
    sourcePod: network-check-source-685456655f-2cvhw
    targetEndpoint: ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T21:07:30Z"
      message: 'load-balancer-api-internal: tcp connection to ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.463652ms
      message: 'load-balancer-api-internal: tcp connection to ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:07:30Z"
    - latency: 15.456793ms
      message: 'load-balancer-api-internal: resolved host name ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:07:30Z"
    - latency: 4.994341ms
      message: 'load-balancer-api-internal: tcp connection to ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:06:30Z"
    - latency: 7.686619ms
      message: 'load-balancer-api-internal: resolved host name ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:06:30Z"
    - latency: 3.854038ms
      message: 'load-balancer-api-internal: tcp connection to ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:05:30Z"
    - latency: 8.880657ms
      message: 'load-balancer-api-internal: resolved host name ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:05:30Z"
    - latency: 3.696513ms
      message: 'load-balancer-api-internal: tcp connection to ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:04:30Z"
    - latency: 7.972388ms
      message: 'load-balancer-api-internal: resolved host name ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:04:30Z"
    - latency: 4.290216ms
      message: 'load-balancer-api-internal: tcp connection to ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:03:30Z"
    - latency: 7.454675ms
      message: 'load-balancer-api-internal: resolved host name ae400727eddc542d59f1b373695f45b5-3098cc1c27948816.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:03:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T21:01:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-24-to-network-check-target-ip-10-0-136-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-24.ec2.internal
      uid: 349681eb-bc5a-4484-8968-5c0625ccab2a
    resourceVersion: "11129"
    uid: ee40b3c7-0f4e-4d8b-b129-0dc80364d589
  spec:
    sourcePod: network-check-source-685456655f-2cvhw
    targetEndpoint: 10.134.0.4:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T21:01:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-24-to-network-check-target-ip-10-0-138-24
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-24.ec2.internal
      uid: 349681eb-bc5a-4484-8968-5c0625ccab2a
    resourceVersion: "11128"
    uid: 5ef1ca50-4047-438e-89db-37115ead755d
  spec:
    sourcePod: network-check-source-685456655f-2cvhw
    targetEndpoint: 10.133.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T21:01:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-24-to-network-check-target-ip-10-0-140-24
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-24.ec2.internal
      uid: 349681eb-bc5a-4484-8968-5c0625ccab2a
    resourceVersion: "11127"
    uid: 568a2cac-0007-425f-8aef-e618fd560370
  spec:
    sourcePod: network-check-source-685456655f-2cvhw
    targetEndpoint: 10.132.0.5:8080
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T21:01:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-24-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-24.ec2.internal
      uid: 349681eb-bc5a-4484-8968-5c0625ccab2a
    resourceVersion: "22999"
    uid: 62f78501-3c73-47d0-bc42-2715ab01e34b
  spec:
    sourcePod: network-check-source-685456655f-2cvhw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T21:07:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.022034ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:07:30Z"
    - latency: 2.175237ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:07:30Z"
    - latency: 855.993µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:06:30Z"
    - latency: 2.269284ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:06:30Z"
    - latency: 1.164262ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:05:30Z"
    - latency: 1.966496ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:05:30Z"
    - latency: 1.496267ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:04:30Z"
    - latency: 2.162919ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:04:30Z"
    - latency: 1.603674ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T21:03:30Z"
    - latency: 2.130968ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T21:03:30Z"
kind: List
metadata:
  resourceVersion: ""