apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:05:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-5-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-5.ec2.internal uid: 4a26bc1d-534c-4f03-9247-3c7a7828dc25 resourceVersion: "55692" uid: f25a1d23-b85c-4644-bb22-f5dbae90f678 spec: sourcePod: network-check-source-989f8b8dc-6grcx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T04:12:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 862.635µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:40:13Z" - latency: 965.7µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:39:13Z" - latency: 1.048485ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:38:13Z" - latency: 1.617254ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:37:13Z" - latency: 1.11199ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:36:13Z" - latency: 1.107643ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:35:13Z" - latency: 1.082357ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:34:13Z" - latency: 1.236726ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:33:13Z" - latency: 1.05312ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:32:13Z" - latency: 984.084µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:31:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:05:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-5-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-5.ec2.internal uid: 4a26bc1d-534c-4f03-9247-3c7a7828dc25 resourceVersion: "56650" uid: a8cf6a0d-50f1-42d0-a618-6295e1801edb spec: sourcePod: network-check-source-989f8b8dc-6grcx targetEndpoint: acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T04:11:13Z" message: 'load-balancer-api-external: tcp connection to acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.032219ms message: 'load-balancer-api-external: tcp connection to acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:41:13Z" - latency: 11.817762ms message: 'load-balancer-api-external: resolved host name acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:41:13Z" - latency: 5.321683ms message: 'load-balancer-api-external: tcp connection to acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:40:13Z" - latency: 19.045086ms message: 'load-balancer-api-external: resolved host name acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:40:13Z" - latency: 4.020558ms message: 'load-balancer-api-external: tcp connection to acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:39:13Z" - latency: 8.309212ms message: 'load-balancer-api-external: resolved host name acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:39:13Z" - latency: 5.008128ms message: 'load-balancer-api-external: tcp connection to acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:38:13Z" - latency: 9.527728ms message: 'load-balancer-api-external: resolved host name acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:38:13Z" - latency: 4.241486ms message: 'load-balancer-api-external: tcp connection to acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:37:13Z" - latency: 8.494906ms message: 'load-balancer-api-external: resolved host name acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:37:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:05:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-5-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-5.ec2.internal uid: 4a26bc1d-534c-4f03-9247-3c7a7828dc25 resourceVersion: "56651" uid: e4c20e36-33cc-43c4-b81f-d380d5f5d15c spec: sourcePod: network-check-source-989f8b8dc-6grcx targetEndpoint: acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T04:11:13Z" message: 'load-balancer-api-internal: tcp connection to acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.011862ms message: 'load-balancer-api-internal: tcp connection to acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:41:13Z" - latency: 11.841297ms message: 'load-balancer-api-internal: resolved host name acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:41:13Z" - latency: 5.295899ms message: 'load-balancer-api-internal: tcp connection to acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:40:13Z" - latency: 19.070374ms message: 'load-balancer-api-internal: resolved host name acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:40:13Z" - latency: 4.035143ms message: 'load-balancer-api-internal: tcp connection to acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:39:13Z" - latency: 8.402688ms message: 'load-balancer-api-internal: resolved host name acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:39:13Z" - latency: 5.539507ms message: 'load-balancer-api-internal: tcp connection to acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:38:13Z" - latency: 9.572409ms message: 'load-balancer-api-internal: resolved host name acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:38:13Z" - latency: 6.402796ms message: 'load-balancer-api-internal: tcp connection to acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:37:13Z" - latency: 8.437406ms message: 'load-balancer-api-internal: resolved host name acfa7feb7741b4a30b7de00bedaadd03-e4ea14aa04db216f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T04:37:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:05:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-5-to-network-check-target-ip-10-0-135-255 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-5.ec2.internal uid: 4a26bc1d-534c-4f03-9247-3c7a7828dc25 resourceVersion: "55691" uid: 2999efe3-1dae-42a3-b6e1-428933e9f8b7 spec: sourcePod: network-check-source-989f8b8dc-6grcx targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T04:12:13Z" message: 'network-check-target-ip-10-0-135-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.180647ms message: 'network-check-target-ip-10-0-135-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:40:13Z" - latency: 2.322523ms message: 'network-check-target-ip-10-0-135-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:39:13Z" - latency: 1.945786ms message: 'network-check-target-ip-10-0-135-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:38:13Z" - latency: 2.693731ms message: 'network-check-target-ip-10-0-135-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:37:13Z" - latency: 2.00979ms message: 'network-check-target-ip-10-0-135-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:36:13Z" - latency: 2.223184ms message: 'network-check-target-ip-10-0-135-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:35:13Z" - latency: 1.924042ms message: 'network-check-target-ip-10-0-135-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:34:13Z" - latency: 2.216844ms message: 'network-check-target-ip-10-0-135-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:33:13Z" - latency: 2.207219ms message: 'network-check-target-ip-10-0-135-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:32:13Z" - latency: 2.07348ms message: 'network-check-target-ip-10-0-135-255: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:31:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:05:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-5-to-network-check-target-ip-10-0-137-39 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-5.ec2.internal uid: 4a26bc1d-534c-4f03-9247-3c7a7828dc25 resourceVersion: "55690" uid: 4d3d6546-ec46-42eb-b432-24a06431352e spec: sourcePod: network-check-source-989f8b8dc-6grcx targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T04:12:13Z" message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.902829ms message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:40:13Z" - latency: 2.175661ms message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:39:13Z" - latency: 2.07846ms message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:38:13Z" - latency: 1.986031ms message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:37:13Z" - latency: 2.017118ms message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:36:13Z" - latency: 1.992457ms message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:35:13Z" - latency: 1.580207ms message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:34:13Z" - latency: 2.001548ms message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:33:13Z" - latency: 2.152896ms message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:32:13Z" - latency: 1.626158ms message: 'network-check-target-ip-10-0-137-39: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:31:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:05:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-5-to-network-check-target-ip-10-0-142-5 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-5.ec2.internal uid: 4a26bc1d-534c-4f03-9247-3c7a7828dc25 resourceVersion: "55689" uid: cec70c4c-26df-4f21-acb1-cd417400ca33 spec: sourcePod: network-check-source-989f8b8dc-6grcx targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T04:12:13Z" message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 877.962µs message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:40:13Z" - latency: 876.787µs message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:39:13Z" - latency: 771.633µs message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:38:13Z" - latency: 1.252797ms message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:37:13Z" - latency: 785.096µs message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:36:13Z" - latency: 835.935µs message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:35:13Z" - latency: 864.677µs message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:34:13Z" - latency: 881.482µs message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:33:13Z" - latency: 1.348002ms message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:32:13Z" - latency: 829.032µs message: 'network-check-target-ip-10-0-142-5: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:31:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T04:05:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-5-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-5.ec2.internal uid: 4a26bc1d-534c-4f03-9247-3c7a7828dc25 resourceVersion: "56649" uid: 17409e83-d744-445b-b68d-d1b8194a1504 spec: sourcePod: network-check-source-989f8b8dc-6grcx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T04:11:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.156395ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:41:13Z" - latency: 1.640447ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T04:41:13Z" - latency: 970.387µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:40:13Z" - latency: 1.851986ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T04:40:13Z" - latency: 820.836µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:39:13Z" - latency: 1.776294ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T04:39:13Z" - latency: 849.617µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:38:13Z" - latency: 1.781101ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T04:38:13Z" - latency: 954.974µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T04:37:13Z" - latency: 1.81821ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T04:37:13Z" kind: List metadata: resourceVersion: ""