apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:14:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-243-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-243.ec2.internal uid: 5068fc89-a21d-480d-be8f-73ffadd590fc resourceVersion: "29682" uid: 0e9d9ece-66b3-4775-8bf6-5e48fccecca2 spec: sourcePod: network-check-source-56d84b9f44-7gkt9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T01:21:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 907.7µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:28:29Z" - latency: 881.698µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:27:29Z" - latency: 894.027µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:26:29Z" - latency: 947.976µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:25:29Z" - latency: 1.090344ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:24:29Z" - latency: 1.097086ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:23:29Z" - latency: 791.75µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:22:29Z" - latency: 1.109479ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:21:29Z" - latency: 1.44498ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:20:29Z" - latency: 948.124µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:19:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:14:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-243-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-243.ec2.internal uid: 5068fc89-a21d-480d-be8f-73ffadd590fc resourceVersion: "28140" uid: 29e33728-fdc8-4cac-92b5-4ff77c87cc30 spec: sourcePod: network-check-source-56d84b9f44-7gkt9 targetEndpoint: a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T01:20:29Z" message: 'load-balancer-api-external: tcp connection to a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.227509ms message: 'load-balancer-api-external: tcp connection to a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:26:29Z" - latency: 7.374985ms message: 'load-balancer-api-external: resolved host name a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:26:29Z" - latency: 4.384319ms message: 'load-balancer-api-external: tcp connection to a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:25:29Z" - latency: 7.970509ms message: 'load-balancer-api-external: resolved host name a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:25:29Z" - latency: 5.713739ms message: 'load-balancer-api-external: tcp connection to a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:24:29Z" - latency: 6.68349ms message: 'load-balancer-api-external: resolved host name a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:24:29Z" - latency: 5.810519ms message: 'load-balancer-api-external: tcp connection to a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:23:29Z" - latency: 7.05913ms message: 'load-balancer-api-external: resolved host name a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:23:29Z" - latency: 4.553442ms message: 'load-balancer-api-external: tcp connection to a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:22:29Z" - latency: 9.149446ms message: 'load-balancer-api-external: resolved host name a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:22:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:14:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-243-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-243.ec2.internal uid: 5068fc89-a21d-480d-be8f-73ffadd590fc resourceVersion: "28139" uid: 64c9e8c9-c6a2-419b-867b-c5d1902f2cab spec: sourcePod: network-check-source-56d84b9f44-7gkt9 targetEndpoint: a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T01:20:29Z" message: 'load-balancer-api-internal: tcp connection to a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.193933ms message: 'load-balancer-api-internal: tcp connection to a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:26:29Z" - latency: 7.407386ms message: 'load-balancer-api-internal: resolved host name a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:26:29Z" - latency: 4.40535ms message: 'load-balancer-api-internal: tcp connection to a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:25:29Z" - latency: 8.027086ms message: 'load-balancer-api-internal: resolved host name a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:25:29Z" - latency: 6.661975ms message: 'load-balancer-api-internal: tcp connection to a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:24:29Z" - latency: 6.734681ms message: 'load-balancer-api-internal: resolved host name a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:24:29Z" - latency: 6.302597ms message: 'load-balancer-api-internal: tcp connection to a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:23:29Z" - latency: 7.03716ms message: 'load-balancer-api-internal: resolved host name a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:23:29Z" - latency: 4.51494ms message: 'load-balancer-api-internal: tcp connection to a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:22:29Z" - latency: 9.18622ms message: 'load-balancer-api-internal: resolved host name a6e382f116d0049b7a4636e71249d1d1-0904f8e2167c9843.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:22:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:14:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-243-to-network-check-target-ip-10-0-135-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-243.ec2.internal uid: 5068fc89-a21d-480d-be8f-73ffadd590fc resourceVersion: "29681" uid: 67e13659-b251-474c-973a-714b0ea12d51 spec: sourcePod: network-check-source-56d84b9f44-7gkt9 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-02T01:21:29Z" message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.481637ms message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:28:29Z" - latency: 1.831263ms message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:27:29Z" - latency: 2.308315ms message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:26:29Z" - latency: 2.089843ms message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:25:29Z" - latency: 2.329476ms message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:24:29Z" - latency: 2.197837ms message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:23:29Z" - latency: 2.066033ms message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:22:29Z" - latency: 2.351349ms message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:21:29Z" - latency: 2.887854ms message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:20:29Z" - latency: 2.159381ms message: 'network-check-target-ip-10-0-135-17: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:19:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:14:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-243-to-network-check-target-ip-10-0-138-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-243.ec2.internal uid: 5068fc89-a21d-480d-be8f-73ffadd590fc resourceVersion: "29680" uid: c77a9852-cd56-471e-afbd-bf1b06d16784 spec: sourcePod: network-check-source-56d84b9f44-7gkt9 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T01:21:29Z" message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.225249ms message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:28:29Z" - latency: 2.278251ms message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:27:29Z" - latency: 2.277551ms message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:26:29Z" - latency: 2.03012ms message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:25:29Z" - latency: 2.169907ms message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:24:29Z" - latency: 2.376338ms message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:23:29Z" - latency: 2.103049ms message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:22:29Z" - latency: 2.543267ms message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:21:29Z" - latency: 2.674146ms message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:20:29Z" - latency: 2.197847ms message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:19:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:14:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-243-to-network-check-target-ip-10-0-139-243 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-243.ec2.internal uid: 5068fc89-a21d-480d-be8f-73ffadd590fc resourceVersion: "29679" uid: 2d93c214-971b-4652-8124-13940f52f36f spec: sourcePod: network-check-source-56d84b9f44-7gkt9 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T01:21:29Z" message: 'network-check-target-ip-10-0-139-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 777.698µs message: 'network-check-target-ip-10-0-139-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:28:29Z" - latency: 805.67µs message: 'network-check-target-ip-10-0-139-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:27:29Z" - latency: 905.818µs message: 'network-check-target-ip-10-0-139-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:26:29Z" - latency: 1.297383ms message: 'network-check-target-ip-10-0-139-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:25:29Z" - latency: 905.906µs message: 'network-check-target-ip-10-0-139-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:24:29Z" - latency: 877.396µs message: 'network-check-target-ip-10-0-139-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:23:29Z" - latency: 887.858µs message: 'network-check-target-ip-10-0-139-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:22:29Z" - latency: 1.050218ms message: 'network-check-target-ip-10-0-139-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:21:29Z" - latency: 1.396846ms message: 'network-check-target-ip-10-0-139-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:20:29Z" - latency: 964.501µs message: 'network-check-target-ip-10-0-139-243: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:19:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:14:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-243-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-243.ec2.internal uid: 5068fc89-a21d-480d-be8f-73ffadd590fc resourceVersion: "28138" uid: 1a44f58e-e1d7-4afb-8bd0-98621d017a0e spec: sourcePod: network-check-source-56d84b9f44-7gkt9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T01:20:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 753.645µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:26:29Z" - latency: 1.58741ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T01:26:29Z" - latency: 717.113µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:25:29Z" - latency: 1.962011ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T01:25:29Z" - latency: 798.662µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:24:29Z" - latency: 1.552957ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T01:24:29Z" - latency: 1.339556ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:23:29Z" - latency: 1.777172ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T01:23:29Z" - latency: 1.034893ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:22:29Z" - latency: 1.911041ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T01:22:29Z" kind: List metadata: resourceVersion: ""