apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:10:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-242-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-242.ec2.internal uid: ec8edb82-2410-455e-aae4-d796e61e5f61 resourceVersion: "68833" uid: c1aa995a-2ae9-4323-8c3a-1e45be259276 spec: sourcePod: network-check-source-6f8b768455-c8bmg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-16T12:17:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.036913ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:45:19Z" - latency: 1.083056ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:44:19Z" - latency: 863.168µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:43:19Z" - latency: 926.359µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:42:19Z" - latency: 998.452µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:41:19Z" - latency: 1.404495ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:40:19Z" - latency: 1.2475ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:39:19Z" - latency: 1.045001ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:38:19Z" - latency: 1.315923ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:37:19Z" - latency: 1.28314ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:36:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:10:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-242-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-242.ec2.internal uid: ec8edb82-2410-455e-aae4-d796e61e5f61 resourceVersion: "69722" uid: 83b0bb92-7b9b-4841-9131-433c0bc6f27d spec: sourcePod: network-check-source-6f8b768455-c8bmg targetEndpoint: a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T12:16:19Z" message: 'load-balancer-api-external: tcp connection to a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.733507ms message: 'load-balancer-api-external: tcp connection to a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:46:19Z" - latency: 8.414133ms message: 'load-balancer-api-external: resolved host name a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:46:19Z" - latency: 5.901051ms message: 'load-balancer-api-external: tcp connection to a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:45:19Z" - latency: 6.767062ms message: 'load-balancer-api-external: resolved host name a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:45:19Z" - latency: 5.196906ms message: 'load-balancer-api-external: tcp connection to a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:44:19Z" - latency: 8.378543ms message: 'load-balancer-api-external: resolved host name a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:44:19Z" - latency: 5.083461ms message: 'load-balancer-api-external: tcp connection to a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:43:19Z" - latency: 10.799229ms message: 'load-balancer-api-external: resolved host name a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:43:19Z" - latency: 10.129651ms message: 'load-balancer-api-external: tcp connection to a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:42:19Z" - latency: 7.083943ms message: 'load-balancer-api-external: resolved host name a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:42:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:10:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-242-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-242.ec2.internal uid: ec8edb82-2410-455e-aae4-d796e61e5f61 resourceVersion: "69723" uid: a28729cf-1fdd-4b60-ae65-9d6e963c1899 spec: sourcePod: network-check-source-6f8b768455-c8bmg targetEndpoint: a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-16T12:16:19Z" message: 'load-balancer-api-internal: tcp connection to a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.03177ms message: 'load-balancer-api-internal: tcp connection to a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:46:19Z" - latency: 8.503202ms message: 'load-balancer-api-internal: resolved host name a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:46:19Z" - latency: 5.869025ms message: 'load-balancer-api-internal: tcp connection to a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:45:19Z" - latency: 6.821574ms message: 'load-balancer-api-internal: resolved host name a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:45:19Z" - latency: 5.170972ms message: 'load-balancer-api-internal: tcp connection to a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:44:19Z" - latency: 8.483773ms message: 'load-balancer-api-internal: resolved host name a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:44:19Z" - latency: 4.669827ms message: 'load-balancer-api-internal: tcp connection to a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:43:19Z" - latency: 10.907098ms message: 'load-balancer-api-internal: resolved host name a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:43:19Z" - latency: 4.349198ms message: 'load-balancer-api-internal: tcp connection to a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:42:19Z" - latency: 7.158412ms message: 'load-balancer-api-internal: resolved host name a41356bb1716a42feb9b7c27f324302e-b8896dddd8dcb430.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-16T12:42:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:10:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-242-to-network-check-target-ip-10-0-135-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-242.ec2.internal uid: ec8edb82-2410-455e-aae4-d796e61e5f61 resourceVersion: "68830" uid: 6d9437a3-13ce-4e22-9211-da3623ea9eb0 spec: sourcePod: network-check-source-6f8b768455-c8bmg targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-16T12:17:19Z" message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.428631ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:45:19Z" - latency: 1.024404ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:44:19Z" - latency: 915.221µs message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:43:19Z" - latency: 1.061398ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:42:19Z" - latency: 1.117397ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:41:19Z" - latency: 972.928µs message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:40:19Z" - latency: 998.583µs message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:39:19Z" - latency: 1.042072ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:38:19Z" - latency: 976.719µs message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:37:19Z" - latency: 1.338798ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:36:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:10:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-242-to-network-check-target-ip-10-0-136-98 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-242.ec2.internal uid: ec8edb82-2410-455e-aae4-d796e61e5f61 resourceVersion: "68832" uid: 684f0499-75aa-4d1c-9f2f-d65e59bfc6f5 spec: sourcePod: network-check-source-6f8b768455-c8bmg targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-16T12:17:19Z" message: 'network-check-target-ip-10-0-136-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.496361ms message: 'network-check-target-ip-10-0-136-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:45:19Z" - latency: 2.269364ms message: 'network-check-target-ip-10-0-136-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:44:19Z" - latency: 2.345645ms message: 'network-check-target-ip-10-0-136-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:43:19Z" - latency: 2.125598ms message: 'network-check-target-ip-10-0-136-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:42:19Z" - latency: 2.380856ms message: 'network-check-target-ip-10-0-136-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:41:19Z" - latency: 2.250796ms message: 'network-check-target-ip-10-0-136-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:40:19Z" - latency: 2.265555ms message: 'network-check-target-ip-10-0-136-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:39:19Z" - latency: 2.311973ms message: 'network-check-target-ip-10-0-136-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:38:19Z" - latency: 2.196896ms message: 'network-check-target-ip-10-0-136-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:37:19Z" - latency: 2.271981ms message: 'network-check-target-ip-10-0-136-98: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:36:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:10:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-242-to-network-check-target-ip-10-0-137-30 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-242.ec2.internal uid: ec8edb82-2410-455e-aae4-d796e61e5f61 resourceVersion: "68831" uid: 84d40d42-059f-49c7-a844-57f9b45f29e1 spec: sourcePod: network-check-source-6f8b768455-c8bmg targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-16T12:17:19Z" message: 'network-check-target-ip-10-0-137-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.674783ms message: 'network-check-target-ip-10-0-137-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:45:19Z" - latency: 2.39318ms message: 'network-check-target-ip-10-0-137-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:44:19Z" - latency: 2.290524ms message: 'network-check-target-ip-10-0-137-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:43:19Z" - latency: 2.335095ms message: 'network-check-target-ip-10-0-137-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:42:19Z" - latency: 2.296296ms message: 'network-check-target-ip-10-0-137-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:41:19Z" - latency: 2.257255ms message: 'network-check-target-ip-10-0-137-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:40:19Z" - latency: 2.77157ms message: 'network-check-target-ip-10-0-137-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:39:19Z" - latency: 2.294847ms message: 'network-check-target-ip-10-0-137-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:38:19Z" - latency: 2.02261ms message: 'network-check-target-ip-10-0-137-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:37:19Z" - latency: 2.211134ms message: 'network-check-target-ip-10-0-137-30: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:36:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-16T12:10:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-242-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-242.ec2.internal uid: ec8edb82-2410-455e-aae4-d796e61e5f61 resourceVersion: "69721" uid: 11ac5004-d86e-4872-b4f0-26891665cebf spec: sourcePod: network-check-source-6f8b768455-c8bmg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-16T12:16:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 876.63µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:46:19Z" - latency: 1.820628ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T12:46:19Z" - latency: 1.564254ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:45:19Z" - latency: 1.804181ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T12:45:19Z" - latency: 1.009866ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:44:19Z" - latency: 1.790718ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T12:44:19Z" - latency: 1.115635ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:43:19Z" - latency: 2.916256ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T12:43:19Z" - latency: 1.073331ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-16T12:42:19Z" - latency: 1.718788ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-16T12:42:19Z" kind: List metadata: resourceVersion: ""