apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:29:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-16-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-16.ec2.internal uid: 1fe1753a-bf0d-429c-8113-56dbeead7d0d resourceVersion: "37196" uid: 44e40073-5e0f-49e7-9a9e-97dbc22f7b26 spec: sourcePod: network-check-source-869dcfcdcd-zgwwr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-13T18:36:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.046968ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:50:35Z" - latency: 913.404µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:49:35Z" - latency: 1.267025ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:48:35Z" - latency: 1.10207ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:47:35Z" - latency: 956.982µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:46:35Z" - latency: 944.193µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:45:35Z" - latency: 952.872µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:44:35Z" - latency: 1.26804ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:43:35Z" - latency: 858.742µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:42:35Z" - latency: 993.387µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:41:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:29:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-16-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-16.ec2.internal uid: 1fe1753a-bf0d-429c-8113-56dbeead7d0d resourceVersion: "34716" uid: 70843f19-83c9-402b-aa5b-f99e7b8c204d spec: sourcePod: network-check-source-869dcfcdcd-zgwwr targetEndpoint: ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T18:35:35Z" message: 'load-balancer-api-external: tcp connection to ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.587222ms message: 'load-balancer-api-external: tcp connection to ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:47:35Z" - latency: 7.213806ms message: 'load-balancer-api-external: resolved host name ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:47:35Z" - latency: 3.852758ms message: 'load-balancer-api-external: tcp connection to ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:46:35Z" - latency: 8.515178ms message: 'load-balancer-api-external: resolved host name ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:46:35Z" - latency: 4.865231ms message: 'load-balancer-api-external: tcp connection to ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:45:35Z" - latency: 9.438545ms message: 'load-balancer-api-external: resolved host name ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:45:35Z" - latency: 4.036931ms message: 'load-balancer-api-external: tcp connection to ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:44:35Z" - latency: 7.672154ms message: 'load-balancer-api-external: resolved host name ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:44:35Z" - latency: 4.769801ms message: 'load-balancer-api-external: tcp connection to ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:43:35Z" - latency: 7.130861ms message: 'load-balancer-api-external: resolved host name ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:43:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:29:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-16-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-16.ec2.internal uid: 1fe1753a-bf0d-429c-8113-56dbeead7d0d resourceVersion: "34715" uid: 6ce18b99-9e6e-4b9a-b924-37ac9254233f spec: sourcePod: network-check-source-869dcfcdcd-zgwwr targetEndpoint: ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-13T18:35:35Z" message: 'load-balancer-api-internal: tcp connection to ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.597877ms message: 'load-balancer-api-internal: tcp connection to ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:47:35Z" - latency: 7.290319ms message: 'load-balancer-api-internal: resolved host name ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:47:35Z" - latency: 3.915618ms message: 'load-balancer-api-internal: tcp connection to ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:46:35Z" - latency: 8.553528ms message: 'load-balancer-api-internal: resolved host name ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:46:35Z" - latency: 4.433405ms message: 'load-balancer-api-internal: tcp connection to ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:45:35Z" - latency: 9.296815ms message: 'load-balancer-api-internal: resolved host name ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:45:35Z" - latency: 4.098132ms message: 'load-balancer-api-internal: tcp connection to ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:44:35Z" - latency: 7.585267ms message: 'load-balancer-api-internal: resolved host name ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:44:35Z" - latency: 4.751643ms message: 'load-balancer-api-internal: tcp connection to ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:43:35Z" - latency: 6.880757ms message: 'load-balancer-api-internal: resolved host name ae9cc4259a97e432e8d1783235e5e3d8-5abda1782ede050a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-13T18:43:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:29:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-16-to-network-check-target-ip-10-0-132-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-16.ec2.internal uid: 1fe1753a-bf0d-429c-8113-56dbeead7d0d resourceVersion: "37195" uid: c7015e0f-8f73-494b-bc26-6199ca86a60d spec: sourcePod: network-check-source-869dcfcdcd-zgwwr targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-13T18:36:35Z" message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.663928ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:50:35Z" - latency: 1.086523ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:49:35Z" - latency: 849.456µs message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:48:35Z" - latency: 1.30648ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:47:35Z" - latency: 943.927µs message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:46:35Z" - latency: 909.683µs message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:45:35Z" - latency: 857.298µs message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:44:35Z" - latency: 925.56µs message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:43:35Z" - latency: 1.375909ms message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:42:35Z" - latency: 945.979µs message: 'network-check-target-ip-10-0-132-16: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:41:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:29:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-16-to-network-check-target-ip-10-0-135-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-16.ec2.internal uid: 1fe1753a-bf0d-429c-8113-56dbeead7d0d resourceVersion: "37194" uid: 36993777-3479-4c5a-a2db-091a473a4072 spec: sourcePod: network-check-source-869dcfcdcd-zgwwr targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T18:36:35Z" message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.524014ms message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:50:35Z" - latency: 2.293508ms message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:49:35Z" - latency: 1.999707ms message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:48:35Z" - latency: 2.200207ms message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:47:35Z" - latency: 2.100513ms message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:46:35Z" - latency: 2.490078ms message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:45:35Z" - latency: 2.331459ms message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:44:35Z" - latency: 2.281079ms message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:43:35Z" - latency: 2.07158ms message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:42:35Z" - latency: 2.099949ms message: 'network-check-target-ip-10-0-135-6: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:41:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:29:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-16-to-network-check-target-ip-10-0-139-231 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-16.ec2.internal uid: 1fe1753a-bf0d-429c-8113-56dbeead7d0d resourceVersion: "37193" uid: a9b84387-a92b-44c0-a2ab-4d2f46f911a0 spec: sourcePod: network-check-source-869dcfcdcd-zgwwr targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-13T18:36:35Z" message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.546753ms message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:50:35Z" - latency: 2.624377ms message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:49:35Z" - latency: 2.523155ms message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:48:35Z" - latency: 2.702669ms message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:47:35Z" - latency: 2.56417ms message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:46:35Z" - latency: 2.916674ms message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:45:35Z" - latency: 2.597708ms message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:44:35Z" - latency: 2.541958ms message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:43:35Z" - latency: 2.526919ms message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:42:35Z" - latency: 2.412069ms message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:41:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-13T18:29:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-16-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-16.ec2.internal uid: 1fe1753a-bf0d-429c-8113-56dbeead7d0d resourceVersion: "34714" uid: 253b2830-3719-4a5f-b484-2b6890bfe44f spec: sourcePod: network-check-source-869dcfcdcd-zgwwr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-13T18:35:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.164813ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:47:35Z" - latency: 1.71063ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T18:47:35Z" - latency: 1.476475ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:46:35Z" - latency: 1.8103ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T18:46:35Z" - latency: 1.060141ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:45:35Z" - latency: 1.709563ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T18:45:35Z" - latency: 956.193µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:44:35Z" - latency: 1.600232ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T18:44:35Z" - latency: 871.513µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-13T18:43:35Z" - latency: 1.827319ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-13T18:43:35Z" kind: List metadata: resourceVersion: ""