apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T15:20:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-228-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-228.ec2.internal
      uid: a3cbf84e-98d5-411d-bd26-726af63f68a9
    resourceVersion: "15864"
    uid: 6b807c17-18cc-4856-b4d1-c9451cf5a94e
  spec:
    sourcePod: network-check-source-8894fc9bd-g7h5c
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T15:27:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.015599ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:27:16Z"
    - latency: 1.063555ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:26:16Z"
    - latency: 1.078275ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:25:16Z"
    - latency: 830.059µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:24:16Z"
    - latency: 862.409µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:23:16Z"
    - latency: 1.089657ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:22:16Z"
    - latency: 1.436778ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:21:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T15:20:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-228-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-228.ec2.internal
      uid: a3cbf84e-98d5-411d-bd26-726af63f68a9
    resourceVersion: "15519"
    uid: 7525d1a1-fca4-4bb9-b8ab-606201f93a77
  spec:
    sourcePod: network-check-source-8894fc9bd-g7h5c
    targetEndpoint: a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T15:26:16Z"
      message: 'load-balancer-api-external: tcp connection to a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.915874ms
      message: 'load-balancer-api-external: tcp connection to a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:26:16Z"
    - latency: 7.746723ms
      message: 'load-balancer-api-external: resolved host name a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:26:16Z"
    - latency: 4.813808ms
      message: 'load-balancer-api-external: tcp connection to a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:25:16Z"
    - latency: 9.074434ms
      message: 'load-balancer-api-external: resolved host name a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:25:16Z"
    - latency: 4.666784ms
      message: 'load-balancer-api-external: tcp connection to a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:24:16Z"
    - latency: 9.942261ms
      message: 'load-balancer-api-external: resolved host name a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:24:16Z"
    - latency: 4.71936ms
      message: 'load-balancer-api-external: tcp connection to a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:23:16Z"
    - latency: 10.751317ms
      message: 'load-balancer-api-external: resolved host name a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:23:16Z"
    - latency: 6.128489ms
      message: 'load-balancer-api-external: tcp connection to a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:22:16Z"
    - latency: 8.521076ms
      message: 'load-balancer-api-external: resolved host name a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:22:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T15:20:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-228-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-228.ec2.internal
      uid: a3cbf84e-98d5-411d-bd26-726af63f68a9
    resourceVersion: "15518"
    uid: 72e89bed-c5f3-49b6-81b6-1f4524bf105e
  spec:
    sourcePod: network-check-source-8894fc9bd-g7h5c
    targetEndpoint: a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T15:26:16Z"
      message: 'load-balancer-api-internal: tcp connection to a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.960742ms
      message: 'load-balancer-api-internal: tcp connection to a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:26:16Z"
    - latency: 7.682815ms
      message: 'load-balancer-api-internal: resolved host name a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:26:16Z"
    - latency: 4.888311ms
      message: 'load-balancer-api-internal: tcp connection to a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:25:16Z"
    - latency: 9.032118ms
      message: 'load-balancer-api-internal: resolved host name a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:25:16Z"
    - latency: 4.713961ms
      message: 'load-balancer-api-internal: tcp connection to a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:24:16Z"
    - latency: 9.893145ms
      message: 'load-balancer-api-internal: resolved host name a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:24:16Z"
    - latency: 4.714591ms
      message: 'load-balancer-api-internal: tcp connection to a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:23:16Z"
    - latency: 10.693011ms
      message: 'load-balancer-api-internal: resolved host name a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:23:16Z"
    - latency: 5.931112ms
      message: 'load-balancer-api-internal: tcp connection to a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:22:16Z"
    - latency: 8.356815ms
      message: 'load-balancer-api-internal: resolved host name a8b6ae6b2229a4fd4a0e3931efee7f01-60bc2ba615638310.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:22:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T15:20:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-228-to-network-check-target-ip-10-0-134-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-228.ec2.internal
      uid: a3cbf84e-98d5-411d-bd26-726af63f68a9
    resourceVersion: "15863"
    uid: 94bff8a9-95b6-4e92-baef-a251b318eeb1
  spec:
    sourcePod: network-check-source-8894fc9bd-g7h5c
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T15:27:16Z"
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.030174ms
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:27:16Z"
    - latency: 2.703765ms
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:26:16Z"
    - latency: 2.131017ms
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:25:16Z"
    - latency: 2.185721ms
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:24:16Z"
    - latency: 2.136408ms
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:23:16Z"
    - latency: 1.943677ms
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:22:16Z"
    - latency: 2.617054ms
      message: 'network-check-target-ip-10-0-134-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:21:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T15:20:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-228-to-network-check-target-ip-10-0-137-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-228.ec2.internal
      uid: a3cbf84e-98d5-411d-bd26-726af63f68a9
    resourceVersion: "15861"
    uid: 6fce32cc-9681-402c-ad5f-2aa8a371292f
  spec:
    sourcePod: network-check-source-8894fc9bd-g7h5c
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T15:27:16Z"
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.572798ms
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:27:16Z"
    - latency: 1.255323ms
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:26:16Z"
    - latency: 936.679µs
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:25:16Z"
    - latency: 809.273µs
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:24:16Z"
    - latency: 1.29024ms
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:23:16Z"
    - latency: 1.063513ms
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:22:16Z"
    - latency: 2.007477ms
      message: 'network-check-target-ip-10-0-137-228: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:21:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T15:20:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-228-to-network-check-target-ip-10-0-141-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-228.ec2.internal
      uid: a3cbf84e-98d5-411d-bd26-726af63f68a9
    resourceVersion: "15862"
    uid: 918eae7c-9a1d-4336-84a0-a28bfc825782
  spec:
    sourcePod: network-check-source-8894fc9bd-g7h5c
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T15:27:16Z"
      message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.573321ms
      message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:27:16Z"
    - latency: 2.425725ms
      message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:26:16Z"
    - latency: 2.268018ms
      message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:25:16Z"
    - latency: 2.113049ms
      message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:24:16Z"
    - latency: 2.04719ms
      message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:23:16Z"
    - latency: 2.212068ms
      message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:22:16Z"
    - latency: 2.921236ms
      message: 'network-check-target-ip-10-0-141-167: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:21:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T15:20:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-228-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-228.ec2.internal
      uid: a3cbf84e-98d5-411d-bd26-726af63f68a9
    resourceVersion: "15517"
    uid: 235fe1c0-8e0b-412f-ace4-a39ee022083b
  spec:
    sourcePod: network-check-source-8894fc9bd-g7h5c
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T15:26:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 735.444µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:26:16Z"
    - latency: 1.832279ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:26:16Z"
    - latency: 875.341µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:25:16Z"
    - latency: 1.631455ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:25:16Z"
    - latency: 1.061417ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:24:16Z"
    - latency: 1.703128ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:24:16Z"
    - latency: 875.293µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:23:16Z"
    - latency: 1.894064ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:23:16Z"
    - latency: 1.032971ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T15:22:16Z"
    - latency: 1.832481ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T15:22:16Z"
kind: List
metadata:
  resourceVersion: ""