apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:10:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-20-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-20.ec2.internal uid: 2e85d161-5e81-44d0-9a51-b12d847816b1 resourceVersion: "33335" uid: d03044ed-6841-4cf3-a56f-c9adfdcaf296 spec: sourcePod: network-check-source-869dcfcdcd-qknbm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T18:17:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 850.925µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:52:33Z" - latency: 999.342µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:51:33Z" - latency: 840.562µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:50:33Z" - latency: 969.432µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:49:33Z" - latency: 881.15µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:48:33Z" - latency: 1.092074ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:47:33Z" - latency: 1.245217ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:46:33Z" - latency: 911.453µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:45:33Z" - latency: 935.759µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:44:33Z" - latency: 1.23651ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:43:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:10:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-20-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-20.ec2.internal uid: 2e85d161-5e81-44d0-9a51-b12d847816b1 resourceVersion: "33338" uid: a4404f73-b230-46e4-a07b-6d818af285cf spec: sourcePod: network-check-source-869dcfcdcd-qknbm targetEndpoint: a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T18:16:33Z" message: 'load-balancer-api-external: tcp connection to a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.601704ms message: 'load-balancer-api-external: tcp connection to a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:52:33Z" - latency: 8.550346ms message: 'load-balancer-api-external: resolved host name a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:52:33Z" - latency: 5.444571ms message: 'load-balancer-api-external: tcp connection to a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:51:33Z" - latency: 15.303054ms message: 'load-balancer-api-external: resolved host name a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:51:33Z" - latency: 6.259244ms message: 'load-balancer-api-external: tcp connection to a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:50:33Z" - latency: 7.670905ms message: 'load-balancer-api-external: resolved host name a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:50:33Z" - latency: 5.848515ms message: 'load-balancer-api-external: tcp connection to a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:49:33Z" - latency: 10.847294ms message: 'load-balancer-api-external: resolved host name a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:49:33Z" - latency: 4.464799ms message: 'load-balancer-api-external: tcp connection to a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:48:33Z" - latency: 9.822199ms message: 'load-balancer-api-external: resolved host name a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:48:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:10:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-20-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-20.ec2.internal uid: 2e85d161-5e81-44d0-9a51-b12d847816b1 resourceVersion: "33337" uid: e27b6168-28b6-4418-93b0-a26adcfa3bd8 spec: sourcePod: network-check-source-869dcfcdcd-qknbm targetEndpoint: a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T18:16:33Z" message: 'load-balancer-api-internal: tcp connection to a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.584967ms message: 'load-balancer-api-internal: tcp connection to a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:52:33Z" - latency: 8.525353ms message: 'load-balancer-api-internal: resolved host name a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:52:33Z" - latency: 5.398741ms message: 'load-balancer-api-internal: tcp connection to a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:51:33Z" - latency: 15.252335ms message: 'load-balancer-api-internal: resolved host name a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:51:33Z" - latency: 6.307238ms message: 'load-balancer-api-internal: tcp connection to a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:50:33Z" - latency: 7.638868ms message: 'load-balancer-api-internal: resolved host name a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:50:33Z" - latency: 5.928685ms message: 'load-balancer-api-internal: tcp connection to a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:49:33Z" - latency: 10.814138ms message: 'load-balancer-api-internal: resolved host name a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:49:33Z" - latency: 4.449816ms message: 'load-balancer-api-internal: tcp connection to a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:48:33Z" - latency: 9.78718ms message: 'load-balancer-api-internal: resolved host name a57e60d2773d84f89b3ff01436ff6869-1e6eb7d98339cd61.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T18:48:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:10:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-20-to-network-check-target-ip-10-0-132-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-20.ec2.internal uid: 2e85d161-5e81-44d0-9a51-b12d847816b1 resourceVersion: "33332" uid: a423b573-4b9e-40a1-8983-73c80ab17f8d spec: sourcePod: network-check-source-869dcfcdcd-qknbm targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:17:33Z" message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.098341ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:52:33Z" - latency: 2.636785ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:51:33Z" - latency: 2.192129ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:50:33Z" - latency: 2.420127ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:49:33Z" - latency: 2.344513ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:48:33Z" - latency: 2.265801ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:47:33Z" - latency: 1.880808ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:46:33Z" - latency: 2.31455ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:45:33Z" - latency: 1.946609ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:44:33Z" - latency: 2.686525ms message: 'network-check-target-ip-10-0-132-102: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:43:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:10:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-20-to-network-check-target-ip-10-0-138-20 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-20.ec2.internal uid: 2e85d161-5e81-44d0-9a51-b12d847816b1 resourceVersion: "33331" uid: 556bb598-85f7-4e01-9137-22888e4af3b0 spec: sourcePod: network-check-source-869dcfcdcd-qknbm targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:17:33Z" message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 903.772µs message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:52:33Z" - latency: 740.804µs message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:51:33Z" - latency: 893.022µs message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:50:33Z" - latency: 940.782µs message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:49:33Z" - latency: 928.098µs message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:48:33Z" - latency: 1.523789ms message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:47:33Z" - latency: 819.042µs message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:46:33Z" - latency: 908.042µs message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:45:33Z" - latency: 1.362113ms message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:44:33Z" - latency: 855.175µs message: 'network-check-target-ip-10-0-138-20: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:43:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:10:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-20-to-network-check-target-ip-10-0-140-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-20.ec2.internal uid: 2e85d161-5e81-44d0-9a51-b12d847816b1 resourceVersion: "33333" uid: 7d9582cc-1d94-422c-84fd-00d9098ecb2b spec: sourcePod: network-check-source-869dcfcdcd-qknbm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T18:17:33Z" message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.126266ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:52:33Z" - latency: 2.349467ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:51:33Z" - latency: 2.18644ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:50:33Z" - latency: 2.118044ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:49:33Z" - latency: 2.088795ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:48:33Z" - latency: 2.314475ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:47:33Z" - latency: 1.973934ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:46:33Z" - latency: 1.950521ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:45:33Z" - latency: 2.511737ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:44:33Z" - latency: 2.411817ms message: 'network-check-target-ip-10-0-140-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:43:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T18:10:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-20-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-20.ec2.internal uid: 2e85d161-5e81-44d0-9a51-b12d847816b1 resourceVersion: "33334" uid: 74f7a917-9ea8-4d50-83d6-6e076fb24e72 spec: sourcePod: network-check-source-869dcfcdcd-qknbm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T18:16:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 859.167µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:52:33Z" - latency: 1.741771ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:52:33Z" - latency: 1.07056ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:51:33Z" - latency: 1.74501ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:51:33Z" - latency: 821.259µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:50:33Z" - latency: 1.675017ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:50:33Z" - latency: 769.414µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:49:33Z" - latency: 2.097107ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:49:33Z" - latency: 839.165µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T18:48:33Z" - latency: 1.716656ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T18:48:33Z" kind: List metadata: resourceVersion: ""