apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-219-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-219.ec2.internal uid: c2499524-8f5e-4c01-bd5b-11f6580d083a resourceVersion: "20232" uid: 8e36d86e-4f87-4958-a34c-9116421a603b spec: sourcePod: network-check-source-dbd9cf844-g66cw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T12:19:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 840.373µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:33:57Z" - latency: 913.561µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:32:57Z" - latency: 798.373µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:31:57Z" - latency: 1.098797ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:30:57Z" - latency: 993.869µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:29:57Z" - latency: 1.368384ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:28:57Z" - latency: 1.250237ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:27:57Z" - latency: 1.140015ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:26:57Z" - latency: 864.058µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:25:57Z" - latency: 1.079145ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:24:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-219-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-219.ec2.internal uid: c2499524-8f5e-4c01-bd5b-11f6580d083a resourceVersion: "21682" uid: 5f9c55e9-fbf5-4eaa-91bd-b3dd716b3527 spec: sourcePod: network-check-source-dbd9cf844-g66cw targetEndpoint: a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T12:18:57Z" message: 'load-balancer-api-external: tcp connection to a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.829612ms message: 'load-balancer-api-external: tcp connection to a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:36:57Z" - latency: 7.067041ms message: 'load-balancer-api-external: resolved host name a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:36:57Z" - latency: 4.921104ms message: 'load-balancer-api-external: tcp connection to a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:35:57Z" - latency: 6.872262ms message: 'load-balancer-api-external: resolved host name a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:35:57Z" - latency: 6.295012ms message: 'load-balancer-api-external: tcp connection to a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:34:57Z" - latency: 6.318526ms message: 'load-balancer-api-external: resolved host name a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:34:57Z" - latency: 5.100809ms message: 'load-balancer-api-external: tcp connection to a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:33:57Z" - latency: 7.118967ms message: 'load-balancer-api-external: resolved host name a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:33:57Z" - latency: 4.928889ms message: 'load-balancer-api-external: tcp connection to a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:32:57Z" - latency: 6.355124ms message: 'load-balancer-api-external: resolved host name a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:32:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-219-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-219.ec2.internal uid: c2499524-8f5e-4c01-bd5b-11f6580d083a resourceVersion: "21683" uid: 1f0ac195-a601-4ea4-8ea8-2f82ecfd3276 spec: sourcePod: network-check-source-dbd9cf844-g66cw targetEndpoint: a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T12:18:57Z" message: 'load-balancer-api-internal: tcp connection to a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.531992ms message: 'load-balancer-api-internal: tcp connection to a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:36:57Z" - latency: 7.03633ms message: 'load-balancer-api-internal: resolved host name a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:36:57Z" - latency: 4.373561ms message: 'load-balancer-api-internal: tcp connection to a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:35:57Z" - latency: 6.846926ms message: 'load-balancer-api-internal: resolved host name a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:35:57Z" - latency: 5.285945ms message: 'load-balancer-api-internal: tcp connection to a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:34:57Z" - latency: 6.268124ms message: 'load-balancer-api-internal: resolved host name a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:34:57Z" - latency: 5.119087ms message: 'load-balancer-api-internal: tcp connection to a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:33:57Z" - latency: 7.030657ms message: 'load-balancer-api-internal: resolved host name a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:33:57Z" - latency: 4.937653ms message: 'load-balancer-api-internal: tcp connection to a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:32:57Z" - latency: 6.431236ms message: 'load-balancer-api-internal: resolved host name a4b20eeb155d04d6b9b80f12ae8d8bab-0649224764291a87.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T12:32:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-219-to-network-check-target-ip-10-0-128-216 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-219.ec2.internal uid: c2499524-8f5e-4c01-bd5b-11f6580d083a resourceVersion: "20230" uid: d9bc9f1e-1e2d-4bbb-82b5-91d9b9a69fb4 spec: sourcePod: network-check-source-dbd9cf844-g66cw targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T12:19:57Z" message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.000461ms message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:33:57Z" - latency: 2.03761ms message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:32:57Z" - latency: 1.907451ms message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:31:57Z" - latency: 1.87659ms message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:30:57Z" - latency: 2.010212ms message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:29:57Z" - latency: 1.914184ms message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:28:57Z" - latency: 2.081962ms message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:27:57Z" - latency: 2.114419ms message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:26:57Z" - latency: 2.061275ms message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:25:57Z" - latency: 2.173915ms message: 'network-check-target-ip-10-0-128-216: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:24:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-219-to-network-check-target-ip-10-0-142-219 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-219.ec2.internal uid: c2499524-8f5e-4c01-bd5b-11f6580d083a resourceVersion: "20229" uid: 5b49322c-6ec4-46da-819d-cfb6bd5937b0 spec: sourcePod: network-check-source-dbd9cf844-g66cw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T12:19:57Z" message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.127492ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:33:57Z" - latency: 731.22µs message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:32:57Z" - latency: 668.179µs message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:31:57Z" - latency: 719.078µs message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:30:57Z" - latency: 845.682µs message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:29:57Z" - latency: 775.638µs message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:28:57Z" - latency: 1.094834ms message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:27:57Z" - latency: 961.425µs message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:26:57Z" - latency: 857.387µs message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:25:57Z" - latency: 847.608µs message: 'network-check-target-ip-10-0-142-219: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:24:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-219-to-network-check-target-ip-10-0-142-230 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-219.ec2.internal uid: c2499524-8f5e-4c01-bd5b-11f6580d083a resourceVersion: "20231" uid: 0c2e47cb-7c5e-4bf4-ae5b-32df2ba92d03 spec: sourcePod: network-check-source-dbd9cf844-g66cw targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T12:19:57Z" message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.255747ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:33:57Z" - latency: 1.907279ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:32:57Z" - latency: 1.74462ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:31:57Z" - latency: 1.871176ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:30:57Z" - latency: 2.149674ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:29:57Z" - latency: 1.778776ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:28:57Z" - latency: 1.789844ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:27:57Z" - latency: 1.946183ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:26:57Z" - latency: 1.866504ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:25:57Z" - latency: 1.979837ms message: 'network-check-target-ip-10-0-142-230: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:24:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T12:12:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-219-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-219.ec2.internal uid: c2499524-8f5e-4c01-bd5b-11f6580d083a resourceVersion: "21681" uid: 7586929b-ff35-437d-8ac0-45e25023b7c2 spec: sourcePod: network-check-source-dbd9cf844-g66cw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T12:18:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 799.215µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:36:57Z" - latency: 1.735925ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:36:57Z" - latency: 878.242µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:35:57Z" - latency: 1.954664ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:35:57Z" - latency: 1.224189ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:34:57Z" - latency: 1.570732ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:34:57Z" - latency: 1.102758ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:33:57Z" - latency: 2.023304ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:33:57Z" - latency: 721.784µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T12:32:57Z" - latency: 2.349918ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T12:32:57Z" kind: List metadata: resourceVersion: ""