apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T21:19:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-174-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-174.ec2.internal
      uid: 7e964740-45c9-419d-a45c-99b565b74338
    resourceVersion: "24134"
    uid: 7ce0f9ce-8f28-404e-abda-5bc136aee065
  spec:
    sourcePod: network-check-source-8894fc9bd-7f8kn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:26:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 962.276µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:26:07Z"
    - latency: 981.048µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:25:07Z"
    - latency: 1.100361ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:24:07Z"
    - latency: 877.853µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:23:07Z"
    - latency: 1.169401ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:22:07Z"
    - latency: 847.189µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:21:07Z"
    - latency: 910.716µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:20:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T21:19:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-174-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-174.ec2.internal
      uid: 7e964740-45c9-419d-a45c-99b565b74338
    resourceVersion: "22750"
    uid: bf4cb7cf-6195-4086-aeb9-6d30f74da5cd
  spec:
    sourcePod: network-check-source-8894fc9bd-7f8kn
    targetEndpoint: aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:25:07Z"
      message: 'load-balancer-api-external: tcp connection to aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.029114ms
      message: 'load-balancer-api-external: tcp connection to aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:25:07Z"
    - latency: 7.881797ms
      message: 'load-balancer-api-external: resolved host name aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:25:07Z"
    - latency: 5.283815ms
      message: 'load-balancer-api-external: tcp connection to aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:24:07Z"
    - latency: 9.126146ms
      message: 'load-balancer-api-external: resolved host name aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:24:07Z"
    - latency: 4.514665ms
      message: 'load-balancer-api-external: tcp connection to aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:23:07Z"
    - latency: 12.494272ms
      message: 'load-balancer-api-external: resolved host name aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:23:07Z"
    - latency: 5.023298ms
      message: 'load-balancer-api-external: tcp connection to aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:22:07Z"
    - latency: 10.176216ms
      message: 'load-balancer-api-external: resolved host name aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:22:07Z"
    - latency: 4.397689ms
      message: 'load-balancer-api-external: tcp connection to aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:21:07Z"
    - latency: 8.057978ms
      message: 'load-balancer-api-external: resolved host name aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:21:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T21:19:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-174-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-174.ec2.internal
      uid: 7e964740-45c9-419d-a45c-99b565b74338
    resourceVersion: "22749"
    uid: 5884080c-adfb-4bdf-8477-a2eade012f87
  spec:
    sourcePod: network-check-source-8894fc9bd-7f8kn
    targetEndpoint: aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:25:07Z"
      message: 'load-balancer-api-internal: tcp connection to aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.032323ms
      message: 'load-balancer-api-internal: tcp connection to aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:25:07Z"
    - latency: 7.77909ms
      message: 'load-balancer-api-internal: resolved host name aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:25:07Z"
    - latency: 5.260503ms
      message: 'load-balancer-api-internal: tcp connection to aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:24:07Z"
    - latency: 9.218092ms
      message: 'load-balancer-api-internal: resolved host name aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:24:07Z"
    - latency: 5.183309ms
      message: 'load-balancer-api-internal: tcp connection to aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:23:07Z"
    - latency: 12.511552ms
      message: 'load-balancer-api-internal: resolved host name aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:23:07Z"
    - latency: 4.936316ms
      message: 'load-balancer-api-internal: tcp connection to aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:22:07Z"
    - latency: 10.206221ms
      message: 'load-balancer-api-internal: resolved host name aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:22:07Z"
    - latency: 4.387221ms
      message: 'load-balancer-api-internal: tcp connection to aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:21:07Z"
    - latency: 8.045928ms
      message: 'load-balancer-api-internal: resolved host name aa39de3c9853f48ea80fa11daef7c9c0-733bd267f588bf1f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:21:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T21:19:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-174-to-network-check-target-ip-10-0-134-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-174.ec2.internal
      uid: 7e964740-45c9-419d-a45c-99b565b74338
    resourceVersion: "24132"
    uid: e5155e73-1c00-495a-b227-299b5a231a3b
  spec:
    sourcePod: network-check-source-8894fc9bd-7f8kn
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:26:07Z"
      message: 'network-check-target-ip-10-0-134-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.268181ms
      message: 'network-check-target-ip-10-0-134-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:26:07Z"
    - latency: 2.420256ms
      message: 'network-check-target-ip-10-0-134-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:25:07Z"
    - latency: 2.265583ms
      message: 'network-check-target-ip-10-0-134-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:24:07Z"
    - latency: 2.680814ms
      message: 'network-check-target-ip-10-0-134-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:23:07Z"
    - latency: 2.416003ms
      message: 'network-check-target-ip-10-0-134-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:22:07Z"
    - latency: 2.362327ms
      message: 'network-check-target-ip-10-0-134-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:21:07Z"
    - latency: 2.629759ms
      message: 'network-check-target-ip-10-0-134-198: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:20:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T21:19:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-174-to-network-check-target-ip-10-0-135-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-174.ec2.internal
      uid: 7e964740-45c9-419d-a45c-99b565b74338
    resourceVersion: "24131"
    uid: 61a4b17c-cfd9-4c47-8584-7295896a652c
  spec:
    sourcePod: network-check-source-8894fc9bd-7f8kn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:26:07Z"
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.108222ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:26:07Z"
    - latency: 1.370836ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:25:07Z"
    - latency: 1.341651ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:24:07Z"
    - latency: 1.163731ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:23:07Z"
    - latency: 953.287µs
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:22:07Z"
    - latency: 794.208µs
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:21:07Z"
    - latency: 1.659791ms
      message: 'network-check-target-ip-10-0-135-174: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:20:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T21:19:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-174-to-network-check-target-ip-10-0-138-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-174.ec2.internal
      uid: 7e964740-45c9-419d-a45c-99b565b74338
    resourceVersion: "24133"
    uid: 221c8412-617c-42b2-afe1-1b8860c563c7
  spec:
    sourcePod: network-check-source-8894fc9bd-7f8kn
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:26:07Z"
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.200105ms
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:26:07Z"
    - latency: 2.304727ms
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:25:07Z"
    - latency: 2.43591ms
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:24:07Z"
    - latency: 2.233643ms
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:23:07Z"
    - latency: 2.246416ms
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:22:07Z"
    - latency: 2.194006ms
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:21:07Z"
    - latency: 2.348662ms
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:20:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T21:19:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-174-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-174.ec2.internal
      uid: 7e964740-45c9-419d-a45c-99b565b74338
    resourceVersion: "22748"
    uid: a8333a08-7ba4-4818-881d-27dcdc2b8524
  spec:
    sourcePod: network-check-source-8894fc9bd-7f8kn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T21:25:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 780.553µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:25:07Z"
    - latency: 1.476181ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:25:07Z"
    - latency: 781.406µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:24:07Z"
    - latency: 1.795717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:24:07Z"
    - latency: 1.323537ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:23:07Z"
    - latency: 1.610506ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:23:07Z"
    - latency: 925.937µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:22:07Z"
    - latency: 1.801899ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:22:07Z"
    - latency: 825.532µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T21:21:07Z"
    - latency: 1.68036ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T21:21:07Z"
kind: List
metadata:
  resourceVersion: ""