apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:53:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-107-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-107.ec2.internal uid: 6609f4d1-cc69-467a-9db2-3890ab7114da resourceVersion: "22320" uid: b01e3ac7-8455-400d-a7eb-7c090e00bc3c spec: sourcePod: network-check-source-8894fc9bd-v5kgg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-23T18:00:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 726.626µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:14:24Z" - latency: 1.023971ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:13:24Z" - latency: 830.612µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:12:24Z" - latency: 979.79µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:11:24Z" - latency: 948.382µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:10:24Z" - latency: 895.24µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:09:24Z" - latency: 863.805µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:08:24Z" - latency: 1.176361ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:07:24Z" - latency: 907.924µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:06:24Z" - latency: 989.397µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:05:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:53:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-107-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-107.ec2.internal uid: 6609f4d1-cc69-467a-9db2-3890ab7114da resourceVersion: "23750" uid: 602770d7-4d80-4dd2-9d8d-cc31f2bf66ca spec: sourcePod: network-check-source-8894fc9bd-v5kgg targetEndpoint: ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T17:59:24Z" message: 'load-balancer-api-external: tcp connection to ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.878779ms message: 'load-balancer-api-external: tcp connection to ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:17:24Z" - latency: 6.469526ms message: 'load-balancer-api-external: resolved host name ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:17:24Z" - latency: 5.613213ms message: 'load-balancer-api-external: tcp connection to ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:16:24Z" - latency: 7.446779ms message: 'load-balancer-api-external: resolved host name ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:16:24Z" - latency: 4.983597ms message: 'load-balancer-api-external: tcp connection to ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:15:24Z" - latency: 8.618238ms message: 'load-balancer-api-external: resolved host name ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:15:24Z" - latency: 6.198115ms message: 'load-balancer-api-external: tcp connection to ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:14:24Z" - latency: 9.077617ms message: 'load-balancer-api-external: resolved host name ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:14:24Z" - latency: 5.178155ms message: 'load-balancer-api-external: tcp connection to ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:13:24Z" - latency: 7.110218ms message: 'load-balancer-api-external: resolved host name ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:13:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:53:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-107-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-107.ec2.internal uid: 6609f4d1-cc69-467a-9db2-3890ab7114da resourceVersion: "23751" uid: fbc5c993-b17c-4dda-86a2-efeea72f1015 spec: sourcePod: network-check-source-8894fc9bd-v5kgg targetEndpoint: ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T17:59:24Z" message: 'load-balancer-api-internal: tcp connection to ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.872388ms message: 'load-balancer-api-internal: tcp connection to ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:17:24Z" - latency: 6.386791ms message: 'load-balancer-api-internal: resolved host name ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:17:24Z" - latency: 5.613505ms message: 'load-balancer-api-internal: tcp connection to ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:16:24Z" - latency: 7.561366ms message: 'load-balancer-api-internal: resolved host name ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:16:24Z" - latency: 4.988662ms message: 'load-balancer-api-internal: tcp connection to ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:15:24Z" - latency: 8.567957ms message: 'load-balancer-api-internal: resolved host name ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:15:24Z" - latency: 6.589974ms message: 'load-balancer-api-internal: tcp connection to ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:14:24Z" - latency: 9.031045ms message: 'load-balancer-api-internal: resolved host name ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:14:24Z" - latency: 5.199906ms message: 'load-balancer-api-internal: tcp connection to ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:13:24Z" - latency: 7.02304ms message: 'load-balancer-api-internal: resolved host name ae3f1098939394c93a07b9a9adc2f11b-d0393709c08041ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T18:13:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:53:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-107-to-network-check-target-ip-10-0-131-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-107.ec2.internal uid: 6609f4d1-cc69-467a-9db2-3890ab7114da resourceVersion: "22317" uid: d5da2f65-2aa2-43f6-a3ba-dab11dafad3a spec: sourcePod: network-check-source-8894fc9bd-v5kgg targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-23T18:00:24Z" message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.34122ms message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:14:24Z" - latency: 860.589µs message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:13:24Z" - latency: 1.01061ms message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:12:24Z" - latency: 734.409µs message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:11:24Z" - latency: 1.321647ms message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:10:24Z" - latency: 867.849µs message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:09:24Z" - latency: 1.09509ms message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:08:24Z" - latency: 1.313865ms message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:07:24Z" - latency: 867.333µs message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:06:24Z" - latency: 1.234014ms message: 'network-check-target-ip-10-0-131-107: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:05:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:53:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-107-to-network-check-target-ip-10-0-138-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-107.ec2.internal uid: 6609f4d1-cc69-467a-9db2-3890ab7114da resourceVersion: "22318" uid: 39c111ec-aefa-4417-a273-fba17fe4bac6 spec: sourcePod: network-check-source-8894fc9bd-v5kgg targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-23T18:00:24Z" message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.43778ms message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:14:24Z" - latency: 2.37144ms message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:13:24Z" - latency: 2.109892ms message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:12:24Z" - latency: 2.253167ms message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:11:24Z" - latency: 2.070331ms message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:10:24Z" - latency: 2.221235ms message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:09:24Z" - latency: 2.292837ms message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:08:24Z" - latency: 2.282485ms message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:07:24Z" - latency: 2.99076ms message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:06:24Z" - latency: 2.239861ms message: 'network-check-target-ip-10-0-138-17: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:05:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:53:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-107-to-network-check-target-ip-10-0-139-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-107.ec2.internal uid: 6609f4d1-cc69-467a-9db2-3890ab7114da resourceVersion: "22319" uid: 30c059e8-0894-4c06-ade0-1ea6b3c61718 spec: sourcePod: network-check-source-8894fc9bd-v5kgg targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-23T18:00:24Z" message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.158765ms message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:14:24Z" - latency: 2.220259ms message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:13:24Z" - latency: 2.213648ms message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:12:24Z" - latency: 2.239259ms message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:11:24Z" - latency: 2.209524ms message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:10:24Z" - latency: 2.309748ms message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:09:24Z" - latency: 2.602034ms message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:08:24Z" - latency: 2.296693ms message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:07:24Z" - latency: 2.522956ms message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:06:24Z" - latency: 2.235275ms message: 'network-check-target-ip-10-0-139-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:05:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T17:53:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-107-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-107.ec2.internal uid: 6609f4d1-cc69-467a-9db2-3890ab7114da resourceVersion: "23749" uid: 8812ab73-889a-41e0-8512-1bab52c8469d spec: sourcePod: network-check-source-8894fc9bd-v5kgg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-23T17:59:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 767.193µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:17:24Z" - latency: 1.79073ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:17:24Z" - latency: 773.988µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:16:24Z" - latency: 1.940521ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:16:24Z" - latency: 1.080706ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:15:24Z" - latency: 2.159918ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:15:24Z" - latency: 778.708µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:14:24Z" - latency: 2.184572ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:14:24Z" - latency: 894.052µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T18:13:24Z" - latency: 1.646849ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T18:13:24Z" kind: List metadata: resourceVersion: ""