apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T20:19:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-198-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-198.ec2.internal uid: e1564e63-04c7-4688-b8b9-7b6e303bfa6e resourceVersion: "65065" uid: 765f3217-57c0-4695-a315-0c6d21fa834f spec: sourcePod: network-check-source-7d88cb55d8-q7w4l targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T20:26:35Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.808235ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:01:35Z" - latency: 1.023457ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:00:35Z" - latency: 1.209901ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:59:35Z" - latency: 1.191384ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:58:35Z" - latency: 1.53916ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:57:35Z" - latency: 1.007628ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:56:35Z" - latency: 1.311656ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:55:35Z" - latency: 1.444754ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:54:35Z" - latency: 814.62µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:53:35Z" - latency: 1.22587ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:52:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T20:19:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-198-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-198.ec2.internal uid: e1564e63-04c7-4688-b8b9-7b6e303bfa6e resourceVersion: "71446" uid: 55b4d588-0711-46c3-a861-cb12b1b545b7 spec: sourcePod: network-check-source-7d88cb55d8-q7w4l targetEndpoint: aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T20:25:35Z" message: 'load-balancer-api-external: tcp connection to aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.554526ms message: 'load-balancer-api-external: tcp connection to aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:07:35Z" - latency: 10.343187ms message: 'load-balancer-api-external: resolved host name aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:07:35Z" - latency: 5.996492ms message: 'load-balancer-api-external: tcp connection to aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:06:35Z" - latency: 7.20799ms message: 'load-balancer-api-external: resolved host name aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:06:35Z" - latency: 3.69738ms message: 'load-balancer-api-external: tcp connection to aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:05:35Z" - latency: 6.868562ms message: 'load-balancer-api-external: resolved host name aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:05:35Z" - latency: 3.922561ms message: 'load-balancer-api-external: tcp connection to aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:04:35Z" - latency: 9.487604ms message: 'load-balancer-api-external: resolved host name aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:04:35Z" - latency: 3.384845ms message: 'load-balancer-api-external: tcp connection to aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:03:35Z" - latency: 6.761032ms message: 'load-balancer-api-external: resolved host name aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:03:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T20:19:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-198-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-198.ec2.internal uid: e1564e63-04c7-4688-b8b9-7b6e303bfa6e resourceVersion: "71447" uid: 69d4892a-38bc-45a3-87be-47f0f6119c5b spec: sourcePod: network-check-source-7d88cb55d8-q7w4l targetEndpoint: aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T20:25:35Z" message: 'load-balancer-api-internal: tcp connection to aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.588921ms message: 'load-balancer-api-internal: tcp connection to aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:07:35Z" - latency: 10.378537ms message: 'load-balancer-api-internal: resolved host name aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:07:35Z" - latency: 5.018399ms message: 'load-balancer-api-internal: tcp connection to aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:06:35Z" - latency: 7.304605ms message: 'load-balancer-api-internal: resolved host name aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:06:35Z" - latency: 3.644383ms message: 'load-balancer-api-internal: tcp connection to aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:05:35Z" - latency: 6.910394ms message: 'load-balancer-api-internal: resolved host name aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:05:35Z" - latency: 4.962265ms message: 'load-balancer-api-internal: tcp connection to aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:04:35Z" - latency: 9.378707ms message: 'load-balancer-api-internal: resolved host name aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:04:35Z" - latency: 3.395775ms message: 'load-balancer-api-internal: tcp connection to aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:03:35Z" - latency: 6.723655ms message: 'load-balancer-api-internal: resolved host name aa2d03f289b9545f3b5e9d0633179b08-cbbbd8dfe25b37cd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T21:03:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T20:19:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-198-to-network-check-target-ip-10-0-129-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-198.ec2.internal uid: e1564e63-04c7-4688-b8b9-7b6e303bfa6e resourceVersion: "65063" uid: ac7ba1ae-864f-42c6-981c-b38575f4971f spec: sourcePod: network-check-source-7d88cb55d8-q7w4l targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T20:26:35Z" message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.951806ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:01:35Z" - latency: 2.102817ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:00:35Z" - latency: 2.020715ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:59:35Z" - latency: 2.107092ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:58:35Z" - latency: 2.431043ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:57:35Z" - latency: 2.078575ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:56:35Z" - latency: 2.285062ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:55:35Z" - latency: 2.352934ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:54:35Z" - latency: 1.865682ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:53:35Z" - latency: 2.3743ms message: 'network-check-target-ip-10-0-129-245: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:52:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T20:19:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-198-to-network-check-target-ip-10-0-132-198 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-198.ec2.internal uid: e1564e63-04c7-4688-b8b9-7b6e303bfa6e resourceVersion: "65061" uid: 6ea52630-cdee-41e9-8d73-aec13cd4d0ef spec: sourcePod: network-check-source-7d88cb55d8-q7w4l targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T20:26:35Z" message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 859.986µs message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:01:35Z" - latency: 982.027µs message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:00:35Z" - latency: 987.451µs message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:59:35Z" - latency: 892.426µs message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:58:35Z" - latency: 1.370762ms message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:57:35Z" - latency: 1.335912ms message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:56:35Z" - latency: 1.570744ms message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:55:35Z" - latency: 1.121243ms message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:54:35Z" - latency: 1.289305ms message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:53:35Z" - latency: 985.139µs message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:52:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T20:19:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-198-to-network-check-target-ip-10-0-136-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-198.ec2.internal uid: e1564e63-04c7-4688-b8b9-7b6e303bfa6e resourceVersion: "65062" uid: 62b1560f-f1af-4028-83b7-6d05f8e62b50 spec: sourcePod: network-check-source-7d88cb55d8-q7w4l targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T20:26:35Z" message: 'network-check-target-ip-10-0-136-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.072626ms message: 'network-check-target-ip-10-0-136-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:01:35Z" - latency: 2.206142ms message: 'network-check-target-ip-10-0-136-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:00:35Z" - latency: 2.246685ms message: 'network-check-target-ip-10-0-136-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:59:35Z" - latency: 2.038575ms message: 'network-check-target-ip-10-0-136-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:58:35Z" - latency: 2.056741ms message: 'network-check-target-ip-10-0-136-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:57:35Z" - latency: 1.776823ms message: 'network-check-target-ip-10-0-136-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:56:35Z" - latency: 2.083914ms message: 'network-check-target-ip-10-0-136-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:55:35Z" - latency: 1.932909ms message: 'network-check-target-ip-10-0-136-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:54:35Z" - latency: 2.01349ms message: 'network-check-target-ip-10-0-136-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:53:35Z" - latency: 1.995804ms message: 'network-check-target-ip-10-0-136-110: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T20:52:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T20:19:33Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-198-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-198.ec2.internal uid: e1564e63-04c7-4688-b8b9-7b6e303bfa6e resourceVersion: "71445" uid: a40c0fff-650a-4996-b3a1-91b4b7745c62 spec: sourcePod: network-check-source-7d88cb55d8-q7w4l targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T20:25:35Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 885.813µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:07:35Z" - latency: 1.795818ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T21:07:35Z" - latency: 1.097709ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:06:35Z" - latency: 1.784886ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T21:06:35Z" - latency: 839.913µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:05:35Z" - latency: 1.587755ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T21:05:35Z" - latency: 977.89µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:04:35Z" - latency: 1.684271ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T21:04:35Z" - latency: 959.581µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T21:03:35Z" - latency: 1.924207ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T21:03:35Z" kind: List metadata: resourceVersion: ""