apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:22:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-205-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-205.ec2.internal uid: 2e9bab92-5652-456b-9cbe-cf6048339e98 resourceVersion: "44140" uid: d8f96472-0674-48e1-87e6-895ac9d5afa2 spec: sourcePod: network-check-source-7f44b6dd87-x8mrk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T17:29:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 958.257µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:50:16Z" - latency: 1.062198ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:49:16Z" - latency: 1.097464ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:16Z" - latency: 1.137132ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:16Z" - latency: 814.392µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:46:16Z" - latency: 1.045569ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:45:16Z" - latency: 1.023277ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:44:16Z" - latency: 804.384µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:16Z" - latency: 845.055µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:16Z" - latency: 793.014µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:22:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-205-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-205.ec2.internal uid: 2e9bab92-5652-456b-9cbe-cf6048339e98 resourceVersion: "46363" uid: 2dc32b2b-8a45-4155-ae2d-8ada8c9ac25a spec: sourcePod: network-check-source-7f44b6dd87-x8mrk targetEndpoint: a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T17:28:16Z" message: 'load-balancer-api-external: tcp connection to a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.866751ms message: 'load-balancer-api-external: tcp connection to a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:52:16Z" - latency: 11.126851ms message: 'load-balancer-api-external: resolved host name a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:52:16Z" - latency: 4.588344ms message: 'load-balancer-api-external: tcp connection to a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:51:16Z" - latency: 9.411045ms message: 'load-balancer-api-external: resolved host name a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:51:16Z" - latency: 3.721864ms message: 'load-balancer-api-external: tcp connection to a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:50:16Z" - latency: 10.258514ms message: 'load-balancer-api-external: resolved host name a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:50:16Z" - latency: 4.255447ms message: 'load-balancer-api-external: tcp connection to a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:49:16Z" - latency: 9.08552ms message: 'load-balancer-api-external: resolved host name a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:49:16Z" - latency: 4.755194ms message: 'load-balancer-api-external: tcp connection to a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:16Z" - latency: 8.658144ms message: 'load-balancer-api-external: resolved host name a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:48:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:22:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-205-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-205.ec2.internal uid: 2e9bab92-5652-456b-9cbe-cf6048339e98 resourceVersion: "46362" uid: 3d3b35e4-5b41-4acb-b8aa-e601bf3d6544 spec: sourcePod: network-check-source-7f44b6dd87-x8mrk targetEndpoint: a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T17:28:16Z" message: 'load-balancer-api-internal: tcp connection to a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.959178ms message: 'load-balancer-api-internal: tcp connection to a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:52:16Z" - latency: 11.106545ms message: 'load-balancer-api-internal: resolved host name a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:52:16Z" - latency: 4.584034ms message: 'load-balancer-api-internal: tcp connection to a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:51:16Z" - latency: 9.498757ms message: 'load-balancer-api-internal: resolved host name a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:51:16Z" - latency: 3.647393ms message: 'load-balancer-api-internal: tcp connection to a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:50:16Z" - latency: 10.38176ms message: 'load-balancer-api-internal: resolved host name a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:50:16Z" - latency: 4.428842ms message: 'load-balancer-api-internal: tcp connection to a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:49:16Z" - latency: 8.999732ms message: 'load-balancer-api-internal: resolved host name a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:49:16Z" - latency: 4.779868ms message: 'load-balancer-api-internal: tcp connection to a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:16Z" - latency: 8.617395ms message: 'load-balancer-api-internal: resolved host name a7f197230aebd41429b7afe658c090c0-dcee11fee9840af9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T17:48:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:22:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-205-to-network-check-target-ip-10-0-130-182 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-205.ec2.internal uid: 2e9bab92-5652-456b-9cbe-cf6048339e98 resourceVersion: "44139" uid: 9ab8f94b-da74-49c8-819a-fe2d6c4e1c4f spec: sourcePod: network-check-source-7f44b6dd87-x8mrk targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T17:29:16Z" message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.512226ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:50:16Z" - latency: 2.306687ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:49:16Z" - latency: 2.334544ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:16Z" - latency: 2.266423ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:16Z" - latency: 2.246766ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:46:16Z" - latency: 2.163018ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:45:16Z" - latency: 2.015576ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:44:16Z" - latency: 2.375386ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:16Z" - latency: 2.02081ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:16Z" - latency: 1.915745ms message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:22:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-205-to-network-check-target-ip-10-0-133-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-205.ec2.internal uid: 2e9bab92-5652-456b-9cbe-cf6048339e98 resourceVersion: "44137" uid: 98c927e5-e963-47a2-a725-cad9a0d9f346 spec: sourcePod: network-check-source-7f44b6dd87-x8mrk targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-28T17:29:16Z" message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.239073ms message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:50:16Z" - latency: 830.444µs message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:49:16Z" - latency: 762.262µs message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:16Z" - latency: 803.873µs message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:16Z" - latency: 813.304µs message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:46:16Z" - latency: 1.154635ms message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:45:16Z" - latency: 959.592µs message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:44:16Z" - latency: 715.45µs message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:16Z" - latency: 734.421µs message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:16Z" - latency: 1.07943ms message: 'network-check-target-ip-10-0-133-205: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:22:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-205-to-network-check-target-ip-10-0-139-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-205.ec2.internal uid: 2e9bab92-5652-456b-9cbe-cf6048339e98 resourceVersion: "44138" uid: bb68af16-d360-4b65-acca-752a0538a86a spec: sourcePod: network-check-source-7f44b6dd87-x8mrk targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T17:29:16Z" message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.13369ms message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:50:16Z" - latency: 1.957296ms message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:49:16Z" - latency: 2.092964ms message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:16Z" - latency: 2.195037ms message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:47:16Z" - latency: 1.877633ms message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:46:16Z" - latency: 2.147429ms message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:45:16Z" - latency: 2.282992ms message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:44:16Z" - latency: 2.003275ms message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:43:16Z" - latency: 1.745331ms message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:42:16Z" - latency: 2.354002ms message: 'network-check-target-ip-10-0-139-178: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:41:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:22:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-205-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-205.ec2.internal uid: 2e9bab92-5652-456b-9cbe-cf6048339e98 resourceVersion: "46361" uid: c15b6640-3f49-4baa-859e-3aa59254ab31 spec: sourcePod: network-check-source-7f44b6dd87-x8mrk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T17:28:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 763.833µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:52:16Z" - latency: 1.773636ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:52:16Z" - latency: 792.688µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:51:16Z" - latency: 1.926837ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:51:16Z" - latency: 934.464µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:50:16Z" - latency: 1.580117ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:50:16Z" - latency: 966.652µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:49:16Z" - latency: 1.729161ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:49:16Z" - latency: 883.927µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T17:48:16Z" - latency: 1.634475ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T17:48:16Z" kind: List metadata: resourceVersion: ""