apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-66-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-66.ec2.internal
      uid: 7d16371a-7965-4816-9dc1-cea339da8a91
    resourceVersion: "14888"
    uid: 37986bb3-d37b-4878-8b84-9bfe9aa8880a
  spec:
    sourcePod: network-check-source-56d84b9f44-8gsbp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:27: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.05539ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:27:38Z"
    - latency: 899.015µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:26:38Z"
    - latency: 870.483µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:25:38Z"
    - latency: 885.306µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:24:38Z"
    - latency: 1.053452ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:23:38Z"
    - latency: 1.068891ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:22:38Z"
    - latency: 1.059125ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:21:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-66-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-66.ec2.internal
      uid: 7d16371a-7965-4816-9dc1-cea339da8a91
    resourceVersion: "14493"
    uid: 19e6d0da-ab8f-447d-ac23-a8e2c8fc0746
  spec:
    sourcePod: network-check-source-56d84b9f44-8gsbp
    targetEndpoint: ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:26:38Z"
      message: 'load-balancer-api-external: tcp connection to ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.186698ms
      message: 'load-balancer-api-external: tcp connection to ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:26:38Z"
    - latency: 6.927192ms
      message: 'load-balancer-api-external: resolved host name ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:26:38Z"
    - latency: 6.01618ms
      message: 'load-balancer-api-external: tcp connection to ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:25:38Z"
    - latency: 5.914194ms
      message: 'load-balancer-api-external: resolved host name ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:25:38Z"
    - latency: 6.305272ms
      message: 'load-balancer-api-external: tcp connection to ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:24:38Z"
    - latency: 6.670814ms
      message: 'load-balancer-api-external: resolved host name ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:24:38Z"
    - latency: 5.425979ms
      message: 'load-balancer-api-external: tcp connection to ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:23:38Z"
    - latency: 8.067982ms
      message: 'load-balancer-api-external: resolved host name ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:23:38Z"
    - latency: 6.128794ms
      message: 'load-balancer-api-external: tcp connection to ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:22:38Z"
    - latency: 10.071441ms
      message: 'load-balancer-api-external: resolved host name ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:22:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-66-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-66.ec2.internal
      uid: 7d16371a-7965-4816-9dc1-cea339da8a91
    resourceVersion: "14492"
    uid: 39ea3319-43d2-40d1-b317-8d16eae56ce1
  spec:
    sourcePod: network-check-source-56d84b9f44-8gsbp
    targetEndpoint: ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:26:38Z"
      message: 'load-balancer-api-internal: tcp connection to ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.175096ms
      message: 'load-balancer-api-internal: tcp connection to ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:26:38Z"
    - latency: 6.841204ms
      message: 'load-balancer-api-internal: resolved host name ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:26:38Z"
    - latency: 8.615355ms
      message: 'load-balancer-api-internal: tcp connection to ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:25:38Z"
    - latency: 5.951667ms
      message: 'load-balancer-api-internal: resolved host name ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:25:38Z"
    - latency: 7.176881ms
      message: 'load-balancer-api-internal: tcp connection to ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:24:38Z"
    - latency: 6.731627ms
      message: 'load-balancer-api-internal: resolved host name ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:24:38Z"
    - latency: 9.884298ms
      message: 'load-balancer-api-internal: tcp connection to ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:23:38Z"
    - latency: 8.001381ms
      message: 'load-balancer-api-internal: resolved host name ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:23:38Z"
    - latency: 6.28224ms
      message: 'load-balancer-api-internal: tcp connection to ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:22:38Z"
    - latency: 10.040482ms
      message: 'load-balancer-api-internal: resolved host name ac827ee4467044d0198cbdfebcce8119-aa91b1ecd1ee319f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:22:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-66-to-network-check-target-ip-10-0-128-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-66.ec2.internal
      uid: 7d16371a-7965-4816-9dc1-cea339da8a91
    resourceVersion: "14887"
    uid: 56c43f7b-6942-439a-9674-903b2622ad1c
  spec:
    sourcePod: network-check-source-56d84b9f44-8gsbp
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:27:38Z"
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.836597ms
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:27:38Z"
    - latency: 1.765831ms
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:26:38Z"
    - latency: 1.936027ms
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:25:38Z"
    - latency: 1.67915ms
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:24:38Z"
    - latency: 1.880696ms
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:23:38Z"
    - latency: 1.974258ms
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:22:38Z"
    - latency: 2.168065ms
      message: 'network-check-target-ip-10-0-128-172: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:21:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-66-to-network-check-target-ip-10-0-137-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-66.ec2.internal
      uid: 7d16371a-7965-4816-9dc1-cea339da8a91
    resourceVersion: "14886"
    uid: b1a62106-e522-4c47-b49f-5c2440e363e2
  spec:
    sourcePod: network-check-source-56d84b9f44-8gsbp
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:27:38Z"
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.028239ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:27:38Z"
    - latency: 2.379259ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:26:38Z"
    - latency: 2.005527ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:25:38Z"
    - latency: 2.127934ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:24:38Z"
    - latency: 2.164426ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:23:38Z"
    - latency: 1.743284ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:22:38Z"
    - latency: 2.17276ms
      message: 'network-check-target-ip-10-0-137-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:21:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:20:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-66-to-network-check-target-ip-10-0-142-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-66.ec2.internal
      uid: 7d16371a-7965-4816-9dc1-cea339da8a91
    resourceVersion: "14885"
    uid: 208bca22-5004-49f4-9cba-1b4cd943d6d0
  spec:
    sourcePod: network-check-source-56d84b9f44-8gsbp
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:27:38Z"
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 891.932µs
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:27:38Z"
    - latency: 812.688µs
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:26:38Z"
    - latency: 899.397µs
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:25:38Z"
    - latency: 900.04µs
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:24:38Z"
    - latency: 895.205µs
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:23:38Z"
    - latency: 768.005µs
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:22:38Z"
    - latency: 1.256791ms
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:21:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T15:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-66-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-66.ec2.internal
      uid: 7d16371a-7965-4816-9dc1-cea339da8a91
    resourceVersion: "14491"
    uid: 93c21615-083c-4e3b-9e37-785594b5e784
  spec:
    sourcePod: network-check-source-56d84b9f44-8gsbp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T15:26:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 896.826µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:26:38Z"
    - latency: 1.601313ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:26:38Z"
    - latency: 777.999µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:25:38Z"
    - latency: 1.581372ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:25:38Z"
    - latency: 828.066µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:24:38Z"
    - latency: 2.108224ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:24:38Z"
    - latency: 1.269459ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:23:38Z"
    - latency: 1.574015ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:23:38Z"
    - latency: 807.649µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T15:22:38Z"
    - latency: 2.058067ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T15:22:38Z"
kind: List
metadata:
  resourceVersion: ""