apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T15:01:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-140-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-140.ec2.internal uid: 26a5a299-1989-450e-b6c4-9c62fe6c01fc resourceVersion: "32742" uid: 03521cf0-7c56-485e-b988-f5237c39c595 spec: sourcePod: network-check-source-7b678d77c7-whfzb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T15:08:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 962.365µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:43:11Z" - latency: 1.445491ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:42:11Z" - latency: 989.071µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:41:11Z" - latency: 973.951µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:40:11Z" - latency: 1.027727ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:39:11Z" - latency: 1.12037ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:38:11Z" - latency: 1.002165ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:37:11Z" - latency: 922.923µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:36:11Z" - latency: 1.13946ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:35:11Z" - latency: 982.56µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:34:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T15:01:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-140-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-140.ec2.internal uid: 26a5a299-1989-450e-b6c4-9c62fe6c01fc resourceVersion: "32743" uid: 57d38a95-2098-4188-b3c5-1485f217f978 spec: sourcePod: network-check-source-7b678d77c7-whfzb targetEndpoint: ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T15:07:11Z" message: 'load-balancer-api-external: tcp connection to ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.274789ms message: 'load-balancer-api-external: tcp connection to ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:43:11Z" - latency: 8.776499ms message: 'load-balancer-api-external: resolved host name ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:43:11Z" - latency: 4.398117ms message: 'load-balancer-api-external: tcp connection to ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:42:11Z" - latency: 6.667525ms message: 'load-balancer-api-external: resolved host name ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:42:11Z" - latency: 5.090729ms message: 'load-balancer-api-external: tcp connection to ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:41:11Z" - latency: 8.385702ms message: 'load-balancer-api-external: resolved host name ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:41:11Z" - latency: 4.603539ms message: 'load-balancer-api-external: tcp connection to ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:40:11Z" - latency: 8.448364ms message: 'load-balancer-api-external: resolved host name ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:40:11Z" - latency: 4.137696ms message: 'load-balancer-api-external: tcp connection to ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:39:11Z" - latency: 7.67249ms message: 'load-balancer-api-external: resolved host name ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:39:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T15:01:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-140-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-140.ec2.internal uid: 26a5a299-1989-450e-b6c4-9c62fe6c01fc resourceVersion: "32744" uid: 1074af77-6499-4491-977f-dfb697df9dec spec: sourcePod: network-check-source-7b678d77c7-whfzb targetEndpoint: ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T15:07:11Z" message: 'load-balancer-api-internal: tcp connection to ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.264082ms message: 'load-balancer-api-internal: tcp connection to ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:43:11Z" - latency: 8.824865ms message: 'load-balancer-api-internal: resolved host name ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:43:11Z" - latency: 6.325636ms message: 'load-balancer-api-internal: tcp connection to ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:42:11Z" - latency: 6.74681ms message: 'load-balancer-api-internal: resolved host name ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:42:11Z" - latency: 5.105956ms message: 'load-balancer-api-internal: tcp connection to ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:41:11Z" - latency: 8.461325ms message: 'load-balancer-api-internal: resolved host name ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:41:11Z" - latency: 4.896433ms message: 'load-balancer-api-internal: tcp connection to ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:40:11Z" - latency: 8.535577ms message: 'load-balancer-api-internal: resolved host name ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:40:11Z" - latency: 5.491707ms message: 'load-balancer-api-internal: tcp connection to ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:39:11Z" - latency: 7.72646ms message: 'load-balancer-api-internal: resolved host name ab9e3902f7bd848f1b89e2372ad270fd-c3ed3a216f8cd9c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T15:39:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T15:01:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-140-to-network-check-target-ip-10-0-129-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-140.ec2.internal uid: 26a5a299-1989-450e-b6c4-9c62fe6c01fc resourceVersion: "32740" uid: 02d2b555-0082-4c27-a61d-c3580ef21d5f spec: sourcePod: network-check-source-7b678d77c7-whfzb targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T15:08:11Z" message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.397334ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:43:11Z" - latency: 2.338885ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:42:11Z" - latency: 2.128934ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:41:11Z" - latency: 2.432888ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:40:11Z" - latency: 2.557081ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:39:11Z" - latency: 2.213254ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:38:11Z" - latency: 1.920627ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:37:11Z" - latency: 2.441585ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:36:11Z" - latency: 2.359137ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:35:11Z" - latency: 2.214074ms message: 'network-check-target-ip-10-0-129-105: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:34:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T15:01:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-140-to-network-check-target-ip-10-0-130-140 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-140.ec2.internal uid: 26a5a299-1989-450e-b6c4-9c62fe6c01fc resourceVersion: "32738" uid: c78f9626-a16f-4444-9edf-1ce8dd34e7af spec: sourcePod: network-check-source-7b678d77c7-whfzb targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T15:08:11Z" message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.210136ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:43:11Z" - latency: 889.229µs message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:42:11Z" - latency: 827.279µs message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:41:11Z" - latency: 884.036µs message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:40:11Z" - latency: 851.88µs message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:39:11Z" - latency: 838.576µs message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:38:11Z" - latency: 856.945µs message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:37:11Z" - latency: 1.173483ms message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:36:11Z" - latency: 842.26µs message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:35:11Z" - latency: 873.127µs message: 'network-check-target-ip-10-0-130-140: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:34:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T15:01:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-140-to-network-check-target-ip-10-0-130-229 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-140.ec2.internal uid: 26a5a299-1989-450e-b6c4-9c62fe6c01fc resourceVersion: "32739" uid: 0e4ccf4c-49d5-49aa-85ec-2841e95e68db spec: sourcePod: network-check-source-7b678d77c7-whfzb targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T15:08:11Z" message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.162265ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:43:11Z" - latency: 2.065899ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:42:11Z" - latency: 1.89085ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:41:11Z" - latency: 1.872646ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:40:11Z" - latency: 2.05717ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:39:11Z" - latency: 2.040465ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:38:11Z" - latency: 2.16748ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:37:11Z" - latency: 1.913304ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:36:11Z" - latency: 1.980915ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:35:11Z" - latency: 1.897468ms message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:34:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T15:01:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-140-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-140.ec2.internal uid: 26a5a299-1989-450e-b6c4-9c62fe6c01fc resourceVersion: "32741" uid: 6705fc03-3847-4837-92f6-5be7d8267f09 spec: sourcePod: network-check-source-7b678d77c7-whfzb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T15:07:11Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 911.654µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:43:11Z" - latency: 2.292364ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T15:43:11Z" - latency: 737.268µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:42:11Z" - latency: 2.016732ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T15:42:11Z" - latency: 838.811µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:41:11Z" - latency: 1.877008ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T15:41:11Z" - latency: 906.664µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:40:11Z" - latency: 1.79487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T15:40:11Z" - latency: 1.130912ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T15:39:11Z" - latency: 1.674894ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T15:39:11Z" kind: List metadata: resourceVersion: ""