apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T11:25:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-132-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-132.ec2.internal
      uid: 7c133621-d4ab-4661-83ce-8e26016f8362
    resourceVersion: "22856"
    uid: 82298b8b-457a-4df7-8122-92849f3390f2
  spec:
    sourcePod: network-check-source-7cbc45fddc-5nt57
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T11:32:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.05162ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:32:38Z"
    - latency: 1.03014ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:31:38Z"
    - latency: 1.314967ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:30:38Z"
    - latency: 1.35182ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:29:38Z"
    - latency: 930.358µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:28:38Z"
    - latency: 871.912µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:27:38Z"
    - latency: 1.02107ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:26:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T11:25:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-132-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-132.ec2.internal
      uid: 7c133621-d4ab-4661-83ce-8e26016f8362
    resourceVersion: "26894"
    uid: 422460fc-2eb3-4ed3-877e-bb929dff3dc2
  spec:
    sourcePod: network-check-source-7cbc45fddc-5nt57
    targetEndpoint: ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T11:31:38Z"
      message: 'load-balancer-api-external: tcp connection to ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.484743ms
      message: 'load-balancer-api-external: tcp connection to ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:37:38Z"
    - latency: 8.577918ms
      message: 'load-balancer-api-external: resolved host name ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:37:38Z"
    - latency: 5.044239ms
      message: 'load-balancer-api-external: tcp connection to ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:36:38Z"
    - latency: 7.474143ms
      message: 'load-balancer-api-external: resolved host name ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:36:38Z"
    - latency: 5.468342ms
      message: 'load-balancer-api-external: tcp connection to ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:35:38Z"
    - latency: 7.765203ms
      message: 'load-balancer-api-external: resolved host name ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:35:38Z"
    - latency: 5.436743ms
      message: 'load-balancer-api-external: tcp connection to ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:34:38Z"
    - latency: 7.254548ms
      message: 'load-balancer-api-external: resolved host name ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:34:38Z"
    - latency: 4.838377ms
      message: 'load-balancer-api-external: tcp connection to ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:33:38Z"
    - latency: 7.62513ms
      message: 'load-balancer-api-external: resolved host name ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:33:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T11:25:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-132-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-132.ec2.internal
      uid: 7c133621-d4ab-4661-83ce-8e26016f8362
    resourceVersion: "26893"
    uid: ca45454f-3a86-4317-9d5e-784562886d46
  spec:
    sourcePod: network-check-source-7cbc45fddc-5nt57
    targetEndpoint: ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T11:31:38Z"
      message: 'load-balancer-api-internal: tcp connection to ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.75478ms
      message: 'load-balancer-api-internal: tcp connection to ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:37:38Z"
    - latency: 8.48088ms
      message: 'load-balancer-api-internal: resolved host name ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:37:38Z"
    - latency: 5.058867ms
      message: 'load-balancer-api-internal: tcp connection to ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:36:38Z"
    - latency: 7.409485ms
      message: 'load-balancer-api-internal: resolved host name ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:36:38Z"
    - latency: 5.4394ms
      message: 'load-balancer-api-internal: tcp connection to ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:35:38Z"
    - latency: 7.848456ms
      message: 'load-balancer-api-internal: resolved host name ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:35:38Z"
    - latency: 6.096496ms
      message: 'load-balancer-api-internal: tcp connection to ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:34:38Z"
    - latency: 7.220958ms
      message: 'load-balancer-api-internal: resolved host name ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:34:38Z"
    - latency: 4.797632ms
      message: 'load-balancer-api-internal: tcp connection to ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:33:38Z"
    - latency: 7.70101ms
      message: 'load-balancer-api-internal: resolved host name ac14fb1a921334a2e82a4b6bf6087708-e7219f53670a75c5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:33:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T11:25:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-132-to-network-check-target-ip-10-0-135-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-132.ec2.internal
      uid: 7c133621-d4ab-4661-83ce-8e26016f8362
    resourceVersion: "22854"
    uid: a22c8712-5dd8-4a6b-a635-0f260da543ee
  spec:
    sourcePod: network-check-source-7cbc45fddc-5nt57
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T11:32:38Z"
      message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.205321ms
      message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:32:38Z"
    - latency: 2.351355ms
      message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:31:38Z"
    - latency: 2.336954ms
      message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:30:38Z"
    - latency: 2.169965ms
      message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:29:38Z"
    - latency: 1.750813ms
      message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:28:38Z"
    - latency: 2.156814ms
      message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:27:38Z"
    - latency: 2.28708ms
      message: 'network-check-target-ip-10-0-135-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:26:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T11:25:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-132-to-network-check-target-ip-10-0-140-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-132.ec2.internal
      uid: 7c133621-d4ab-4661-83ce-8e26016f8362
    resourceVersion: "22855"
    uid: 6a9e5e59-894f-459c-9ff6-f9e1a6adccbf
  spec:
    sourcePod: network-check-source-7cbc45fddc-5nt57
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T11:32:38Z"
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.47023ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:32:38Z"
    - latency: 2.362341ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:31:38Z"
    - latency: 2.644131ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:30:38Z"
    - latency: 2.944309ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:29:38Z"
    - latency: 2.186546ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:28:38Z"
    - latency: 2.351141ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:27:38Z"
    - latency: 2.499625ms
      message: 'network-check-target-ip-10-0-140-158: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:26:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T11:25:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-132-to-network-check-target-ip-10-0-142-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-132.ec2.internal
      uid: 7c133621-d4ab-4661-83ce-8e26016f8362
    resourceVersion: "22853"
    uid: c3b6cdef-e5ae-47ce-aeef-c0c184ebd130
  spec:
    sourcePod: network-check-source-7cbc45fddc-5nt57
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T11:32:38Z"
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 872.835µs
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:32:38Z"
    - latency: 922.519µs
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:31:38Z"
    - latency: 1.16898ms
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:30:38Z"
    - latency: 824.084µs
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:29:38Z"
    - latency: 1.051501ms
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:28:38Z"
    - latency: 793.841µs
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:27:38Z"
    - latency: 1.08497ms
      message: 'network-check-target-ip-10-0-142-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:26:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T11:25:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-132-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-132.ec2.internal
      uid: 7c133621-d4ab-4661-83ce-8e26016f8362
    resourceVersion: "26892"
    uid: e35e5452-9685-415e-bd14-6ef2cdaba4b6
  spec:
    sourcePod: network-check-source-7cbc45fddc-5nt57
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T11:31:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.277µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:37:38Z"
    - latency: 1.853701ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:37:38Z"
    - latency: 828.433µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:36:38Z"
    - latency: 1.537566ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:36:38Z"
    - latency: 919.98µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:35:38Z"
    - latency: 1.634879ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:35:38Z"
    - latency: 771.652µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:34:38Z"
    - latency: 1.75413ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:34:38Z"
    - latency: 876.377µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T11:33:38Z"
    - latency: 1.620562ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T11:33:38Z"
kind: List
metadata:
  resourceVersion: ""