apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:15:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-168-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-168.ec2.internal
      uid: 2682d132-afbe-4c84-837b-16e46b7f25c8
    resourceVersion: "14591"
    uid: 5505739f-091b-48cd-8a83-ff996bac18c1
  spec:
    sourcePod: network-check-source-8894fc9bd-lnq2b
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:22:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 912.894µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:22:06Z"
    - latency: 820.817µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:21:06Z"
    - latency: 876.012µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:20:06Z"
    - latency: 838.662µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:19:06Z"
    - latency: 809.171µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:18:06Z"
    - latency: 1.149596ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:17:06Z"
    - latency: 879.498µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:16:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:15:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-168-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-168.ec2.internal
      uid: 2682d132-afbe-4c84-837b-16e46b7f25c8
    resourceVersion: "14169"
    uid: 17945f9b-b3de-4fd7-bb4f-9d09027bdb84
  spec:
    sourcePod: network-check-source-8894fc9bd-lnq2b
    targetEndpoint: ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:21:06Z"
      message: 'load-balancer-api-external: tcp connection to ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.293204ms
      message: 'load-balancer-api-external: tcp connection to ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:21:06Z"
    - latency: 8.413329ms
      message: 'load-balancer-api-external: resolved host name ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:21:06Z"
    - latency: 5.079015ms
      message: 'load-balancer-api-external: tcp connection to ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:20:06Z"
    - latency: 7.64834ms
      message: 'load-balancer-api-external: resolved host name ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:20:06Z"
    - latency: 5.168976ms
      message: 'load-balancer-api-external: tcp connection to ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:19:06Z"
    - latency: 6.646526ms
      message: 'load-balancer-api-external: resolved host name ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:19:06Z"
    - latency: 3.766302ms
      message: 'load-balancer-api-external: tcp connection to ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:18:06Z"
    - latency: 7.912965ms
      message: 'load-balancer-api-external: resolved host name ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:18:06Z"
    - latency: 4.899311ms
      message: 'load-balancer-api-external: tcp connection to ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:17:06Z"
    - latency: 9.235646ms
      message: 'load-balancer-api-external: resolved host name ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:17:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:15:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-168-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-168.ec2.internal
      uid: 2682d132-afbe-4c84-837b-16e46b7f25c8
    resourceVersion: "14170"
    uid: aad36fcd-1ed7-4d9a-9397-573356d9fbc9
  spec:
    sourcePod: network-check-source-8894fc9bd-lnq2b
    targetEndpoint: ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:21:06Z"
      message: 'load-balancer-api-internal: tcp connection to ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.004019ms
      message: 'load-balancer-api-internal: tcp connection to ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:21:06Z"
    - latency: 8.460467ms
      message: 'load-balancer-api-internal: resolved host name ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:21:06Z"
    - latency: 5.062582ms
      message: 'load-balancer-api-internal: tcp connection to ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:20:06Z"
    - latency: 7.608356ms
      message: 'load-balancer-api-internal: resolved host name ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:20:06Z"
    - latency: 5.1935ms
      message: 'load-balancer-api-internal: tcp connection to ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:19:06Z"
    - latency: 6.549606ms
      message: 'load-balancer-api-internal: resolved host name ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:19:06Z"
    - latency: 4.917463ms
      message: 'load-balancer-api-internal: tcp connection to ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:18:06Z"
    - latency: 7.876094ms
      message: 'load-balancer-api-internal: resolved host name ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:18:06Z"
    - latency: 4.907951ms
      message: 'load-balancer-api-internal: tcp connection to ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:17:06Z"
    - latency: 9.130831ms
      message: 'load-balancer-api-internal: resolved host name ad4dc090bbdee4a7ea8c3b83520e0b64-bc05896aa29879c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:17:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:15:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-168-to-network-check-target-ip-10-0-131-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-168.ec2.internal
      uid: 2682d132-afbe-4c84-837b-16e46b7f25c8
    resourceVersion: "14590"
    uid: 6ea03952-76ec-485b-b6bb-bff4b01202e1
  spec:
    sourcePod: network-check-source-8894fc9bd-lnq2b
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:22:06Z"
      message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.728655ms
      message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:22:06Z"
    - latency: 2.905804ms
      message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:21:06Z"
    - latency: 2.045659ms
      message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:20:06Z"
    - latency: 2.062085ms
      message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:19:06Z"
    - latency: 2.202199ms
      message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:18:06Z"
    - latency: 2.131233ms
      message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:17:06Z"
    - latency: 2.378265ms
      message: 'network-check-target-ip-10-0-131-11: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:16:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:15:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-168-to-network-check-target-ip-10-0-137-168
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-168.ec2.internal
      uid: 2682d132-afbe-4c84-837b-16e46b7f25c8
    resourceVersion: "14588"
    uid: e7396a39-b2a7-4585-9682-73476b5ee0d2
  spec:
    sourcePod: network-check-source-8894fc9bd-lnq2b
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:22:06Z"
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 915.537µs
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:22:06Z"
    - latency: 835.123µs
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:21:06Z"
    - latency: 911.399µs
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:20:06Z"
    - latency: 952.194µs
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:19:06Z"
    - latency: 1.278116ms
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:18:06Z"
    - latency: 1.072539ms
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:17:06Z"
    - latency: 1.585623ms
      message: 'network-check-target-ip-10-0-137-168: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:16:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:15:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-168-to-network-check-target-ip-10-0-143-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-168.ec2.internal
      uid: 2682d132-afbe-4c84-837b-16e46b7f25c8
    resourceVersion: "14589"
    uid: 68036094-775d-4670-9637-56c79521f290
  spec:
    sourcePod: network-check-source-8894fc9bd-lnq2b
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:22:06Z"
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.230634ms
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:22:06Z"
    - latency: 2.292924ms
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:21:06Z"
    - latency: 1.980187ms
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:20:06Z"
    - latency: 2.177659ms
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:19:06Z"
    - latency: 2.121714ms
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:18:06Z"
    - latency: 1.994623ms
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:17:06Z"
    - latency: 2.300192ms
      message: 'network-check-target-ip-10-0-143-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:16:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:15:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-168-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-168.ec2.internal
      uid: 2682d132-afbe-4c84-837b-16e46b7f25c8
    resourceVersion: "14168"
    uid: 90b62b3d-8cb8-456a-8478-3eb8ff734903
  spec:
    sourcePod: network-check-source-8894fc9bd-lnq2b
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:21:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 996.613µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:21:06Z"
    - latency: 2.575472ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:21:06Z"
    - latency: 801.63µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:20:06Z"
    - latency: 1.806267ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:20:06Z"
    - latency: 940.595µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:19:06Z"
    - latency: 1.783655ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:19:06Z"
    - latency: 1.004121ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:18:06Z"
    - latency: 1.843569ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:18:06Z"
    - latency: 810.277µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:17:06Z"
    - latency: 1.811061ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:17:06Z"
kind: List
metadata:
  resourceVersion: ""