apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T14:50:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-166-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-166.ec2.internal
      uid: 5bc40b26-c2e3-4625-bef2-374a44157e40
    resourceVersion: "23152"
    uid: efe495cd-014f-4cc5-8aa2-89320892fc0a
  spec:
    sourcePod: network-check-source-56d84b9f44-4hxsn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T14:57:14Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.087831ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:57:14Z"
    - latency: 1.154933ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:56:14Z"
    - latency: 958.309µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:55:14Z"
    - latency: 1.269441ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:54:14Z"
    - latency: 1.066998ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:53:14Z"
    - latency: 1.17095ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:52:14Z"
    - latency: 1.713002ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:51:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T14:50:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-166-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-166.ec2.internal
      uid: 5bc40b26-c2e3-4625-bef2-374a44157e40
    resourceVersion: "22095"
    uid: 7d3a4337-eb94-45d1-9f77-09dd354041d8
  spec:
    sourcePod: network-check-source-56d84b9f44-4hxsn
    targetEndpoint: a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T14:56:14Z"
      message: 'load-balancer-api-external: tcp connection to a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.006613ms
      message: 'load-balancer-api-external: tcp connection to a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:56:14Z"
    - latency: 12.549311ms
      message: 'load-balancer-api-external: resolved host name a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:56:14Z"
    - latency: 4.197409ms
      message: 'load-balancer-api-external: tcp connection to a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:55:14Z"
    - latency: 8.712264ms
      message: 'load-balancer-api-external: resolved host name a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:55:14Z"
    - latency: 4.740034ms
      message: 'load-balancer-api-external: tcp connection to a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:54:14Z"
    - latency: 9.468803ms
      message: 'load-balancer-api-external: resolved host name a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:54:14Z"
    - latency: 6.061177ms
      message: 'load-balancer-api-external: tcp connection to a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:53:14Z"
    - latency: 8.167101ms
      message: 'load-balancer-api-external: resolved host name a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:53:14Z"
    - latency: 16.001246ms
      message: 'load-balancer-api-external: tcp connection to a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:52:14Z"
    - latency: 8.11058ms
      message: 'load-balancer-api-external: resolved host name a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:52:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T14:50:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-166-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-166.ec2.internal
      uid: 5bc40b26-c2e3-4625-bef2-374a44157e40
    resourceVersion: "22094"
    uid: 9e8c1b37-4c01-4507-96db-6d2b882b90d9
  spec:
    sourcePod: network-check-source-56d84b9f44-4hxsn
    targetEndpoint: a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T14:56:14Z"
      message: 'load-balancer-api-internal: tcp connection to a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.21814ms
      message: 'load-balancer-api-internal: tcp connection to a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:56:14Z"
    - latency: 12.470579ms
      message: 'load-balancer-api-internal: resolved host name a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:56:14Z"
    - latency: 4.209085ms
      message: 'load-balancer-api-internal: tcp connection to a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:55:14Z"
    - latency: 8.644451ms
      message: 'load-balancer-api-internal: resolved host name a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:55:14Z"
    - latency: 4.800256ms
      message: 'load-balancer-api-internal: tcp connection to a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:54:14Z"
    - latency: 9.430776ms
      message: 'load-balancer-api-internal: resolved host name a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:54:14Z"
    - latency: 5.799884ms
      message: 'load-balancer-api-internal: tcp connection to a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:53:14Z"
    - latency: 8.081988ms
      message: 'load-balancer-api-internal: resolved host name a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:53:14Z"
    - latency: 4.655415ms
      message: 'load-balancer-api-internal: tcp connection to a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:52:14Z"
    - latency: 8.038044ms
      message: 'load-balancer-api-internal: resolved host name a8ceb50d8a6c94c49a06b0cf92ea69ad-005b205a8490249f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:52:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T14:50:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-166-to-network-check-target-ip-10-0-129-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-166.ec2.internal
      uid: 5bc40b26-c2e3-4625-bef2-374a44157e40
    resourceVersion: "23149"
    uid: 31bc6507-261c-4f5c-96fe-5146b6b51c78
  spec:
    sourcePod: network-check-source-56d84b9f44-4hxsn
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T14:57:14Z"
      message: 'network-check-target-ip-10-0-129-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.005181ms
      message: 'network-check-target-ip-10-0-129-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:57:14Z"
    - latency: 2.136111ms
      message: 'network-check-target-ip-10-0-129-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:56:14Z"
    - latency: 1.615607ms
      message: 'network-check-target-ip-10-0-129-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:55:14Z"
    - latency: 1.962769ms
      message: 'network-check-target-ip-10-0-129-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:54:14Z"
    - latency: 1.834424ms
      message: 'network-check-target-ip-10-0-129-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:53:14Z"
    - latency: 1.868241ms
      message: 'network-check-target-ip-10-0-129-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:52:14Z"
    - latency: 2.418346ms
      message: 'network-check-target-ip-10-0-129-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:51:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T14:50:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-166-to-network-check-target-ip-10-0-130-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-166.ec2.internal
      uid: 5bc40b26-c2e3-4625-bef2-374a44157e40
    resourceVersion: "23148"
    uid: 48cad6df-d089-4805-841b-4b8a25f33857
  spec:
    sourcePod: network-check-source-56d84b9f44-4hxsn
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T14:57:14Z"
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 878.398µs
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:57:14Z"
    - latency: 953.251µs
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:56:14Z"
    - latency: 844.629µs
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:55:14Z"
    - latency: 1.208731ms
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:54:14Z"
    - latency: 856.583µs
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:53:14Z"
    - latency: 910.653µs
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:52:14Z"
    - latency: 1.324829ms
      message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:51:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T14:50:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-166-to-network-check-target-ip-10-0-142-169
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-166.ec2.internal
      uid: 5bc40b26-c2e3-4625-bef2-374a44157e40
    resourceVersion: "23150"
    uid: 6c6b034f-3616-4083-9921-0596a7dbfac6
  spec:
    sourcePod: network-check-source-56d84b9f44-4hxsn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T14:57:14Z"
      message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.047425ms
      message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:57:14Z"
    - latency: 2.585815ms
      message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:56:14Z"
    - latency: 2.008657ms
      message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:55:14Z"
    - latency: 2.136133ms
      message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:54:14Z"
    - latency: 1.962777ms
      message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:53:14Z"
    - latency: 2.027483ms
      message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:52:14Z"
    - latency: 2.711534ms
      message: 'network-check-target-ip-10-0-142-169: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:51:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-29T14:50:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-166-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-166.ec2.internal
      uid: 5bc40b26-c2e3-4625-bef2-374a44157e40
    resourceVersion: "22093"
    uid: cde3ea9b-74ab-456e-a9e3-91ea9318a895
  spec:
    sourcePod: network-check-source-56d84b9f44-4hxsn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-29T14:56:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 865.061µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:56:14Z"
    - latency: 1.717618ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:56:14Z"
    - latency: 780.074µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:55:14Z"
    - latency: 2.061538ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:55:14Z"
    - latency: 797.663µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:54:14Z"
    - latency: 1.918225ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:54:14Z"
    - latency: 928.33µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:53:14Z"
    - latency: 1.643535ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:53:14Z"
    - latency: 933.316µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-29T14:52:14Z"
    - latency: 1.637146ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-29T14:52:14Z"
kind: List
metadata:
  resourceVersion: ""