apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:12:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-104-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-104.ec2.internal uid: 3b452849-70c6-4cd8-8450-5c5a7e9ea693 resourceVersion: "45294" uid: 613a2c75-11c8-4f65-a59a-f949d5013210 spec: sourcePod: network-check-source-dbd9cf844-fswqw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-05T13:19:09Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 801.82µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:40:09Z" - latency: 1.211626ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:39:09Z" - latency: 903.957µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:38:09Z" - latency: 1.067447ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:37:09Z" - latency: 739.145µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:36:09Z" - latency: 1.081558ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:35:09Z" - latency: 1.084988ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:34:09Z" - latency: 1.509067ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:33:09Z" - latency: 930.978µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:32:09Z" - latency: 937.397µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:31:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:12:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-104-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-104.ec2.internal uid: 3b452849-70c6-4cd8-8450-5c5a7e9ea693 resourceVersion: "47585" uid: 3986076d-8192-4dc2-b54b-63cbf0c56fa3 spec: sourcePod: network-check-source-dbd9cf844-fswqw targetEndpoint: aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T13:18:09Z" message: 'load-balancer-api-external: tcp connection to aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 8.82518ms message: 'load-balancer-api-external: tcp connection to aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:42:09Z" - latency: 6.590249ms message: 'load-balancer-api-external: resolved host name aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:42:09Z" - latency: 4.151748ms message: 'load-balancer-api-external: tcp connection to aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:41:09Z" - latency: 7.086046ms message: 'load-balancer-api-external: resolved host name aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:41:09Z" - latency: 4.333081ms message: 'load-balancer-api-external: tcp connection to aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:40:09Z" - latency: 6.954391ms message: 'load-balancer-api-external: resolved host name aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:40:09Z" - latency: 5.426907ms message: 'load-balancer-api-external: tcp connection to aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:39:09Z" - latency: 7.278098ms message: 'load-balancer-api-external: resolved host name aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:39:09Z" - latency: 3.868867ms message: 'load-balancer-api-external: tcp connection to aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:38:09Z" - latency: 6.762172ms message: 'load-balancer-api-external: resolved host name aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:38:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:12:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-104-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-104.ec2.internal uid: 3b452849-70c6-4cd8-8450-5c5a7e9ea693 resourceVersion: "47586" uid: 45449060-cb09-44a4-ae61-fcbef2fff7bd spec: sourcePod: network-check-source-dbd9cf844-fswqw targetEndpoint: aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T13:18:09Z" message: 'load-balancer-api-internal: tcp connection to aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.373187ms message: 'load-balancer-api-internal: tcp connection to aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:42:09Z" - latency: 6.529449ms message: 'load-balancer-api-internal: resolved host name aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:42:09Z" - latency: 4.141393ms message: 'load-balancer-api-internal: tcp connection to aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:41:09Z" - latency: 7.127106ms message: 'load-balancer-api-internal: resolved host name aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:41:09Z" - latency: 4.95348ms message: 'load-balancer-api-internal: tcp connection to aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:40:09Z" - latency: 6.995072ms message: 'load-balancer-api-internal: resolved host name aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:40:09Z" - latency: 5.429637ms message: 'load-balancer-api-internal: tcp connection to aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:39:09Z" - latency: 7.196471ms message: 'load-balancer-api-internal: resolved host name aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:39:09Z" - latency: 3.792563ms message: 'load-balancer-api-internal: tcp connection to aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:38:09Z" - latency: 6.782957ms message: 'load-balancer-api-internal: resolved host name aac4abc6696744609a6879362891eb27-06c1370b03f1530d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T13:38:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:12:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-104-to-network-check-target-ip-10-0-137-145 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-104.ec2.internal uid: 3b452849-70c6-4cd8-8450-5c5a7e9ea693 resourceVersion: "45292" uid: 018d199c-db34-464b-870a-3826fb1b76c6 spec: sourcePod: network-check-source-dbd9cf844-fswqw targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T13:19:09Z" message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.191193ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:40:09Z" - latency: 1.85689ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:39:09Z" - latency: 2.160956ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:38:09Z" - latency: 2.264976ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:37:09Z" - latency: 2.329813ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:36:09Z" - latency: 2.482041ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:35:09Z" - latency: 2.116183ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:34:09Z" - latency: 2.813997ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:33:09Z" - latency: 2.447455ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:32:09Z" - latency: 2.140746ms message: 'network-check-target-ip-10-0-137-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:31:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:12:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-104-to-network-check-target-ip-10-0-141-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-104.ec2.internal uid: 3b452849-70c6-4cd8-8450-5c5a7e9ea693 resourceVersion: "45291" uid: 20a16991-b266-47ea-ad48-37abc00cd6fb spec: sourcePod: network-check-source-dbd9cf844-fswqw targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T13:19:09Z" message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 967.228µs message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:40:09Z" - latency: 707.401µs message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:39:09Z" - latency: 987.885µs message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:38:09Z" - latency: 800.937µs message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:37:09Z" - latency: 1.401229ms message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:36:09Z" - latency: 1.514243ms message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:35:09Z" - latency: 992.958µs message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:34:09Z" - latency: 751.392µs message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:33:09Z" - latency: 791.938µs message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:32:09Z" - latency: 1.518478ms message: 'network-check-target-ip-10-0-141-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:31:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:12:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-104-to-network-check-target-ip-10-0-141-220 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-104.ec2.internal uid: 3b452849-70c6-4cd8-8450-5c5a7e9ea693 resourceVersion: "45293" uid: 2cfad585-a5e5-43e1-8706-7206840ed492 spec: sourcePod: network-check-source-dbd9cf844-fswqw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-05T13:19:09Z" message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.506881ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:40:09Z" - latency: 2.305306ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:39:09Z" - latency: 2.340252ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:38:09Z" - latency: 2.464803ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:37:09Z" - latency: 2.687099ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:36:09Z" - latency: 2.619335ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:35:09Z" - latency: 2.236615ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:34:09Z" - latency: 2.302952ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:33:09Z" - latency: 2.170823ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:32:09Z" - latency: 2.533121ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:31:09Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T13:12:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-104-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-104.ec2.internal uid: 3b452849-70c6-4cd8-8450-5c5a7e9ea693 resourceVersion: "47584" uid: 4b709599-06cb-4e53-b94a-fdd9591bfead spec: sourcePod: network-check-source-dbd9cf844-fswqw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-05T13:18:09Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 911.371µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:42:09Z" - latency: 1.761153ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T13:42:09Z" - latency: 933.5µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:41:09Z" - latency: 1.67692ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T13:41:09Z" - latency: 833.298µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:40:09Z" - latency: 1.736984ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T13:40:09Z" - latency: 776.605µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:39:09Z" - latency: 1.863514ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T13:39:09Z" - latency: 851.685µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T13:38:09Z" - latency: 1.745301ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T13:38:09Z" kind: List metadata: resourceVersion: ""