apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:21:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-193-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-193.ec2.internal uid: a8bcb655-6e32-4b56-a615-7b26b7935022 resourceVersion: "21363" uid: d48edc90-6e2f-42b9-bb8f-5edca2fe9df5 spec: sourcePod: network-check-source-989f8b8dc-zskj7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T02:28:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.132259ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:42:02Z" - latency: 1.240273ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:41:02Z" - latency: 1.018233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:40:02Z" - latency: 1.173437ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:39:02Z" - latency: 1.197365ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:38:02Z" - latency: 958.759µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:37:02Z" - latency: 971.845µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:36:02Z" - latency: 881.263µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:35:02Z" - latency: 1.110237ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:34:02Z" - latency: 1.022144ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:33:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:21:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-193-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-193.ec2.internal uid: a8bcb655-6e32-4b56-a615-7b26b7935022 resourceVersion: "20037" uid: 2a5f05c3-c836-4350-a1a2-83892c04f363 spec: sourcePod: network-check-source-989f8b8dc-zskj7 targetEndpoint: a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T02:27:02Z" message: 'load-balancer-api-external: tcp connection to a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.885923ms message: 'load-balancer-api-external: tcp connection to a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:39:02Z" - latency: 8.965082ms message: 'load-balancer-api-external: resolved host name a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:39:02Z" - latency: 4.703873ms message: 'load-balancer-api-external: tcp connection to a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:38:02Z" - latency: 9.177535ms message: 'load-balancer-api-external: resolved host name a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:38:02Z" - latency: 5.362918ms message: 'load-balancer-api-external: tcp connection to a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:37:02Z" - latency: 8.5028ms message: 'load-balancer-api-external: resolved host name a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:37:02Z" - latency: 4.358678ms message: 'load-balancer-api-external: tcp connection to a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:36:02Z" - latency: 11.980296ms message: 'load-balancer-api-external: resolved host name a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:36:02Z" - latency: 4.316922ms message: 'load-balancer-api-external: tcp connection to a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:35:02Z" - latency: 8.051943ms message: 'load-balancer-api-external: resolved host name a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:35:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:21:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-193-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-193.ec2.internal uid: a8bcb655-6e32-4b56-a615-7b26b7935022 resourceVersion: "20036" uid: 05694a62-234e-4049-ae1d-a6656b6f9e52 spec: sourcePod: network-check-source-989f8b8dc-zskj7 targetEndpoint: a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T02:27:02Z" message: 'load-balancer-api-internal: tcp connection to a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.886011ms message: 'load-balancer-api-internal: tcp connection to a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:39:02Z" - latency: 9.023077ms message: 'load-balancer-api-internal: resolved host name a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:39:02Z" - latency: 4.704864ms message: 'load-balancer-api-internal: tcp connection to a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:38:02Z" - latency: 9.254564ms message: 'load-balancer-api-internal: resolved host name a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:38:02Z" - latency: 4.234297ms message: 'load-balancer-api-internal: tcp connection to a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:37:02Z" - latency: 8.452967ms message: 'load-balancer-api-internal: resolved host name a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:37:02Z" - latency: 4.673419ms message: 'load-balancer-api-internal: tcp connection to a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:36:02Z" - latency: 11.908829ms message: 'load-balancer-api-internal: resolved host name a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:36:02Z" - latency: 4.330869ms message: 'load-balancer-api-internal: tcp connection to a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:35:02Z" - latency: 7.983501ms message: 'load-balancer-api-internal: resolved host name a7f4f064be4014cecbd8d1c40036b5ae-587c253c9c74a07f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T02:35:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:21:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-193-to-network-check-target-ip-10-0-133-208 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-193.ec2.internal uid: a8bcb655-6e32-4b56-a615-7b26b7935022 resourceVersion: "21362" uid: 157dbb33-2522-44ea-a04e-41e455c075ee spec: sourcePod: network-check-source-989f8b8dc-zskj7 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T02:28:02Z" message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.875012ms message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:42:02Z" - latency: 2.294527ms message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:41:02Z" - latency: 2.368189ms message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:40:02Z" - latency: 2.133663ms message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:39:02Z" - latency: 2.107338ms message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:38:02Z" - latency: 2.330594ms message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:37:02Z" - latency: 2.099834ms message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:36:02Z" - latency: 2.79869ms message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:35:02Z" - latency: 2.362056ms message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:34:02Z" - latency: 2.495471ms message: 'network-check-target-ip-10-0-133-208: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:33:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:21:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-193-to-network-check-target-ip-10-0-136-193 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-193.ec2.internal uid: a8bcb655-6e32-4b56-a615-7b26b7935022 resourceVersion: "21360" uid: 3aacf610-4e90-489c-b864-8e1c69649be4 spec: sourcePod: network-check-source-989f8b8dc-zskj7 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T02:28:02Z" message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.314111ms message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:42:02Z" - latency: 1.271519ms message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:41:02Z" - latency: 1.360847ms message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:40:02Z" - latency: 1.352144ms message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:39:02Z" - latency: 801.403µs message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:38:02Z" - latency: 802.846µs message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:37:02Z" - latency: 952.583µs message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:36:02Z" - latency: 1.03611ms message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:35:02Z" - latency: 1.052133ms message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:34:02Z" - latency: 866.735µs message: 'network-check-target-ip-10-0-136-193: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:33:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:21:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-193-to-network-check-target-ip-10-0-142-238 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-193.ec2.internal uid: a8bcb655-6e32-4b56-a615-7b26b7935022 resourceVersion: "21361" uid: 05aaf816-c734-419b-a470-a581bf1adf63 spec: sourcePod: network-check-source-989f8b8dc-zskj7 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T02:28:02Z" message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.432681ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:42:02Z" - latency: 2.326716ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:41:02Z" - latency: 2.526271ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:40:02Z" - latency: 2.252631ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:39:02Z" - latency: 2.143932ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:38:02Z" - latency: 2.334237ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:37:02Z" - latency: 1.946411ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:36:02Z" - latency: 2.647204ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:35:02Z" - latency: 2.404105ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:34:02Z" - latency: 2.308222ms message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:33:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:21:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-193-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-193.ec2.internal uid: a8bcb655-6e32-4b56-a615-7b26b7935022 resourceVersion: "20035" uid: db3a48f0-d2c5-459d-930f-bf961cdae50f spec: sourcePod: network-check-source-989f8b8dc-zskj7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T02:27:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 958.925µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:39:02Z" - latency: 1.922356ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T02:39:02Z" - latency: 1.145287ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:38:02Z" - latency: 1.675951ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T02:38:02Z" - latency: 981.188µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:37:02Z" - latency: 2.273667ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T02:37:02Z" - latency: 801.228µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:36:02Z" - latency: 2.257965ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T02:36:02Z" - latency: 1.135987ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T02:35:02Z" - latency: 1.649246ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T02:35:02Z" kind: List metadata: resourceVersion: ""