apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T02:29:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-153-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-153.ec2.internal uid: b9ae5078-6960-40b1-b280-3b6b82aa7e9a resourceVersion: "23278" uid: 70cbf283-42f6-48ff-8174-910b133e698e spec: sourcePod: network-check-source-685456655f-l47l7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-09T02:36:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.003789ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:36:22Z" - latency: 1.491961ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:35:22Z" - latency: 1.115493ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:34:22Z" - latency: 1.042835ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:33:22Z" - latency: 1.097883ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:32:22Z" - latency: 1.183909ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:31:22Z" - latency: 1.20021ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:30:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T02:29:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-153-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-153.ec2.internal uid: b9ae5078-6960-40b1-b280-3b6b82aa7e9a resourceVersion: "22430" uid: 173e68d6-ba19-4a81-9b9a-f9d4c3b96fcc spec: sourcePod: network-check-source-685456655f-l47l7 targetEndpoint: a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T02:35:22Z" message: 'load-balancer-api-external: tcp connection to a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.180792ms message: 'load-balancer-api-external: tcp connection to a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:35:22Z" - latency: 7.315787ms message: 'load-balancer-api-external: resolved host name a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T02:35:22Z" - latency: 6.638728ms message: 'load-balancer-api-external: tcp connection to a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:34:22Z" - latency: 8.404015ms message: 'load-balancer-api-external: resolved host name a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T02:34:22Z" - latency: 4.242757ms message: 'load-balancer-api-external: tcp connection to a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:33:22Z" - latency: 10.474239ms message: 'load-balancer-api-external: resolved host name a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T02:33:22Z" - latency: 5.280477ms message: 'load-balancer-api-external: tcp connection to a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:32:22Z" - latency: 7.743601ms message: 'load-balancer-api-external: resolved host name a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T02:32:22Z" - latency: 5.029496ms message: 'load-balancer-api-external: tcp connection to a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:31:22Z" - latency: 8.997551ms message: 'load-balancer-api-external: resolved host name a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T02:31:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T02:29:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-153-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-153.ec2.internal uid: b9ae5078-6960-40b1-b280-3b6b82aa7e9a resourceVersion: "22429" uid: 6040a45c-299a-47e2-a615-f2beba48ccfc spec: sourcePod: network-check-source-685456655f-l47l7 targetEndpoint: a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-09T02:35:22Z" message: 'load-balancer-api-internal: tcp connection to a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.869135ms message: 'load-balancer-api-internal: tcp connection to a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:35:22Z" - latency: 7.337556ms message: 'load-balancer-api-internal: resolved host name a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T02:35:22Z" - latency: 4.069908ms message: 'load-balancer-api-internal: tcp connection to a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:34:22Z" - latency: 8.429735ms message: 'load-balancer-api-internal: resolved host name a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T02:34:22Z" - latency: 4.231613ms message: 'load-balancer-api-internal: tcp connection to a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:33:22Z" - latency: 10.500618ms message: 'load-balancer-api-internal: resolved host name a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T02:33:22Z" - latency: 4.738503ms message: 'load-balancer-api-internal: tcp connection to a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:32:22Z" - latency: 7.792214ms message: 'load-balancer-api-internal: resolved host name a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T02:32:22Z" - latency: 5.137421ms message: 'load-balancer-api-internal: tcp connection to a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:31:22Z" - latency: 8.954425ms message: 'load-balancer-api-internal: resolved host name a5d9b333c355c46c787f889e36e5f4ef-a24fc32a576a395a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-09T02:31:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T02:29:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-153-to-network-check-target-ip-10-0-128-153 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-153.ec2.internal uid: b9ae5078-6960-40b1-b280-3b6b82aa7e9a resourceVersion: "23275" uid: dbe314b9-211f-4cb1-bc80-46cd058ecbef spec: sourcePod: network-check-source-685456655f-l47l7 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-09T02:36:22Z" message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 925.349µs message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:36:22Z" - latency: 1.88919ms message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:35:22Z" - latency: 821.669µs message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:34:22Z" - latency: 1.451338ms message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:33:22Z" - latency: 979.49µs message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:32:22Z" - latency: 1.159903ms message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:31:22Z" - latency: 1.265208ms message: 'network-check-target-ip-10-0-128-153: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:30:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T02:29:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-153-to-network-check-target-ip-10-0-137-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-153.ec2.internal uid: b9ae5078-6960-40b1-b280-3b6b82aa7e9a resourceVersion: "23277" uid: 96d967e9-1a44-42a8-839b-4363abfdf376 spec: sourcePod: network-check-source-685456655f-l47l7 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-09T02:36:22Z" message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.069169ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:36:22Z" - latency: 2.056645ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:35:22Z" - latency: 1.982127ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:34:22Z" - latency: 2.171586ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:33:22Z" - latency: 1.847649ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:32:22Z" - latency: 2.217387ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:31:22Z" - latency: 2.22549ms message: 'network-check-target-ip-10-0-137-93: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:30:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T02:29:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-153-to-network-check-target-ip-10-0-143-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-153.ec2.internal uid: b9ae5078-6960-40b1-b280-3b6b82aa7e9a resourceVersion: "23276" uid: 53fe5d1d-9ce3-40ad-b505-715b1fc11cb9 spec: sourcePod: network-check-source-685456655f-l47l7 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-09T02:36:22Z" message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.324894ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:36:22Z" - latency: 2.117719ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:35:22Z" - latency: 2.290284ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:34:22Z" - latency: 2.167058ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:33:22Z" - latency: 2.169185ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:32:22Z" - latency: 2.280127ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:31:22Z" - latency: 2.452316ms message: 'network-check-target-ip-10-0-143-68: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:30:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-09T02:29:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-153-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-153.ec2.internal uid: b9ae5078-6960-40b1-b280-3b6b82aa7e9a resourceVersion: "22428" uid: 1a381fb9-38d2-4e44-9813-4920dcf8d457 spec: sourcePod: network-check-source-685456655f-l47l7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-09T02:35:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 870.731µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:35:22Z" - latency: 1.993341ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T02:35:22Z" - latency: 1.226909ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:34:22Z" - latency: 1.784801ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T02:34:22Z" - latency: 740.062µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:33:22Z" - latency: 1.753816ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T02:33:22Z" - latency: 882.233µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:32:22Z" - latency: 1.808304ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T02:32:22Z" - latency: 863.113µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-09T02:31:22Z" - latency: 2.28062ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-09T02:31:22Z" kind: List metadata: resourceVersion: ""