apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T02:04:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-209-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-209.ec2.internal uid: 972c96e9-b57a-46cf-ac10-12963528a477 resourceVersion: "27755" uid: f4e1a304-db35-44ec-971a-7263b9fee662 spec: sourcePod: network-check-source-6f8b768455-k8bq6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-11T02:11:59Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 958.472µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:18:59Z" - latency: 1.007231ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:17:59Z" - latency: 849.92µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:16:59Z" - latency: 945.215µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:15:59Z" - latency: 1.347939ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:14:59Z" - latency: 902.91µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:13:59Z" - latency: 1.544197ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:12:59Z" - latency: 1.200884ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:11:59Z" - latency: 933.367µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:10:59Z" - latency: 843.879µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:09:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T02:04:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-209-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-209.ec2.internal uid: 972c96e9-b57a-46cf-ac10-12963528a477 resourceVersion: "26553" uid: ddaf5a93-fa1b-474f-b385-0a8167b08b2a spec: sourcePod: network-check-source-6f8b768455-k8bq6 targetEndpoint: a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T02:10:59Z" message: 'load-balancer-api-external: tcp connection to a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.584819ms message: 'load-balancer-api-external: tcp connection to a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:16:59Z" - latency: 8.954686ms message: 'load-balancer-api-external: resolved host name a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T02:16:59Z" - latency: 4.542955ms message: 'load-balancer-api-external: tcp connection to a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:15:59Z" - latency: 7.945641ms message: 'load-balancer-api-external: resolved host name a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T02:15:59Z" - latency: 4.526119ms message: 'load-balancer-api-external: tcp connection to a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:14:59Z" - latency: 8.488846ms message: 'load-balancer-api-external: resolved host name a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T02:14:59Z" - latency: 4.743151ms message: 'load-balancer-api-external: tcp connection to a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:13:59Z" - latency: 8.687123ms message: 'load-balancer-api-external: resolved host name a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T02:13:59Z" - latency: 4.778856ms message: 'load-balancer-api-external: tcp connection to a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:12:59Z" - latency: 8.54102ms message: 'load-balancer-api-external: resolved host name a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T02:12:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T02:04:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-209-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-209.ec2.internal uid: 972c96e9-b57a-46cf-ac10-12963528a477 resourceVersion: "26552" uid: b05d237a-b08a-440c-9c96-d66d8049e72f spec: sourcePod: network-check-source-6f8b768455-k8bq6 targetEndpoint: a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-11T02:10:59Z" message: 'load-balancer-api-internal: tcp connection to a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.55304ms message: 'load-balancer-api-internal: tcp connection to a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:16:59Z" - latency: 9.031877ms message: 'load-balancer-api-internal: resolved host name a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T02:16:59Z" - latency: 4.589305ms message: 'load-balancer-api-internal: tcp connection to a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:15:59Z" - latency: 7.91374ms message: 'load-balancer-api-internal: resolved host name a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T02:15:59Z" - latency: 4.592916ms message: 'load-balancer-api-internal: tcp connection to a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:14:59Z" - latency: 8.410619ms message: 'load-balancer-api-internal: resolved host name a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T02:14:59Z" - latency: 4.995967ms message: 'load-balancer-api-internal: tcp connection to a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:13:59Z" - latency: 8.60816ms message: 'load-balancer-api-internal: resolved host name a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T02:13:59Z" - latency: 4.830492ms message: 'load-balancer-api-internal: tcp connection to a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:12:59Z" - latency: 8.575454ms message: 'load-balancer-api-internal: resolved host name a2990ca43ed7945a7bb7b1c90af7a37a-f7d854c7aacd0f6c.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-11T02:12:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T02:04:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-209-to-network-check-target-ip-10-0-134-209 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-209.ec2.internal uid: 972c96e9-b57a-46cf-ac10-12963528a477 resourceVersion: "27752" uid: 33354c42-c875-471a-a916-4f8e3da54cef spec: sourcePod: network-check-source-6f8b768455-k8bq6 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-11T02:11:59Z" message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 986.258µs message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:18:59Z" - latency: 1.645646ms message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:17:59Z" - latency: 1.388616ms message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:16:59Z" - latency: 1.734326ms message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:15:59Z" - latency: 934.359µs message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:14:59Z" - latency: 1.138271ms message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:13:59Z" - latency: 1.101749ms message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:12:59Z" - latency: 1.31193ms message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:11:59Z" - latency: 1.045314ms message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:10:59Z" - latency: 918.348µs message: 'network-check-target-ip-10-0-134-209: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:09:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T02:04:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-209-to-network-check-target-ip-10-0-135-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-209.ec2.internal uid: 972c96e9-b57a-46cf-ac10-12963528a477 resourceVersion: "27753" uid: d26b18e5-bc67-4d10-bfbb-baee2f0aa725 spec: sourcePod: network-check-source-6f8b768455-k8bq6 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-11T02:11:59Z" message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.286921ms message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:18:59Z" - latency: 2.861577ms message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:17:59Z" - latency: 2.332934ms message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:16:59Z" - latency: 2.898653ms message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:15:59Z" - latency: 2.559541ms message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:14:59Z" - latency: 2.45782ms message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:13:59Z" - latency: 3.45547ms message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:12:59Z" - latency: 2.55399ms message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:11:59Z" - latency: 2.222933ms message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:10:59Z" - latency: 2.29348ms message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:09:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T02:04:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-209-to-network-check-target-ip-10-0-135-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-209.ec2.internal uid: 972c96e9-b57a-46cf-ac10-12963528a477 resourceVersion: "27754" uid: 149219d5-dcde-4633-afa0-3d466a9c22af spec: sourcePod: network-check-source-6f8b768455-k8bq6 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-11T02:11:59Z" message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.482786ms message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:18:59Z" - latency: 2.383986ms message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:17:59Z" - latency: 2.358841ms message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:16:59Z" - latency: 2.521561ms message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:15:59Z" - latency: 2.464331ms message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:14:59Z" - latency: 2.527692ms message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:13:59Z" - latency: 2.138105ms message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:12:59Z" - latency: 2.257261ms message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:11:59Z" - latency: 2.422824ms message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:10:59Z" - latency: 2.350616ms message: 'network-check-target-ip-10-0-135-234: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:09:59Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-11T02:04:58Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-209-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-209.ec2.internal uid: 972c96e9-b57a-46cf-ac10-12963528a477 resourceVersion: "26551" uid: 945f5877-b704-492b-88b6-5408f83d89d9 spec: sourcePod: network-check-source-6f8b768455-k8bq6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-11T02:10:59Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 849.813µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:16:59Z" - latency: 2.312009ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T02:16:59Z" - latency: 1.279596ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:15:59Z" - latency: 1.710023ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T02:15:59Z" - latency: 1.441114ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:14:59Z" - latency: 1.811528ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T02:14:59Z" - latency: 753.33µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:13:59Z" - latency: 1.864018ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T02:13:59Z" - latency: 1.488092ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-11T02:12:59Z" - latency: 1.843532ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-11T02:12:59Z" kind: List metadata: resourceVersion: ""