apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:42:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-193-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-193.us-east-2.compute.internal uid: 9ea84651-7274-4f82-be6f-ea3379c9f6fb resourceVersion: "169826" uid: c292063f-1a50-4e80-990f-97fde4f87d68 spec: sourcePod: network-check-source-6f78d59f99-hqp48 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T21:49:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.913533ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:31:16Z" - latency: 2.341529ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:30:16Z" - latency: 1.535203ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:29:16Z" - latency: 1.5966ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:28:16Z" - latency: 2.354265ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:27:16Z" - latency: 9.211538ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:26:16Z" - latency: 6.359912ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:25:16Z" - latency: 1.711224ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:24:16Z" - latency: 4.778832ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:23:16Z" - latency: 1.999752ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:22:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:42:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-193-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-193.us-east-2.compute.internal uid: 9ea84651-7274-4f82-be6f-ea3379c9f6fb resourceVersion: "187035" uid: 40999d63-25c1-4286-b93c-e9a3ce6915e8 spec: sourcePod: network-check-source-6f78d59f99-hqp48 targetEndpoint: abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:48:16Z" message: 'load-balancer-api-external: tcp connection to abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.881826ms message: 'load-balancer-api-external: tcp connection to abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:16Z" - latency: 7.596915ms message: 'load-balancer-api-external: resolved host name abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:36:16Z" - latency: 6.368306ms message: 'load-balancer-api-external: tcp connection to abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:16Z" - latency: 9.446495ms message: 'load-balancer-api-external: resolved host name abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:35:16Z" - latency: 6.038351ms message: 'load-balancer-api-external: tcp connection to abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:16Z" - latency: 9.007716ms message: 'load-balancer-api-external: resolved host name abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:34:16Z" - latency: 5.999503ms message: 'load-balancer-api-external: tcp connection to abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:16Z" - latency: 10.171554ms message: 'load-balancer-api-external: resolved host name abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:33:16Z" - latency: 5.918306ms message: 'load-balancer-api-external: tcp connection to abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:16Z" - latency: 10.695353ms message: 'load-balancer-api-external: resolved host name abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:32:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:42:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-193-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-193.us-east-2.compute.internal uid: 9ea84651-7274-4f82-be6f-ea3379c9f6fb resourceVersion: "187036" uid: d3444abb-932e-483a-94e1-5c83e008510c spec: sourcePod: network-check-source-6f78d59f99-hqp48 targetEndpoint: abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:48:16Z" message: 'load-balancer-api-internal: tcp connection to abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.783656ms message: 'load-balancer-api-internal: tcp connection to abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:16Z" - latency: 7.701181ms message: 'load-balancer-api-internal: resolved host name abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:36:16Z" - latency: 5.922745ms message: 'load-balancer-api-internal: tcp connection to abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:16Z" - latency: 9.579415ms message: 'load-balancer-api-internal: resolved host name abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:35:16Z" - latency: 6.086009ms message: 'load-balancer-api-internal: tcp connection to abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:16Z" - latency: 8.70884ms message: 'load-balancer-api-internal: resolved host name abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:34:16Z" - latency: 6.02014ms message: 'load-balancer-api-internal: tcp connection to abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:16Z" - latency: 10.092087ms message: 'load-balancer-api-internal: resolved host name abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:33:16Z" - latency: 6.409227ms message: 'load-balancer-api-internal: tcp connection to abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:16Z" - latency: 10.838725ms message: 'load-balancer-api-internal: resolved host name abeb21f142e024ddab1fb595b96b6cef-4f1bfa8e2ddf7bca.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:32:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:42:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-193-to-network-check-target-ip-10-0-131-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-193.us-east-2.compute.internal uid: 9ea84651-7274-4f82-be6f-ea3379c9f6fb resourceVersion: "169823" uid: 1c60622a-5a72-45d9-83d0-9caad262fa9d spec: sourcePod: network-check-source-6f78d59f99-hqp48 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:49:16Z" message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.581422ms message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:31:16Z" - latency: 3.41682ms message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:30:16Z" - latency: 2.689331ms message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:29:16Z" - latency: 5.146622ms message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:28:16Z" - latency: 2.481024ms message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:27:16Z" - latency: 9.502561ms message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:26:16Z" - latency: 3.414925ms message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:25:16Z" - latency: 3.204697ms message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:24:16Z" - latency: 5.783581ms message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:23:16Z" - latency: 3.632814ms message: 'network-check-target-ip-10-0-131-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:22:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:42:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-193-to-network-check-target-ip-10-0-133-193 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-193.us-east-2.compute.internal uid: 9ea84651-7274-4f82-be6f-ea3379c9f6fb resourceVersion: "169824" uid: 4d0835b9-add2-410e-ae24-222703702f3f spec: sourcePod: network-check-source-6f78d59f99-hqp48 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:49:16Z" message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.004568ms message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:31:16Z" - latency: 1.7632ms message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:30:16Z" - latency: 1.823755ms message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:29:16Z" - latency: 2.50774ms message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:28:16Z" - latency: 1.196636ms message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:27:16Z" - latency: 9.415567ms message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:26:16Z" - latency: 9.423384ms message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:25:16Z" - latency: 3.776792ms message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:24:16Z" - latency: 7.107169ms message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:23:16Z" - latency: 2.798549ms message: 'network-check-target-ip-10-0-133-193: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:22:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:42:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-193-to-network-check-target-ip-10-0-137-181 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-193.us-east-2.compute.internal uid: 9ea84651-7274-4f82-be6f-ea3379c9f6fb resourceVersion: "169825" uid: 29835096-2381-41b2-b23a-f12d40fc7f21 spec: sourcePod: network-check-source-6f78d59f99-hqp48 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:49:16Z" message: 'network-check-target-ip-10-0-137-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.109232ms message: 'network-check-target-ip-10-0-137-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:31:16Z" - latency: 3.467572ms message: 'network-check-target-ip-10-0-137-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:30:16Z" - latency: 2.571569ms message: 'network-check-target-ip-10-0-137-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:29:16Z" - latency: 3.160486ms message: 'network-check-target-ip-10-0-137-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:28:16Z" - latency: 2.957888ms message: 'network-check-target-ip-10-0-137-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:27:16Z" - latency: 10.046178ms message: 'network-check-target-ip-10-0-137-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:26:16Z" - latency: 11.912434ms message: 'network-check-target-ip-10-0-137-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:25:16Z" - latency: 3.759125ms message: 'network-check-target-ip-10-0-137-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:24:16Z" - latency: 3.251694ms message: 'network-check-target-ip-10-0-137-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:23:16Z" - latency: 2.908602ms message: 'network-check-target-ip-10-0-137-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:22:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:42:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-193-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-193.us-east-2.compute.internal uid: 9ea84651-7274-4f82-be6f-ea3379c9f6fb resourceVersion: "187034" uid: 741c39fe-168a-46f8-b1dd-47ccc82e6203 spec: sourcePod: network-check-source-6f78d59f99-hqp48 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T21:48:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 878.587µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:36:16Z" - latency: 2.02579ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:36:16Z" - latency: 938.139µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:35:16Z" - latency: 2.560697ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:35:16Z" - latency: 1.449752ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:34:16Z" - latency: 2.571659ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:34:16Z" - latency: 1.100846ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:33:16Z" - latency: 4.022379ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:33:16Z" - latency: 1.001786ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:32:16Z" - latency: 5.542076ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:32:16Z" kind: List metadata: resourceVersion: ""