apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T20:53:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-50-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-50.ec2.internal uid: be20de1e-7c87-4fb1-a5c6-267ccba4443e resourceVersion: "44127" uid: cc35a551-c57f-4c92-822c-6800bea45124 spec: sourcePod: network-check-source-7f44b6dd87-q2qmd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-20T21:00:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.138035ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:21:18Z" - latency: 955.593µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:20:18Z" - latency: 1.110753ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:19:18Z" - latency: 920.996µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:18:18Z" - latency: 1.073279ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:17:18Z" - latency: 849.273µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:16:18Z" - latency: 1.10354ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:15:18Z" - latency: 971.842µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:14:18Z" - latency: 849.836µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:13:18Z" - latency: 1.042557ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:12:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T20:53:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-50-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-50.ec2.internal uid: be20de1e-7c87-4fb1-a5c6-267ccba4443e resourceVersion: "46368" uid: 3f596f24-f895-45a1-9675-26931a760fc1 spec: sourcePod: network-check-source-7f44b6dd87-q2qmd targetEndpoint: a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T20:59:18Z" message: 'load-balancer-api-external: tcp connection to a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.748961ms message: 'load-balancer-api-external: tcp connection to a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:23:18Z" - latency: 6.325716ms message: 'load-balancer-api-external: resolved host name a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T21:23:18Z" - latency: 3.758899ms message: 'load-balancer-api-external: tcp connection to a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:22:18Z" - latency: 6.371068ms message: 'load-balancer-api-external: resolved host name a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T21:22:18Z" - latency: 4.135429ms message: 'load-balancer-api-external: tcp connection to a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:21:18Z" - latency: 6.78314ms message: 'load-balancer-api-external: resolved host name a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T21:21:18Z" - latency: 3.667172ms message: 'load-balancer-api-external: tcp connection to a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:20:18Z" - latency: 6.055996ms message: 'load-balancer-api-external: resolved host name a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T21:20:18Z" - latency: 4.172625ms message: 'load-balancer-api-external: tcp connection to a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:19:18Z" - latency: 6.408604ms message: 'load-balancer-api-external: resolved host name a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T21:19:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T20:53:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-50-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-50.ec2.internal uid: be20de1e-7c87-4fb1-a5c6-267ccba4443e resourceVersion: "46367" uid: 37536500-95fd-48ea-ac79-051b12399b1d spec: sourcePod: network-check-source-7f44b6dd87-q2qmd targetEndpoint: a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T20:59:18Z" message: 'load-balancer-api-internal: tcp connection to a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.779579ms message: 'load-balancer-api-internal: tcp connection to a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:23:18Z" - latency: 6.255572ms message: 'load-balancer-api-internal: resolved host name a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T21:23:18Z" - latency: 3.747911ms message: 'load-balancer-api-internal: tcp connection to a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:22:18Z" - latency: 6.516178ms message: 'load-balancer-api-internal: resolved host name a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T21:22:18Z" - latency: 4.085601ms message: 'load-balancer-api-internal: tcp connection to a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:21:18Z" - latency: 6.806663ms message: 'load-balancer-api-internal: resolved host name a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T21:21:18Z" - latency: 4.724538ms message: 'load-balancer-api-internal: tcp connection to a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:20:18Z" - latency: 6.008647ms message: 'load-balancer-api-internal: resolved host name a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T21:20:18Z" - latency: 3.912378ms message: 'load-balancer-api-internal: tcp connection to a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:19:18Z" - latency: 6.345976ms message: 'load-balancer-api-internal: resolved host name a9a9bdfa5024540089766fa3995cc34c-31a20e78a75aa601.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T21:19:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T20:53:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-50-to-network-check-target-ip-10-0-130-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-50.ec2.internal uid: be20de1e-7c87-4fb1-a5c6-267ccba4443e resourceVersion: "44126" uid: 967024fe-17b9-4a9e-bc39-b81a4867fbc6 spec: sourcePod: network-check-source-7f44b6dd87-q2qmd targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-20T21:00:18Z" message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.257249ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:21:18Z" - latency: 2.229627ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:20:18Z" - latency: 2.226359ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:19:18Z" - latency: 2.401742ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:18:18Z" - latency: 2.358589ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:17:18Z" - latency: 2.044625ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:16:18Z" - latency: 2.433844ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:15:18Z" - latency: 2.315498ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:14:18Z" - latency: 2.046041ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:13:18Z" - latency: 2.180343ms message: 'network-check-target-ip-10-0-130-155: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:12:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T20:53:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-50-to-network-check-target-ip-10-0-138-50 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-50.ec2.internal uid: be20de1e-7c87-4fb1-a5c6-267ccba4443e resourceVersion: "44124" uid: b579ccd4-a607-4e49-9a8d-b5207f858d3d spec: sourcePod: network-check-source-7f44b6dd87-q2qmd targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T21:00:18Z" message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 972.88µs message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:21:18Z" - latency: 919.709µs message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:20:18Z" - latency: 880.422µs message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:19:18Z" - latency: 827.4µs message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:18:18Z" - latency: 787.648µs message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:17:18Z" - latency: 786.656µs message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:16:18Z" - latency: 994.858µs message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:15:18Z" - latency: 1.224723ms message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:14:18Z" - latency: 850.373µs message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:13:18Z" - latency: 872.909µs message: 'network-check-target-ip-10-0-138-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:12:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T20:53:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-50-to-network-check-target-ip-10-0-142-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-50.ec2.internal uid: be20de1e-7c87-4fb1-a5c6-267ccba4443e resourceVersion: "44125" uid: 50317db3-5cb1-4296-bd55-2671cad044a2 spec: sourcePod: network-check-source-7f44b6dd87-q2qmd targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T21:00:18Z" message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.144234ms message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:21:18Z" - latency: 1.942162ms message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:20:18Z" - latency: 2.340944ms message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:19:18Z" - latency: 2.164977ms message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:18:18Z" - latency: 2.285349ms message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:17:18Z" - latency: 2.081979ms message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:16:18Z" - latency: 2.305999ms message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:15:18Z" - latency: 2.156455ms message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:14:18Z" - latency: 2.142567ms message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:13:18Z" - latency: 2.044842ms message: 'network-check-target-ip-10-0-142-248: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:12:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T20:53:16Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-50-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-50.ec2.internal uid: be20de1e-7c87-4fb1-a5c6-267ccba4443e resourceVersion: "46366" uid: 005f4af5-5b46-4177-853e-c11ce70b5745 spec: sourcePod: network-check-source-7f44b6dd87-q2qmd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-20T20:59:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 971.652µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:23:18Z" - latency: 1.782491ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T21:23:18Z" - latency: 854.653µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:22:18Z" - latency: 1.5947ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T21:22:18Z" - latency: 890.272µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:21:18Z" - latency: 1.731414ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T21:21:18Z" - latency: 822.818µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:20:18Z" - latency: 1.616713ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T21:20:18Z" - latency: 1.026318ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T21:19:18Z" - latency: 1.681317ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T21:19:18Z" kind: List metadata: resourceVersion: ""