apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T14:47:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-60-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-60.us-west-1.compute.internal uid: 100d4bb9-44c7-4df4-b377-92bb9e3124ab resourceVersion: "174992" uid: b892ea83-9b69-48b2-bcb1-a6ddf7e4179d spec: sourcePod: network-check-source-6f78d59f99-2p6pl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T14:54:39Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.137877ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:39:39Z" - latency: 4.761294ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:38:39Z" - latency: 1.516403ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:37:39Z" - latency: 1.240307ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:36:39Z" - latency: 7.115392ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:35:39Z" - latency: 906.035µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:34:39Z" - latency: 1.076339ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:33:39Z" - latency: 5.480701ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:32:39Z" - latency: 974.74µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:31:39Z" - latency: 847µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:30:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T14:47:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-60-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-60.us-west-1.compute.internal uid: 100d4bb9-44c7-4df4-b377-92bb9e3124ab resourceVersion: "171660" uid: 012ba7ed-45d1-4d38-abc1-dde80c94d8c6 spec: sourcePod: network-check-source-6f78d59f99-2p6pl targetEndpoint: a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T14:53:39Z" message: 'load-balancer-api-external: tcp connection to a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 65.637305ms message: 'load-balancer-api-external: tcp connection to a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:35:39Z" - latency: 47.540451ms message: 'load-balancer-api-external: resolved host name a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T16:35:39Z" - latency: 54.530717ms message: 'load-balancer-api-external: tcp connection to a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:34:39Z" - latency: 6.19508ms message: 'load-balancer-api-external: resolved host name a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T16:34:39Z" - latency: 52.937897ms message: 'load-balancer-api-external: tcp connection to a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:33:39Z" - latency: 7.531678ms message: 'load-balancer-api-external: resolved host name a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T16:33:39Z" - latency: 65.23864ms message: 'load-balancer-api-external: tcp connection to a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:32:39Z" - latency: 68.217857ms message: 'load-balancer-api-external: resolved host name a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T16:32:39Z" - latency: 53.946939ms message: 'load-balancer-api-external: tcp connection to a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:31:39Z" - latency: 6.853904ms message: 'load-balancer-api-external: resolved host name a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T16:31:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T14:47:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-60-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-60.us-west-1.compute.internal uid: 100d4bb9-44c7-4df4-b377-92bb9e3124ab resourceVersion: "171661" uid: ed7c59d7-20ec-4ca4-8a62-2d81efb7ae7a spec: sourcePod: network-check-source-6f78d59f99-2p6pl targetEndpoint: a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T14:53:39Z" message: 'load-balancer-api-internal: tcp connection to a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 59.451819ms message: 'load-balancer-api-internal: tcp connection to a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:35:39Z" - latency: 48.506418ms message: 'load-balancer-api-internal: resolved host name a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T16:35:39Z" - latency: 54.545083ms message: 'load-balancer-api-internal: tcp connection to a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:34:39Z" - latency: 6.159917ms message: 'load-balancer-api-internal: resolved host name a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T16:34:39Z" - latency: 53.241913ms message: 'load-balancer-api-internal: tcp connection to a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:33:39Z" - latency: 7.564424ms message: 'load-balancer-api-internal: resolved host name a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T16:33:39Z" - latency: 64.869256ms message: 'load-balancer-api-internal: tcp connection to a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:32:39Z" - latency: 61.586633ms message: 'load-balancer-api-internal: resolved host name a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T16:32:39Z" - latency: 53.957822ms message: 'load-balancer-api-internal: tcp connection to a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:31:39Z" - latency: 6.814509ms message: 'load-balancer-api-internal: resolved host name a512747cf7570402090f1cd78c56a05b-54c583efd5dcf322.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T16:31:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T14:47:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-60-to-network-check-target-ip-10-0-131-60 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-60.us-west-1.compute.internal uid: 100d4bb9-44c7-4df4-b377-92bb9e3124ab resourceVersion: "174988" uid: ced2b5ec-8361-43ba-85b5-09ed4f5bc980 spec: sourcePod: network-check-source-6f78d59f99-2p6pl targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T14:54:39Z" message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.131592ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:39:39Z" - latency: 4.546715ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:38:39Z" - latency: 1.695397ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:37:39Z" - latency: 1.514146ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:36:39Z" - latency: 7.955413ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:35:39Z" - latency: 1.061897ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:34:39Z" - latency: 918.895µs message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:33:39Z" - latency: 14.945751ms message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:32:39Z" - latency: 970.309µs message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:31:39Z" - latency: 912.162µs message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:30:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T14:47:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-60-to-network-check-target-ip-10-0-137-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-60.us-west-1.compute.internal uid: 100d4bb9-44c7-4df4-b377-92bb9e3124ab resourceVersion: "174989" uid: 9b348a6f-5fee-405c-9713-683f140ae4df spec: sourcePod: network-check-source-6f78d59f99-2p6pl targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T14:54:39Z" message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.989911ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:39:39Z" - latency: 21.69572ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:38:39Z" - latency: 2.271109ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:37:39Z" - latency: 2.225664ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:36:39Z" - latency: 7.789812ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:35:39Z" - latency: 1.894481ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:34:39Z" - latency: 2.34236ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:33:39Z" - latency: 20.679506ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:32:39Z" - latency: 2.202259ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:31:39Z" - latency: 2.309427ms message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:30:39Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T16:14:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-60-to-network-check-target-ip-10-0-139-115 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-60.us-west-1.compute.internal uid: 100d4bb9-44c7-4df4-b377-92bb9e3124ab resourceVersion: "171215" uid: b89679c4-e76f-4b30-9a47-c5157724036d spec: sourcePod: network-check-source-6f78d59f99-2p6pl targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T16:21:00Z" message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.556651ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:35:00Z" - latency: 2.236103ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:34:00Z" - latency: 2.611762ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:33:00Z" - latency: 2.566796ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:32:00Z" - latency: 2.695506ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:31:00Z" - latency: 2.044306ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:30:00Z" - latency: 2.624152ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:29:00Z" - latency: 2.567045ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:28:00Z" - latency: 2.443516ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:27:00Z" - latency: 2.979351ms message: 'network-check-target-ip-10-0-139-115: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:26:00Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T14:47:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-60-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-60.us-west-1.compute.internal uid: 100d4bb9-44c7-4df4-b377-92bb9e3124ab resourceVersion: "171659" uid: 3a08f8d8-333e-45a8-b1bb-2207e8e850a7 spec: sourcePod: network-check-source-6f78d59f99-2p6pl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T14:53:39Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 10.196382ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:35:39Z" - latency: 7.723914ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T16:35:39Z" - latency: 953.997µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:34:39Z" - latency: 1.901287ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T16:34:39Z" - latency: 926.221µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:33:39Z" - latency: 2.46307ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T16:33:39Z" - latency: 13.059672ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:32:39Z" - latency: 20.172704ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T16:32:39Z" - latency: 902.481µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T16:31:39Z" - latency: 2.208017ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T16:31:39Z" kind: List metadata: resourceVersion: ""