apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:41:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-5-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-5.us-east-2.compute.internal uid: 5ec453c9-1594-42fd-8483-bf742c7c51e3 resourceVersion: "87926" uid: f8c9c477-7062-45d9-a806-13f175d69a8d spec: sourcePod: network-check-source-6f78d59f99-p7tvx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T17:48:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.170067ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:16:28Z" - latency: 1.519752ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:15:28Z" - latency: 1.147681ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:14:28Z" - latency: 1.783567ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:13:28Z" - latency: 859.801µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:12:28Z" - latency: 1.387381ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:11:28Z" - latency: 999.297µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:10:28Z" - latency: 1.16961ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:09:28Z" - latency: 1.539399ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:08:28Z" - latency: 973.139µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:07:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:41:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-5-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-5.us-east-2.compute.internal uid: 5ec453c9-1594-42fd-8483-bf742c7c51e3 resourceVersion: "89351" uid: 900380bc-fa39-4384-8520-a6cecd7b02bc spec: sourcePod: network-check-source-6f78d59f99-p7tvx targetEndpoint: ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T17:47:28Z" message: 'load-balancer-api-external: tcp connection to ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.107328ms message: 'load-balancer-api-external: tcp connection to ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:17:28Z" - latency: 8.655076ms message: 'load-balancer-api-external: resolved host name ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:17:28Z" - latency: 5.327821ms message: 'load-balancer-api-external: tcp connection to ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:16:28Z" - latency: 7.272587ms message: 'load-balancer-api-external: resolved host name ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:16:28Z" - latency: 5.202713ms message: 'load-balancer-api-external: tcp connection to ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:15:28Z" - latency: 7.35455ms message: 'load-balancer-api-external: resolved host name ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:15:28Z" - latency: 6.797063ms message: 'load-balancer-api-external: tcp connection to ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:14:28Z" - latency: 7.30363ms message: 'load-balancer-api-external: resolved host name ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:14:28Z" - latency: 5.816914ms message: 'load-balancer-api-external: tcp connection to ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:13:28Z" - latency: 7.885731ms message: 'load-balancer-api-external: resolved host name ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:13:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:41:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-5-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-5.us-east-2.compute.internal uid: 5ec453c9-1594-42fd-8483-bf742c7c51e3 resourceVersion: "89352" uid: 5c7d2ba4-63b4-4147-8c3c-fbd0ded980f6 spec: sourcePod: network-check-source-6f78d59f99-p7tvx targetEndpoint: ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T17:47:28Z" message: 'load-balancer-api-internal: tcp connection to ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.159036ms message: 'load-balancer-api-internal: tcp connection to ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:17:28Z" - latency: 8.865365ms message: 'load-balancer-api-internal: resolved host name ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:17:28Z" - latency: 5.334387ms message: 'load-balancer-api-internal: tcp connection to ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:16:28Z" - latency: 7.160033ms message: 'load-balancer-api-internal: resolved host name ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:16:28Z" - latency: 4.639398ms message: 'load-balancer-api-internal: tcp connection to ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:15:28Z" - latency: 7.335603ms message: 'load-balancer-api-internal: resolved host name ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:15:28Z" - latency: 6.822805ms message: 'load-balancer-api-internal: tcp connection to ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:14:28Z" - latency: 7.202685ms message: 'load-balancer-api-internal: resolved host name ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:14:28Z" - latency: 5.718628ms message: 'load-balancer-api-internal: tcp connection to ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:13:28Z" - latency: 7.865485ms message: 'load-balancer-api-internal: resolved host name ae5958bb2383e433ca187ce3cb02f6df-5b08594c4817760f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T18:13:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:41:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-5-to-network-check-target-ip-10-0-132-5 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-5.us-east-2.compute.internal uid: 5ec453c9-1594-42fd-8483-bf742c7c51e3 resourceVersion: "87923" uid: 9a6ef3b8-204c-4488-9e21-858dc8815f4a spec: sourcePod: network-check-source-6f78d59f99-p7tvx targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T17:48:28Z" message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.009705ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:16:28Z" - latency: 1.286215ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:15:28Z" - latency: 1.030787ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:14:28Z" - latency: 1.139747ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:13:28Z" - latency: 2.18756ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:12:28Z" - latency: 1.06453ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:11:28Z" - latency: 883.15µs message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:10:28Z" - latency: 1.107856ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:09:28Z" - latency: 1.197156ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:08:28Z" - latency: 1.332787ms message: 'network-check-target-ip-10-0-132-5: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:07:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:41:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-5-to-network-check-target-ip-10-0-135-9 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-5.us-east-2.compute.internal uid: 5ec453c9-1594-42fd-8483-bf742c7c51e3 resourceVersion: "87924" uid: 3cedb102-ed76-4dc3-98a7-4520eb9b4b59 spec: sourcePod: network-check-source-6f78d59f99-p7tvx targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-02T17:48:28Z" message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.004392ms message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:16:28Z" - latency: 2.287875ms message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:15:28Z" - latency: 1.929974ms message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:14:28Z" - latency: 2.250694ms message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:13:28Z" - latency: 2.110367ms message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:12:28Z" - latency: 1.876944ms message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:11:28Z" - latency: 1.920768ms message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:10:28Z" - latency: 1.98509ms message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:09:28Z" - latency: 2.13374ms message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:08:28Z" - latency: 1.982891ms message: 'network-check-target-ip-10-0-135-9: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:07:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:41:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-5-to-network-check-target-ip-10-0-141-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-5.us-east-2.compute.internal uid: 5ec453c9-1594-42fd-8483-bf742c7c51e3 resourceVersion: "87925" uid: 0c89180c-b7ad-42da-b7de-31f4cdc65b3d spec: sourcePod: network-check-source-6f78d59f99-p7tvx targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T17:48:28Z" message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.207236ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:16:28Z" - latency: 2.318661ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:15:28Z" - latency: 2.272519ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:14:28Z" - latency: 2.596744ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:13:28Z" - latency: 2.142569ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:12:28Z" - latency: 2.238465ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:11:28Z" - latency: 2.093952ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:10:28Z" - latency: 2.40505ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:09:28Z" - latency: 2.272807ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:08:28Z" - latency: 2.350776ms message: 'network-check-target-ip-10-0-141-84: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:07:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T17:41:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-5-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-5.us-east-2.compute.internal uid: 5ec453c9-1594-42fd-8483-bf742c7c51e3 resourceVersion: "89350" uid: 863dcd57-c1df-423a-bdc5-c5aef8d06401 spec: sourcePod: network-check-source-6f78d59f99-p7tvx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T17:47:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.038513ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:17:28Z" - latency: 2.712045ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T18:17:28Z" - latency: 1.325705ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:16:28Z" - latency: 1.867057ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T18:16:28Z" - latency: 923.893µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:15:28Z" - latency: 2.179184ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T18:15:28Z" - latency: 957.286µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:14:28Z" - latency: 2.55375ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T18:14:28Z" - latency: 902.188µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T18:13:28Z" - latency: 2.129352ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T18:13:28Z" kind: List metadata: resourceVersion: ""