apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T03:43:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-252-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-252.us-west-2.compute.internal uid: 7abf75da-2e96-4c1a-ba96-90fcd3e094e9 resourceVersion: "89896" uid: 6c974b38-72f9-48da-a11b-e474ad06ceb6 spec: sourcePod: network-check-source-6f78d59f99-lfx6k targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-01T03:50:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.318375ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:32:44Z" - latency: 1.277441ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:31:44Z" - latency: 1.589061ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:30:44Z" - latency: 1.189185ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:29:44Z" - latency: 1.399114ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:28:44Z" - latency: 932.847µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:27:44Z" - latency: 914.648µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:26:44Z" - latency: 978.197µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:25:44Z" - latency: 1.309982ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:24:44Z" - latency: 1.309331ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:23:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T03:43:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-252-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-252.us-west-2.compute.internal uid: 7abf75da-2e96-4c1a-ba96-90fcd3e094e9 resourceVersion: "88631" uid: c2d88b74-0c7e-4125-9fc2-5d508b1a1525 spec: sourcePod: network-check-source-6f78d59f99-lfx6k targetEndpoint: afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T03:49:44Z" message: 'load-balancer-api-external: tcp connection to afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 62.022532ms message: 'load-balancer-api-external: tcp connection to afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:31:44Z" - latency: 6.264124ms message: 'load-balancer-api-external: resolved host name afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:31:44Z" - latency: 51.181548ms message: 'load-balancer-api-external: tcp connection to afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:30:44Z" - latency: 6.963419ms message: 'load-balancer-api-external: resolved host name afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:30:44Z" - latency: 53.917764ms message: 'load-balancer-api-external: tcp connection to afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:29:44Z" - latency: 11.721899ms message: 'load-balancer-api-external: resolved host name afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:29:44Z" - latency: 56.528947ms message: 'load-balancer-api-external: tcp connection to afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:28:44Z" - latency: 6.646112ms message: 'load-balancer-api-external: resolved host name afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:28:44Z" - latency: 52.582377ms message: 'load-balancer-api-external: tcp connection to afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:27:44Z" - latency: 6.248423ms message: 'load-balancer-api-external: resolved host name afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:27:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T03:43:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-252-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-252.us-west-2.compute.internal uid: 7abf75da-2e96-4c1a-ba96-90fcd3e094e9 resourceVersion: "88630" uid: 1206bc62-a96b-469b-a293-3194a3b53837 spec: sourcePod: network-check-source-6f78d59f99-lfx6k targetEndpoint: afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-01T03:49:44Z" message: 'load-balancer-api-internal: tcp connection to afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.328535ms message: 'load-balancer-api-internal: tcp connection to afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:31:44Z" - latency: 6.086564ms message: 'load-balancer-api-internal: resolved host name afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:31:44Z" - latency: 51.169331ms message: 'load-balancer-api-internal: tcp connection to afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:30:44Z" - latency: 6.801167ms message: 'load-balancer-api-internal: resolved host name afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:30:44Z" - latency: 51.552809ms message: 'load-balancer-api-internal: tcp connection to afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:29:44Z" - latency: 11.976464ms message: 'load-balancer-api-internal: resolved host name afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:29:44Z" - latency: 51.911992ms message: 'load-balancer-api-internal: tcp connection to afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:28:44Z" - latency: 6.562342ms message: 'load-balancer-api-internal: resolved host name afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:28:44Z" - latency: 52.624281ms message: 'load-balancer-api-internal: tcp connection to afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:27:44Z" - latency: 6.303003ms message: 'load-balancer-api-internal: resolved host name afdb05243526b4c0e91ef2f637640017-e887bece4d7f5b9e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-01T04:27:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T03:43:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-252-to-network-check-target-ip-10-0-128-69 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-252.us-west-2.compute.internal uid: 7abf75da-2e96-4c1a-ba96-90fcd3e094e9 resourceVersion: "89894" uid: 8eee37e4-0c53-4239-a2fd-026b6689133b spec: sourcePod: network-check-source-6f78d59f99-lfx6k targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-01T03:50:44Z" message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.627761ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:32:44Z" - latency: 2.564476ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:31:44Z" - latency: 2.547901ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:30:44Z" - latency: 2.983286ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:29:44Z" - latency: 2.514923ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:28:44Z" - latency: 2.241961ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:27:44Z" - latency: 2.274843ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:26:44Z" - latency: 2.699315ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:25:44Z" - latency: 2.937598ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:24:44Z" - latency: 2.164872ms message: 'network-check-target-ip-10-0-128-69: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:23:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T03:43:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-252-to-network-check-target-ip-10-0-129-252 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-252.us-west-2.compute.internal uid: 7abf75da-2e96-4c1a-ba96-90fcd3e094e9 resourceVersion: "89892" uid: 871a4b9b-795b-4cf7-9329-5d4be0883bae spec: sourcePod: network-check-source-6f78d59f99-lfx6k targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-01T03:50:44Z" message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.214616ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:32:44Z" - latency: 917.077µs message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:31:44Z" - latency: 1.923371ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:30:44Z" - latency: 1.515265ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:29:44Z" - latency: 1.002643ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:28:44Z" - latency: 1.528088ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:27:44Z" - latency: 891.812µs message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:26:44Z" - latency: 1.014113ms message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:25:44Z" - latency: 820.506µs message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:24:44Z" - latency: 954.342µs message: 'network-check-target-ip-10-0-129-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:23:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T03:43:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-252-to-network-check-target-ip-10-0-136-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-252.us-west-2.compute.internal uid: 7abf75da-2e96-4c1a-ba96-90fcd3e094e9 resourceVersion: "89893" uid: 521b1924-01cb-47d5-b73e-30a66925bf5a spec: sourcePod: network-check-source-6f78d59f99-lfx6k targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-01T03:50:44Z" message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.821507ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:32:44Z" - latency: 2.263668ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:31:44Z" - latency: 2.309993ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:30:44Z" - latency: 2.59159ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:29:44Z" - latency: 2.368349ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:28:44Z" - latency: 2.356738ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:27:44Z" - latency: 2.523184ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:26:44Z" - latency: 2.230661ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:25:44Z" - latency: 2.305998ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:24:44Z" - latency: 2.964114ms message: 'network-check-target-ip-10-0-136-214: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:23:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-01T03:43:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-252-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-252.us-west-2.compute.internal uid: 7abf75da-2e96-4c1a-ba96-90fcd3e094e9 resourceVersion: "88626" uid: bfadb2e1-0db1-47b5-b9f2-d63cce07f4eb spec: sourcePod: network-check-source-6f78d59f99-lfx6k targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-01T03:49:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.397862ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:31:44Z" - latency: 2.138467ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T04:31:44Z" - latency: 867.244µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:30:44Z" - latency: 2.410038ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T04:30:44Z" - latency: 1.186169ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:29:44Z" - latency: 1.970351ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T04:29:44Z" - latency: 1.072902ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:28:44Z" - latency: 2.314056ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T04:28:44Z" - latency: 1.506083ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-01T04:27:44Z" - latency: 1.778942ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-01T04:27:44Z" kind: List metadata: resourceVersion: ""