apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:54:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-121-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-121.ec2.internal uid: e7e73474-9fed-43b6-9571-62bec6e2c756 resourceVersion: "54363" uid: a2ae9151-86b4-4c79-bf4c-8e359b87009e spec: sourcePod: network-check-source-869dcfcdcd-6vjr9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-09T17:01:16Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 903.418µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:29:16Z" - latency: 1.12102ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:28:16Z" - latency: 815.959µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:27:16Z" - latency: 962.643µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:26:16Z" - latency: 971.226µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:25:16Z" - latency: 838.668µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:24:16Z" - latency: 1.321456ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:23:16Z" - latency: 1.31894ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:22:16Z" - latency: 1.233246ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:21:16Z" - latency: 970.412µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:20:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:54:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-121-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-121.ec2.internal uid: e7e73474-9fed-43b6-9571-62bec6e2c756 resourceVersion: "55465" uid: 0873e5a8-1cff-48e3-ba30-6bff3a6eed26 spec: sourcePod: network-check-source-869dcfcdcd-6vjr9 targetEndpoint: a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T17:00:16Z" message: 'load-balancer-api-external: tcp connection to a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.007279ms message: 'load-balancer-api-external: tcp connection to a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:30:16Z" - latency: 7.995399ms message: 'load-balancer-api-external: resolved host name a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:30:16Z" - latency: 3.534661ms message: 'load-balancer-api-external: tcp connection to a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:29:16Z" - latency: 8.168529ms message: 'load-balancer-api-external: resolved host name a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:29:16Z" - latency: 3.478998ms message: 'load-balancer-api-external: tcp connection to a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:28:16Z" - latency: 7.523653ms message: 'load-balancer-api-external: resolved host name a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:28:16Z" - latency: 3.154773ms message: 'load-balancer-api-external: tcp connection to a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:27:16Z" - latency: 7.220776ms message: 'load-balancer-api-external: resolved host name a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:27:16Z" - latency: 3.30174ms message: 'load-balancer-api-external: tcp connection to a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:26:16Z" - latency: 13.22086ms message: 'load-balancer-api-external: resolved host name a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:26:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:54:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-121-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-121.ec2.internal uid: e7e73474-9fed-43b6-9571-62bec6e2c756 resourceVersion: "55466" uid: 18d669d9-cbd5-4322-aee9-cf1a3e02c5ab spec: sourcePod: network-check-source-869dcfcdcd-6vjr9 targetEndpoint: a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-09T17:00:16Z" message: 'load-balancer-api-internal: tcp connection to a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.024863ms message: 'load-balancer-api-internal: tcp connection to a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:30:16Z" - latency: 7.787154ms message: 'load-balancer-api-internal: resolved host name a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:30:16Z" - latency: 4.517841ms message: 'load-balancer-api-internal: tcp connection to a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:29:16Z" - latency: 8.234496ms message: 'load-balancer-api-internal: resolved host name a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:29:16Z" - latency: 4.422645ms message: 'load-balancer-api-internal: tcp connection to a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:28:16Z" - latency: 7.516744ms message: 'load-balancer-api-internal: resolved host name a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:28:16Z" - latency: 3.238003ms message: 'load-balancer-api-internal: tcp connection to a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:27:16Z" - latency: 7.166778ms message: 'load-balancer-api-internal: resolved host name a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:27:16Z" - latency: 3.329744ms message: 'load-balancer-api-internal: tcp connection to a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:26:16Z" - latency: 13.210213ms message: 'load-balancer-api-internal: resolved host name a075cf48f51af43e294e75d157e9f97d-9f49df0be533b2b4.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-09T17:26:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:54:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-121-to-network-check-target-ip-10-0-135-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-121.ec2.internal uid: e7e73474-9fed-43b6-9571-62bec6e2c756 resourceVersion: "54360" uid: 7a894d0a-d30a-430d-b4cc-e6267a321b7b spec: sourcePod: network-check-source-869dcfcdcd-6vjr9 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T17:01:16Z" message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.068749ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:29:16Z" - latency: 915.676µs message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:28:16Z" - latency: 891.973µs message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:27:16Z" - latency: 1.477938ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:26:16Z" - latency: 946.021µs message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:25:16Z" - latency: 1.388564ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:24:16Z" - latency: 946.514µs message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:23:16Z" - latency: 1.012789ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:22:16Z" - latency: 1.021736ms message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:21:16Z" - latency: 962.313µs message: 'network-check-target-ip-10-0-135-121: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:20:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:54:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-121-to-network-check-target-ip-10-0-139-29 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-121.ec2.internal uid: e7e73474-9fed-43b6-9571-62bec6e2c756 resourceVersion: "54362" uid: 82240676-f08e-4718-a007-bb16661f7b5d spec: sourcePod: network-check-source-869dcfcdcd-6vjr9 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-09T17:01:16Z" message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.574827ms message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:29:16Z" - latency: 2.201069ms message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:28:16Z" - latency: 1.89158ms message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:27:16Z" - latency: 2.528232ms message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:26:16Z" - latency: 2.499952ms message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:25:16Z" - latency: 2.535525ms message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:24:16Z" - latency: 2.370163ms message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:23:16Z" - latency: 2.311099ms message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:22:16Z" - latency: 2.245719ms message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:21:16Z" - latency: 2.214057ms message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:20:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:54:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-121-to-network-check-target-ip-10-0-140-229 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-121.ec2.internal uid: e7e73474-9fed-43b6-9571-62bec6e2c756 resourceVersion: "54361" uid: c80a4fd9-261a-414e-8e40-8fab3bb70b24 spec: sourcePod: network-check-source-869dcfcdcd-6vjr9 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-09T17:01:16Z" message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.382271ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:29:16Z" - latency: 2.515437ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:28:16Z" - latency: 2.236726ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:27:16Z" - latency: 2.444138ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:26:16Z" - latency: 2.958954ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:25:16Z" - latency: 2.499286ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:24:16Z" - latency: 2.639576ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:23:16Z" - latency: 2.58058ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:22:16Z" - latency: 2.340877ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:21:16Z" - latency: 2.273579ms message: 'network-check-target-ip-10-0-140-229: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:20:16Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-09T16:54:15Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-121-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-121.ec2.internal uid: e7e73474-9fed-43b6-9571-62bec6e2c756 resourceVersion: "55464" uid: f1990732-bd1d-4aa0-aefb-db94ab1cae08 spec: sourcePod: network-check-source-869dcfcdcd-6vjr9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-09T17:00:16Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.298156ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:30:16Z" - latency: 2.4533ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:30:16Z" - latency: 1.000873ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:29:16Z" - latency: 1.755187ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:29:16Z" - latency: 1.247076ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:28:16Z" - latency: 1.623768ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:28:16Z" - latency: 844.078µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:27:16Z" - latency: 2.125615ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:27:16Z" - latency: 868.002µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-09T17:26:16Z" - latency: 1.715724ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-09T17:26:16Z" kind: List metadata: resourceVersion: ""