apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:10:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-33-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-33.ec2.internal uid: 0c14281d-eb9a-4bb7-a217-b844b4a3d8de resourceVersion: "47428" uid: 65f426e6-4ad9-4f9c-a376-5c5cdf2331ee spec: sourcePod: network-check-source-989f8b8dc-2plj4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-02T23:17:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.385189ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:38:25Z" - latency: 1.12221ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:37:25Z" - latency: 1.470268ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:36:25Z" - latency: 998.764µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:35:25Z" - latency: 1.26268ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:34:25Z" - latency: 980.923µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:33:25Z" - latency: 1.235264ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:32:25Z" - latency: 1.898494ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:31:25Z" - latency: 1.517689ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:30:25Z" - latency: 812.496µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:29:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:10:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-33-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-33.ec2.internal uid: 0c14281d-eb9a-4bb7-a217-b844b4a3d8de resourceVersion: "49945" uid: 28d32543-7a55-47bb-8452-cb89889c4f16 spec: sourcePod: network-check-source-989f8b8dc-2plj4 targetEndpoint: a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T23:16:25Z" message: 'load-balancer-api-external: tcp connection to a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.565158ms message: 'load-balancer-api-external: tcp connection to a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:40:25Z" - latency: 8.691589ms message: 'load-balancer-api-external: resolved host name a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:40:25Z" - latency: 5.026037ms message: 'load-balancer-api-external: tcp connection to a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:39:25Z" - latency: 8.992599ms message: 'load-balancer-api-external: resolved host name a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:39:25Z" - latency: 4.947405ms message: 'load-balancer-api-external: tcp connection to a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:38:25Z" - latency: 8.846696ms message: 'load-balancer-api-external: resolved host name a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:38:25Z" - latency: 4.964089ms message: 'load-balancer-api-external: tcp connection to a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:37:25Z" - latency: 8.105408ms message: 'load-balancer-api-external: resolved host name a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:37:25Z" - latency: 4.416417ms message: 'load-balancer-api-external: tcp connection to a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:36:25Z" - latency: 9.260892ms message: 'load-balancer-api-external: resolved host name a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:36:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:10:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-33-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-33.ec2.internal uid: 0c14281d-eb9a-4bb7-a217-b844b4a3d8de resourceVersion: "49944" uid: c546d5c6-72e7-47d8-95f1-c665c23250ed spec: sourcePod: network-check-source-989f8b8dc-2plj4 targetEndpoint: a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-02T23:16:25Z" message: 'load-balancer-api-internal: tcp connection to a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.575662ms message: 'load-balancer-api-internal: tcp connection to a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:40:25Z" - latency: 8.661209ms message: 'load-balancer-api-internal: resolved host name a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:40:25Z" - latency: 5.002298ms message: 'load-balancer-api-internal: tcp connection to a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:39:25Z" - latency: 8.949214ms message: 'load-balancer-api-internal: resolved host name a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:39:25Z" - latency: 4.995123ms message: 'load-balancer-api-internal: tcp connection to a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:38:25Z" - latency: 8.807351ms message: 'load-balancer-api-internal: resolved host name a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:38:25Z" - latency: 4.242329ms message: 'load-balancer-api-internal: tcp connection to a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:37:25Z" - latency: 8.201248ms message: 'load-balancer-api-internal: resolved host name a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:37:25Z" - latency: 4.123265ms message: 'load-balancer-api-internal: tcp connection to a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:36:25Z" - latency: 9.218736ms message: 'load-balancer-api-internal: resolved host name a81d520618eda4e0f95fe9516c9d5179-98f70e0b660711d2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-02T23:36:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:10:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-33-to-network-check-target-ip-10-0-131-33 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-33.ec2.internal uid: 0c14281d-eb9a-4bb7-a217-b844b4a3d8de resourceVersion: "47426" uid: 0c9781b9-41b1-4d08-9a3b-dea5d823787c spec: sourcePod: network-check-source-989f8b8dc-2plj4 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T23:17:25Z" message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.086259ms message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:38:25Z" - latency: 962.324µs message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:37:25Z" - latency: 861.907µs message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:36:25Z" - latency: 825.902µs message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:35:25Z" - latency: 1.361251ms message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:34:25Z" - latency: 1.210455ms message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:33:25Z" - latency: 1.426883ms message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:32:25Z" - latency: 936.483µs message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:31:25Z" - latency: 1.480071ms message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:30:25Z" - latency: 1.044958ms message: 'network-check-target-ip-10-0-131-33: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:29:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:10:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-33-to-network-check-target-ip-10-0-136-243 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-33.ec2.internal uid: 0c14281d-eb9a-4bb7-a217-b844b4a3d8de resourceVersion: "47427" uid: a4b4329d-836f-4683-a778-6872a27f54e9 spec: sourcePod: network-check-source-989f8b8dc-2plj4 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T23:17:25Z" message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.200663ms message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:38:25Z" - latency: 2.194157ms message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:37:25Z" - latency: 2.160478ms message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:36:25Z" - latency: 2.131304ms message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:35:25Z" - latency: 2.598978ms message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:34:25Z" - latency: 2.217586ms message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:33:25Z" - latency: 2.40413ms message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:32:25Z" - latency: 2.384951ms message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:31:25Z" - latency: 2.435661ms message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:30:25Z" - latency: 2.037755ms message: 'network-check-target-ip-10-0-136-243: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:29:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:10:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-33-to-network-check-target-ip-10-0-141-220 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-33.ec2.internal uid: 0c14281d-eb9a-4bb7-a217-b844b4a3d8de resourceVersion: "47425" uid: 6fbf69b8-7a8c-4600-9979-725e6fb8a6e8 spec: sourcePod: network-check-source-989f8b8dc-2plj4 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-02T23:17:25Z" message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.887693ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:38:25Z" - latency: 1.925356ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:37:25Z" - latency: 2.107542ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:36:25Z" - latency: 1.74543ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:35:25Z" - latency: 2.263058ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:34:25Z" - latency: 2.187867ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:33:25Z" - latency: 2.010788ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:32:25Z" - latency: 1.997195ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:31:25Z" - latency: 1.824045ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:30:25Z" - latency: 1.772481ms message: 'network-check-target-ip-10-0-141-220: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:29:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-02T23:10:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-33-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-33.ec2.internal uid: 0c14281d-eb9a-4bb7-a217-b844b4a3d8de resourceVersion: "49943" uid: 9694bfe8-2eb3-4be3-8d67-e569ba66c703 spec: sourcePod: network-check-source-989f8b8dc-2plj4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-02T23:16:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 779.025µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:40:25Z" - latency: 1.967025ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T23:40:25Z" - latency: 873.31µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:39:25Z" - latency: 2.717298ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T23:39:25Z" - latency: 958.003µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:38:25Z" - latency: 2.492091ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T23:38:25Z" - latency: 945.087µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:37:25Z" - latency: 1.767306ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T23:37:25Z" - latency: 1.029753ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-02T23:36:25Z" - latency: 1.972406ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-02T23:36:25Z" kind: List metadata: resourceVersion: ""