apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T07:04:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-166-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-166.ec2.internal
      uid: eaa443ac-34b6-4862-9536-5c7f7bae90bd
    resourceVersion: "24988"
    uid: 60a2cc94-8550-40c3-9536-3f9e3ce8451f
  spec:
    sourcePod: network-check-source-dbd9cf844-bn5rv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T07:11: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.140407ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:11:04Z"
    - latency: 1.24474ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:10:04Z"
    - latency: 732.849µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:09:04Z"
    - latency: 1.617025ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:08:04Z"
    - latency: 1.091777ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:07:04Z"
    - latency: 972.663µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:06:04Z"
    - latency: 905.511µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:05:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T07:04:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-166-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-166.ec2.internal
      uid: eaa443ac-34b6-4862-9536-5c7f7bae90bd
    resourceVersion: "29059"
    uid: ecae0247-c9e0-4532-a716-10c4f1d27868
  spec:
    sourcePod: network-check-source-dbd9cf844-bn5rv
    targetEndpoint: aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T07:10:04Z"
      message: 'load-balancer-api-external: tcp connection to aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.556262ms
      message: 'load-balancer-api-external: tcp connection to aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:16:04Z"
    - latency: 8.148261ms
      message: 'load-balancer-api-external: resolved host name aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:16:04Z"
    - latency: 5.251282ms
      message: 'load-balancer-api-external: tcp connection to aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:15:04Z"
    - latency: 8.289503ms
      message: 'load-balancer-api-external: resolved host name aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:15:04Z"
    - latency: 4.929551ms
      message: 'load-balancer-api-external: tcp connection to aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:14:04Z"
    - latency: 8.177072ms
      message: 'load-balancer-api-external: resolved host name aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:14:04Z"
    - latency: 4.989135ms
      message: 'load-balancer-api-external: tcp connection to aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:13:04Z"
    - latency: 8.522379ms
      message: 'load-balancer-api-external: resolved host name aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:13:04Z"
    - latency: 4.144896ms
      message: 'load-balancer-api-external: tcp connection to aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:12:04Z"
    - latency: 7.490882ms
      message: 'load-balancer-api-external: resolved host name aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:12:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T07:04:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-166-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-166.ec2.internal
      uid: eaa443ac-34b6-4862-9536-5c7f7bae90bd
    resourceVersion: "29058"
    uid: 82ecae8f-7ee4-4758-a726-d12c6344b323
  spec:
    sourcePod: network-check-source-dbd9cf844-bn5rv
    targetEndpoint: aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T07:10:04Z"
      message: 'load-balancer-api-internal: tcp connection to aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.573835ms
      message: 'load-balancer-api-internal: tcp connection to aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:16:04Z"
    - latency: 8.068614ms
      message: 'load-balancer-api-internal: resolved host name aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:16:04Z"
    - latency: 5.304115ms
      message: 'load-balancer-api-internal: tcp connection to aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:15:04Z"
    - latency: 8.137858ms
      message: 'load-balancer-api-internal: resolved host name aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:15:04Z"
    - latency: 5.225491ms
      message: 'load-balancer-api-internal: tcp connection to aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:14:04Z"
    - latency: 8.111502ms
      message: 'load-balancer-api-internal: resolved host name aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:14:04Z"
    - latency: 4.983762ms
      message: 'load-balancer-api-internal: tcp connection to aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:13:04Z"
    - latency: 8.574505ms
      message: 'load-balancer-api-internal: resolved host name aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:13:04Z"
    - latency: 4.136991ms
      message: 'load-balancer-api-internal: tcp connection to aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:12:04Z"
    - latency: 7.565708ms
      message: 'load-balancer-api-internal: resolved host name aed32f62cbc4147bbba59a1ca8d4f939-c93dbb66178d49fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:12:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T07:04:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-166-to-network-check-target-ip-10-0-131-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-166.ec2.internal
      uid: eaa443ac-34b6-4862-9536-5c7f7bae90bd
    resourceVersion: "24987"
    uid: 7a7c823d-ef42-48b6-b13b-8a31532f6a49
  spec:
    sourcePod: network-check-source-dbd9cf844-bn5rv
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T07:11:04Z"
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.206298ms
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:11:04Z"
    - latency: 2.160807ms
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:10:04Z"
    - latency: 1.977082ms
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:09:04Z"
    - latency: 2.292129ms
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:08:04Z"
    - latency: 2.186631ms
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:07:04Z"
    - latency: 2.175952ms
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:06:04Z"
    - latency: 2.277892ms
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:05:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T07:04:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-166-to-network-check-target-ip-10-0-134-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-166.ec2.internal
      uid: eaa443ac-34b6-4862-9536-5c7f7bae90bd
    resourceVersion: "24986"
    uid: c19700e3-30f6-47ce-a3c9-6e72bb71a942
  spec:
    sourcePod: network-check-source-dbd9cf844-bn5rv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T07:11:04Z"
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.553388ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:11:04Z"
    - latency: 2.196419ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:10:04Z"
    - latency: 1.569419ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:09:04Z"
    - latency: 2.254838ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:08:04Z"
    - latency: 1.872971ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:07:04Z"
    - latency: 1.928683ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:06:04Z"
    - latency: 1.601366ms
      message: 'network-check-target-ip-10-0-134-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:05:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T07:04:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-166-to-network-check-target-ip-10-0-139-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-166.ec2.internal
      uid: eaa443ac-34b6-4862-9536-5c7f7bae90bd
    resourceVersion: "24985"
    uid: 1403b049-91a8-4e21-a5b7-64d049c834d9
  spec:
    sourcePod: network-check-source-dbd9cf844-bn5rv
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T07:11:04Z"
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.516682ms
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:11:04Z"
    - latency: 1.581598ms
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:10:04Z"
    - latency: 687.477µs
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:09:04Z"
    - latency: 1.852734ms
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:08:04Z"
    - latency: 908.553µs
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:07:04Z"
    - latency: 1.508185ms
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:06:04Z"
    - latency: 1.374913ms
      message: 'network-check-target-ip-10-0-139-166: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:05:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T07:04:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-166-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-166.ec2.internal
      uid: eaa443ac-34b6-4862-9536-5c7f7bae90bd
    resourceVersion: "29056"
    uid: 7b9efb93-c83f-4e50-a9c5-e5ab1caa3304
  spec:
    sourcePod: network-check-source-dbd9cf844-bn5rv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T07:10:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 941.939µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:16:04Z"
    - latency: 1.764319ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:16:04Z"
    - latency: 1.028724ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:15:04Z"
    - latency: 1.892645ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:15:04Z"
    - latency: 809.179µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:14:04Z"
    - latency: 1.667969ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:14:04Z"
    - latency: 901.48µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:13:04Z"
    - latency: 2.48892ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:13:04Z"
    - latency: 1.083073ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:12:04Z"
    - latency: 1.81237ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:12:04Z"
kind: List
metadata:
  resourceVersion: ""