apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T21:09:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-111-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-111.ec2.internal uid: 83c6ef52-f09b-4697-857a-32a4256a31dd resourceVersion: "30244" uid: e818f9a3-637e-4f06-b5c3-af3ee440b463 spec: sourcePod: network-check-source-dbd9cf844-qhgth targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-03T21:16:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.341182ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:23:57Z" - latency: 799.685µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:22:57Z" - latency: 1.373932ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:21:57Z" - latency: 1.183269ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:20:57Z" - latency: 949.112µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:19:57Z" - latency: 1.31236ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:18:57Z" - latency: 903.939µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:17:57Z" - latency: 1.125466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:16:57Z" - latency: 927.594µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:15:57Z" - latency: 1.065589ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:14:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T21:09:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-111-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-111.ec2.internal uid: 83c6ef52-f09b-4697-857a-32a4256a31dd resourceVersion: "28705" uid: ba87ae80-bab7-4abc-b4cf-8531d4dedf5b spec: sourcePod: network-check-source-dbd9cf844-qhgth targetEndpoint: a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T21:15:57Z" message: 'load-balancer-api-external: tcp connection to a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.209358ms message: 'load-balancer-api-external: tcp connection to a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:21:57Z" - latency: 8.798759ms message: 'load-balancer-api-external: resolved host name a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:21:57Z" - latency: 6.127393ms message: 'load-balancer-api-external: tcp connection to a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:20:57Z" - latency: 8.465176ms message: 'load-balancer-api-external: resolved host name a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:20:57Z" - latency: 4.457183ms message: 'load-balancer-api-external: tcp connection to a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:19:57Z" - latency: 8.153324ms message: 'load-balancer-api-external: resolved host name a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:19:57Z" - latency: 4.875928ms message: 'load-balancer-api-external: tcp connection to a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:18:57Z" - latency: 7.83698ms message: 'load-balancer-api-external: resolved host name a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:18:57Z" - latency: 4.718642ms message: 'load-balancer-api-external: tcp connection to a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:17:57Z" - latency: 8.761165ms message: 'load-balancer-api-external: resolved host name a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:17:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T21:09:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-111-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-111.ec2.internal uid: 83c6ef52-f09b-4697-857a-32a4256a31dd resourceVersion: "28706" uid: 0bdc358c-1caf-443b-ab52-81444f0466ca spec: sourcePod: network-check-source-dbd9cf844-qhgth targetEndpoint: a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T21:15:57Z" message: 'load-balancer-api-internal: tcp connection to a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 10.507545ms message: 'load-balancer-api-internal: tcp connection to a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:21:57Z" - latency: 8.841107ms message: 'load-balancer-api-internal: resolved host name a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:21:57Z" - latency: 6.119422ms message: 'load-balancer-api-internal: tcp connection to a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:20:57Z" - latency: 8.411983ms message: 'load-balancer-api-internal: resolved host name a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:20:57Z" - latency: 4.495954ms message: 'load-balancer-api-internal: tcp connection to a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:19:57Z" - latency: 8.204927ms message: 'load-balancer-api-internal: resolved host name a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:19:57Z" - latency: 4.881221ms message: 'load-balancer-api-internal: tcp connection to a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:18:57Z" - latency: 7.781139ms message: 'load-balancer-api-internal: resolved host name a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:18:57Z" - latency: 4.689661ms message: 'load-balancer-api-internal: tcp connection to a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:17:57Z" - latency: 8.843111ms message: 'load-balancer-api-internal: resolved host name a57af336bb6394c58b7adc4e85144edd-c03fc928e5799c98.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T21:17:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T21:09:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-111-to-network-check-target-ip-10-0-130-111 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-111.ec2.internal uid: 83c6ef52-f09b-4697-857a-32a4256a31dd resourceVersion: "30240" uid: 1535f841-9cfe-4e47-9bf4-ab8c0e3a7736 spec: sourcePod: network-check-source-dbd9cf844-qhgth targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-03T21:16:57Z" message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.381771ms message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:23:57Z" - latency: 1.268905ms message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:22:57Z" - latency: 1.210201ms message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:21:57Z" - latency: 807.945µs message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:20:57Z" - latency: 1.368835ms message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:19:57Z" - latency: 923.03µs message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:18:57Z" - latency: 860.556µs message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:17:57Z" - latency: 892.983µs message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:16:57Z" - latency: 923.955µs message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:15:57Z" - latency: 1.03909ms message: 'network-check-target-ip-10-0-130-111: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:14:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T21:09:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-111-to-network-check-target-ip-10-0-137-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-111.ec2.internal uid: 83c6ef52-f09b-4697-857a-32a4256a31dd resourceVersion: "30242" uid: 01603ec8-6482-452a-8cd6-a06ddec68ac5 spec: sourcePod: network-check-source-dbd9cf844-qhgth targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-03T21:16:57Z" message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.91168ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:23:57Z" - latency: 2.202328ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:22:57Z" - latency: 1.906851ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:21:57Z" - latency: 1.830859ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:20:57Z" - latency: 2.016533ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:19:57Z" - latency: 1.738349ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:18:57Z" - latency: 1.86648ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:17:57Z" - latency: 2.011649ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:16:57Z" - latency: 1.771228ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:15:57Z" - latency: 1.767022ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:14:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T21:09:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-111-to-network-check-target-ip-10-0-142-28 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-111.ec2.internal uid: 83c6ef52-f09b-4697-857a-32a4256a31dd resourceVersion: "30241" uid: b5cc626b-18d0-4a61-88a8-eee179ccc627 spec: sourcePod: network-check-source-dbd9cf844-qhgth targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-03T21:16:57Z" message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.017343ms message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:23:57Z" - latency: 2.192669ms message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:22:57Z" - latency: 1.972076ms message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:21:57Z" - latency: 1.990804ms message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:20:57Z" - latency: 2.162966ms message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:19:57Z" - latency: 2.183668ms message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:18:57Z" - latency: 2.104437ms message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:17:57Z" - latency: 2.258535ms message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:16:57Z" - latency: 2.419862ms message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:15:57Z" - latency: 2.108464ms message: 'network-check-target-ip-10-0-142-28: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:14:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T21:09:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-111-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-111.ec2.internal uid: 83c6ef52-f09b-4697-857a-32a4256a31dd resourceVersion: "28704" uid: f984d724-ddec-46e5-bd44-3070acd66051 spec: sourcePod: network-check-source-dbd9cf844-qhgth targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-03T21:15:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 877.788µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:21:57Z" - latency: 1.989721ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T21:21:57Z" - latency: 815.222µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:20:57Z" - latency: 2.351909ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T21:20:57Z" - latency: 928.698µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:19:57Z" - latency: 1.621013ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T21:19:57Z" - latency: 873.466µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:18:57Z" - latency: 2.534058ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T21:18:57Z" - latency: 939.175µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T21:17:57Z" - latency: 1.979842ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T21:17:57Z" kind: List metadata: resourceVersion: ""