apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:37:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: be3d51e9-5a27-432e-9dfb-d1662d21bb00 resourceVersion: "32426" uid: a2690eb5-3fc4-4ffe-bdf5-1babd75341f3 spec: sourcePod: network-check-source-7d88cb55d8-czbqw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-28T15:44:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 993.949µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:19:21Z" - latency: 1.017049ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:18:21Z" - latency: 940.782µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:17:21Z" - latency: 1.089894ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:16:21Z" - latency: 859.202µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:15:21Z" - latency: 1.072006ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:14:21Z" - latency: 762.657µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:13:21Z" - latency: 907.339µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:12:21Z" - latency: 924.35µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:11:21Z" - latency: 965.228µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:10:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:37:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: be3d51e9-5a27-432e-9dfb-d1662d21bb00 resourceVersion: "32427" uid: 9730b220-4f2c-4aac-a39b-3beea6c53f91 spec: sourcePod: network-check-source-7d88cb55d8-czbqw targetEndpoint: a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T15:43:21Z" message: 'load-balancer-api-external: tcp connection to a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.63441ms message: 'load-balancer-api-external: tcp connection to a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:19:21Z" - latency: 10.270734ms message: 'load-balancer-api-external: resolved host name a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:19:21Z" - latency: 5.565394ms message: 'load-balancer-api-external: tcp connection to a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:18:21Z" - latency: 13.25807ms message: 'load-balancer-api-external: resolved host name a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:18:21Z" - latency: 4.499851ms message: 'load-balancer-api-external: tcp connection to a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:17:21Z" - latency: 9.779906ms message: 'load-balancer-api-external: resolved host name a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:17:21Z" - latency: 5.051446ms message: 'load-balancer-api-external: tcp connection to a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:16:21Z" - latency: 8.625986ms message: 'load-balancer-api-external: resolved host name a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:16:21Z" - latency: 4.868093ms message: 'load-balancer-api-external: tcp connection to a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:15:21Z" - latency: 9.247827ms message: 'load-balancer-api-external: resolved host name a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:15:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:37:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: be3d51e9-5a27-432e-9dfb-d1662d21bb00 resourceVersion: "32428" uid: 8dddba1c-371a-4a28-b8f2-1c57ccbaa1c9 spec: sourcePod: network-check-source-7d88cb55d8-czbqw targetEndpoint: a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-28T15:43:21Z" message: 'load-balancer-api-internal: tcp connection to a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.959315ms message: 'load-balancer-api-internal: tcp connection to a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:19:21Z" - latency: 10.222659ms message: 'load-balancer-api-internal: resolved host name a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:19:21Z" - latency: 5.626062ms message: 'load-balancer-api-internal: tcp connection to a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:18:21Z" - latency: 13.19971ms message: 'load-balancer-api-internal: resolved host name a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:18:21Z" - latency: 4.588924ms message: 'load-balancer-api-internal: tcp connection to a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:17:21Z" - latency: 9.716618ms message: 'load-balancer-api-internal: resolved host name a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:17:21Z" - latency: 5.056896ms message: 'load-balancer-api-internal: tcp connection to a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:16:21Z" - latency: 8.584065ms message: 'load-balancer-api-internal: resolved host name a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:16:21Z" - latency: 4.946913ms message: 'load-balancer-api-internal: tcp connection to a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:15:21Z" - latency: 9.168468ms message: 'load-balancer-api-internal: resolved host name a4bd0f48d75df4209a9b1a0603236882-fe22181368a95953.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-28T16:15:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:37:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-network-check-target-ip-10-0-134-118 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: be3d51e9-5a27-432e-9dfb-d1662d21bb00 resourceVersion: "32422" uid: 0d204a09-5aa2-4287-89eb-3c1cb2a1768e spec: sourcePod: network-check-source-7d88cb55d8-czbqw targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T15:44:21Z" message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.186628ms message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:19:21Z" - latency: 1.288824ms message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:18:21Z" - latency: 944.647µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:17:21Z" - latency: 755.515µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:16:21Z" - latency: 873.057µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:15:21Z" - latency: 850.144µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:14:21Z" - latency: 754.47µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:13:21Z" - latency: 999.755µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:12:21Z" - latency: 858.443µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:11:21Z" - latency: 753.468µs message: 'network-check-target-ip-10-0-134-118: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:10:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:37:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-network-check-target-ip-10-0-141-87 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: be3d51e9-5a27-432e-9dfb-d1662d21bb00 resourceVersion: "32423" uid: 9e119de0-ef73-4f5e-b4de-6c5a9e2b716e spec: sourcePod: network-check-source-7d88cb55d8-czbqw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-28T15:44:21Z" message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.068999ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:19:21Z" - latency: 1.845355ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:18:21Z" - latency: 1.783021ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:17:21Z" - latency: 1.70213ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:16:21Z" - latency: 2.224726ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:15:21Z" - latency: 1.976053ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:14:21Z" - latency: 1.555676ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:13:21Z" - latency: 2.135764ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:12:21Z" - latency: 2.020319ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:11:21Z" - latency: 1.884674ms message: 'network-check-target-ip-10-0-141-87: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:10:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:37:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-network-check-target-ip-10-0-143-228 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: be3d51e9-5a27-432e-9dfb-d1662d21bb00 resourceVersion: "32425" uid: 0d1cf2f4-938e-4dbb-9ec8-0c317c68efd6 spec: sourcePod: network-check-source-7d88cb55d8-czbqw targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-28T15:44:21Z" message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.18202ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:19:21Z" - latency: 2.107885ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:18:21Z" - latency: 2.134471ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:17:21Z" - latency: 2.083193ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:16:21Z" - latency: 2.008607ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:15:21Z" - latency: 2.168456ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:14:21Z" - latency: 1.763547ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:13:21Z" - latency: 2.369818ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:12:21Z" - latency: 1.842117ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:11:21Z" - latency: 1.780841ms message: 'network-check-target-ip-10-0-143-228: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:10:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-28T15:37:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-118-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-118.ec2.internal uid: be3d51e9-5a27-432e-9dfb-d1662d21bb00 resourceVersion: "32424" uid: 31132903-a59b-4c58-8c85-1989875a61c3 spec: sourcePod: network-check-source-7d88cb55d8-czbqw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-28T15:43:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 810.015µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:19:21Z" - latency: 2.151089ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:19:21Z" - latency: 773.834µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:18:21Z" - latency: 1.717005ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:18:21Z" - latency: 932.178µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:17:21Z" - latency: 1.705615ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:17:21Z" - latency: 1.144869ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:16:21Z" - latency: 1.686473ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:16:21Z" - latency: 831.6µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-28T16:15:21Z" - latency: 1.95044ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-28T16:15:21Z" kind: List metadata: resourceVersion: ""