apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T18:40:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-95-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-95.us-west-2.compute.internal uid: 171f3884-1116-46df-bcce-f27e5047c4bf resourceVersion: "108268" uid: 5db291c3-0ca1-4041-bf2f-f27b9018bb9a spec: sourcePod: network-check-source-6f78d59f99-tqhrb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T18:47:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.294855ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:50:15Z" - latency: 1.228735ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:49:15Z" - latency: 974.021µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:48:15Z" - latency: 879.248µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:47:15Z" - latency: 1.463313ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:46:15Z" - latency: 1.180795ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:45:15Z" - latency: 1.209227ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:44:15Z" - latency: 1.025635ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:43:15Z" - latency: 1.295215ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:42:15Z" - latency: 1.039466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:41:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T18:40:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-95-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-95.us-west-2.compute.internal uid: 171f3884-1116-46df-bcce-f27e5047c4bf resourceVersion: "105514" uid: e4408dbc-f928-4dfd-8fcc-0fece5f6e271 spec: sourcePod: network-check-source-6f78d59f99-tqhrb targetEndpoint: acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T18:46:15Z" message: 'load-balancer-api-external: tcp connection to acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.758481ms message: 'load-balancer-api-external: tcp connection to acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:46:15Z" - latency: 9.460041ms message: 'load-balancer-api-external: resolved host name acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:46:15Z" - latency: 56.353787ms message: 'load-balancer-api-external: tcp connection to acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:45:15Z" - latency: 6.863798ms message: 'load-balancer-api-external: resolved host name acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:45:15Z" - latency: 49.467789ms message: 'load-balancer-api-external: tcp connection to acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:44:15Z" - latency: 6.750045ms message: 'load-balancer-api-external: resolved host name acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:44:15Z" - latency: 51.002087ms message: 'load-balancer-api-external: tcp connection to acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:43:15Z" - latency: 7.288679ms message: 'load-balancer-api-external: resolved host name acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:43:15Z" - latency: 54.474608ms message: 'load-balancer-api-external: tcp connection to acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:42:15Z" - latency: 7.064145ms message: 'load-balancer-api-external: resolved host name acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:42:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T18:40:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-95-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-95.us-west-2.compute.internal uid: 171f3884-1116-46df-bcce-f27e5047c4bf resourceVersion: "105515" uid: d3ba1550-eab3-4096-a00e-2b68e7f155f4 spec: sourcePod: network-check-source-6f78d59f99-tqhrb targetEndpoint: acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T18:46:15Z" message: 'load-balancer-api-internal: tcp connection to acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.305254ms message: 'load-balancer-api-internal: tcp connection to acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:46:15Z" - latency: 9.417442ms message: 'load-balancer-api-internal: resolved host name acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:46:15Z" - latency: 56.927355ms message: 'load-balancer-api-internal: tcp connection to acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:45:15Z" - latency: 6.794954ms message: 'load-balancer-api-internal: resolved host name acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:45:15Z" - latency: 53.455094ms message: 'load-balancer-api-internal: tcp connection to acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:44:15Z" - latency: 6.657005ms message: 'load-balancer-api-internal: resolved host name acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:44:15Z" - latency: 54.126228ms message: 'load-balancer-api-internal: tcp connection to acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:43:15Z" - latency: 7.266427ms message: 'load-balancer-api-internal: resolved host name acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:43:15Z" - latency: 53.904124ms message: 'load-balancer-api-internal: tcp connection to acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:42:15Z" - latency: 7.010943ms message: 'load-balancer-api-internal: resolved host name acc3b4ca8eba54ce98364924c8229c13-670cf6387112f978.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T19:42:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T18:40:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-95-to-network-check-target-ip-10-0-128-95 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-95.us-west-2.compute.internal uid: 171f3884-1116-46df-bcce-f27e5047c4bf resourceVersion: "108264" uid: 26cf2fcf-dd0d-4efc-bcd6-c499f9f5f96d spec: sourcePod: network-check-source-6f78d59f99-tqhrb targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T18:47:15Z" message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.62059ms message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:50:15Z" - latency: 982.366µs message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:49:15Z" - latency: 1.320225ms message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:48:15Z" - latency: 842.675µs message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:47:15Z" - latency: 1.07579ms message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:46:15Z" - latency: 1.085709ms message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:45:15Z" - latency: 1.057004ms message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:44:15Z" - latency: 1.025638ms message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:43:15Z" - latency: 994.656µs message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:42:15Z" - latency: 1.317618ms message: 'network-check-target-ip-10-0-128-95: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:41:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T18:40:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-95-to-network-check-target-ip-10-0-139-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-95.us-west-2.compute.internal uid: 171f3884-1116-46df-bcce-f27e5047c4bf resourceVersion: "108267" uid: b478cc14-3be5-4931-90d4-a1b4ce73e624 spec: sourcePod: network-check-source-6f78d59f99-tqhrb targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T18:47:15Z" message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.213388ms message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:50:15Z" - latency: 2.168427ms message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:49:15Z" - latency: 2.794092ms message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:48:15Z" - latency: 1.924482ms message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:47:15Z" - latency: 2.498915ms message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:46:15Z" - latency: 2.406976ms message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:45:15Z" - latency: 2.497425ms message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:44:15Z" - latency: 2.492298ms message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:43:15Z" - latency: 2.397814ms message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:42:15Z" - latency: 2.628764ms message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:41:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T18:40:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-95-to-network-check-target-ip-10-0-143-45 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-95.us-west-2.compute.internal uid: 171f3884-1116-46df-bcce-f27e5047c4bf resourceVersion: "108265" uid: 31cf689f-450b-4353-bcb6-171469282da6 spec: sourcePod: network-check-source-6f78d59f99-tqhrb targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T18:47:15Z" message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.460341ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:50:15Z" - latency: 2.382436ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:49:15Z" - latency: 2.15467ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:48:15Z" - latency: 2.189822ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:47:15Z" - latency: 2.581641ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:46:15Z" - latency: 2.350691ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:45:15Z" - latency: 2.594644ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:44:15Z" - latency: 2.443612ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:43:15Z" - latency: 2.647804ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:42:15Z" - latency: 2.798025ms message: 'network-check-target-ip-10-0-143-45: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:41:15Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T18:40:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-95-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-95.us-west-2.compute.internal uid: 171f3884-1116-46df-bcce-f27e5047c4bf resourceVersion: "105512" uid: f97a4765-ecef-4d6d-a2b5-ab7320c23fc6 spec: sourcePod: network-check-source-6f78d59f99-tqhrb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T18:46:15Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.072694ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:46:15Z" - latency: 1.824714ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T19:46:15Z" - latency: 948.048µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:45:15Z" - latency: 1.871997ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T19:45:15Z" - latency: 1.614888ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:44:15Z" - latency: 1.877984ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T19:44:15Z" - latency: 1.717149ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:43:15Z" - latency: 1.810243ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T19:43:15Z" - latency: 927.529µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T19:42:15Z" - latency: 1.958653ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T19:42:15Z" kind: List metadata: resourceVersion: ""