apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-114-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-114.ec2.internal uid: eec04970-0c56-4e26-a3e7-d09bfd2704a2 resourceVersion: "55770" uid: 9cbc2236-3a0f-4b91-a64a-113e938eaf95 spec: sourcePod: network-check-source-869dcfcdcd-pzpbf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T16:26:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 943.689µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:54:45Z" - latency: 901.46µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:53:45Z" - latency: 1.018473ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:52:45Z" - latency: 1.132327ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:51:45Z" - latency: 1.210069ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:50:45Z" - latency: 1.402086ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:49:45Z" - latency: 1.014155ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:48:45Z" - latency: 1.798833ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:47:45Z" - latency: 1.060842ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:46:45Z" - latency: 1.213243ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:45:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-114-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-114.ec2.internal uid: eec04970-0c56-4e26-a3e7-d09bfd2704a2 resourceVersion: "56797" uid: b810b7d3-0b7f-43f8-9e0f-85a67ed26d80 spec: sourcePod: network-check-source-869dcfcdcd-pzpbf targetEndpoint: ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T16:25:45Z" message: 'load-balancer-api-external: tcp connection to ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.578402ms message: 'load-balancer-api-external: tcp connection to ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:55:45Z" - latency: 8.839301ms message: 'load-balancer-api-external: resolved host name ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:55:45Z" - latency: 4.537817ms message: 'load-balancer-api-external: tcp connection to ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:54:45Z" - latency: 10.28714ms message: 'load-balancer-api-external: resolved host name ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:54:45Z" - latency: 4.869819ms message: 'load-balancer-api-external: tcp connection to ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:53:45Z" - latency: 7.407853ms message: 'load-balancer-api-external: resolved host name ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:53:45Z" - latency: 6.309066ms message: 'load-balancer-api-external: tcp connection to ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:52:45Z" - latency: 8.501956ms message: 'load-balancer-api-external: resolved host name ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:52:45Z" - latency: 4.879106ms message: 'load-balancer-api-external: tcp connection to ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:51:45Z" - latency: 8.29055ms message: 'load-balancer-api-external: resolved host name ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:51:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-114-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-114.ec2.internal uid: eec04970-0c56-4e26-a3e7-d09bfd2704a2 resourceVersion: "56798" uid: 5d246f55-f868-4605-8fd8-4a3fd1d7ca23 spec: sourcePod: network-check-source-869dcfcdcd-pzpbf targetEndpoint: ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T16:25:45Z" message: 'load-balancer-api-internal: tcp connection to ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.064349ms message: 'load-balancer-api-internal: tcp connection to ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:55:45Z" - latency: 8.788644ms message: 'load-balancer-api-internal: resolved host name ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:55:45Z" - latency: 4.867769ms message: 'load-balancer-api-internal: tcp connection to ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:54:45Z" - latency: 10.313242ms message: 'load-balancer-api-internal: resolved host name ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:54:45Z" - latency: 4.70222ms message: 'load-balancer-api-internal: tcp connection to ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:53:45Z" - latency: 7.451646ms message: 'load-balancer-api-internal: resolved host name ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:53:45Z" - latency: 6.372239ms message: 'load-balancer-api-internal: tcp connection to ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:52:45Z" - latency: 8.554955ms message: 'load-balancer-api-internal: resolved host name ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:52:45Z" - latency: 4.864751ms message: 'load-balancer-api-internal: tcp connection to ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:51:45Z" - latency: 8.376194ms message: 'load-balancer-api-internal: resolved host name ac919d41495924968a6c17bdb66743d0-856a28e8840aa0e9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T16:51:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-114-to-network-check-target-ip-10-0-135-114 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-114.ec2.internal uid: eec04970-0c56-4e26-a3e7-d09bfd2704a2 resourceVersion: "55767" uid: 2c6f0637-ad03-44b7-8fa7-b3f2468c95cc spec: sourcePod: network-check-source-869dcfcdcd-pzpbf targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T16:26:45Z" message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.027192ms message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:54:45Z" - latency: 1.031884ms message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:53:45Z" - latency: 924.967µs message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:52:45Z" - latency: 888.803µs message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:51:45Z" - latency: 1.084615ms message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:50:45Z" - latency: 1.58652ms message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:49:45Z" - latency: 1.392821ms message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:48:45Z" - latency: 969.994µs message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:47:45Z" - latency: 1.301274ms message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:46:45Z" - latency: 848.288µs message: 'network-check-target-ip-10-0-135-114: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:45:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-114-to-network-check-target-ip-10-0-139-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-114.ec2.internal uid: eec04970-0c56-4e26-a3e7-d09bfd2704a2 resourceVersion: "55768" uid: 812c539e-53c4-44dc-befe-f23929ca4de7 spec: sourcePod: network-check-source-869dcfcdcd-pzpbf targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T16:26:45Z" message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.269089ms message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:54:45Z" - latency: 2.311345ms message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:53:45Z" - latency: 1.944158ms message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:52:45Z" - latency: 2.306863ms message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:51:45Z" - latency: 2.946456ms message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:50:45Z" - latency: 2.450623ms message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:49:45Z" - latency: 2.3515ms message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:48:45Z" - latency: 2.214937ms message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:47:45Z" - latency: 2.30952ms message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:46:45Z" - latency: 2.064586ms message: 'network-check-target-ip-10-0-139-93: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:45:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-114-to-network-check-target-ip-10-0-140-120 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-114.ec2.internal uid: eec04970-0c56-4e26-a3e7-d09bfd2704a2 resourceVersion: "55769" uid: c01a3bcc-b90d-40e3-97c4-abf05547ce18 spec: sourcePod: network-check-source-869dcfcdcd-pzpbf targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T16:26:45Z" message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.879461ms message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:54:45Z" - latency: 1.84633ms message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:53:45Z" - latency: 1.861754ms message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:52:45Z" - latency: 1.912734ms message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:51:45Z" - latency: 1.958571ms message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:50:45Z" - latency: 1.9163ms message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:49:45Z" - latency: 1.947148ms message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:48:45Z" - latency: 1.919698ms message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:47:45Z" - latency: 1.936509ms message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:46:45Z" - latency: 1.817507ms message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:45:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:19:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-114-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-114.ec2.internal uid: eec04970-0c56-4e26-a3e7-d09bfd2704a2 resourceVersion: "56796" uid: 17e31082-6b77-4422-9b18-902f11590ba4 spec: sourcePod: network-check-source-869dcfcdcd-pzpbf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T16:25:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 887.687µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:55:45Z" - latency: 1.997112ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T16:55:45Z" - latency: 935.169µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:54:45Z" - latency: 2.45963ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T16:54:45Z" - latency: 801.191µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:53:45Z" - latency: 2.483954ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T16:53:45Z" - latency: 954.665µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:52:45Z" - latency: 1.983846ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T16:52:45Z" - latency: 1.07468ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T16:51:45Z" - latency: 1.843177ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T16:51:45Z" kind: List metadata: resourceVersion: ""