apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T06:59:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-129-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-129.ec2.internal uid: 47d35495-327a-412a-80b2-e1f02b60860e resourceVersion: "94361" uid: 27bfec94-498c-4b89-9428-ba0d50b3342b spec: sourcePod: network-check-source-989f8b8dc-fjzgc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T07:06:03Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.123183ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:30:03Z" - latency: 951.73µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:29:03Z" - latency: 1.28072ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:28:03Z" - latency: 1.490081ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:27:03Z" - latency: 986.885µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:26:03Z" - latency: 938.132µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:25:03Z" - latency: 1.288859ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:24:03Z" - latency: 1.3825ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:23:03Z" - latency: 1.139615ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:22:03Z" - latency: 1.420858ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:21:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T06:59:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-129-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-129.ec2.internal uid: 47d35495-327a-412a-80b2-e1f02b60860e resourceVersion: "98384" uid: 5d0f7b46-81ed-46c1-a618-9316a160dad2 spec: sourcePod: network-check-source-989f8b8dc-fjzgc targetEndpoint: ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T07:05:03Z" message: 'load-balancer-api-external: tcp connection to ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.665981ms message: 'load-balancer-api-external: tcp connection to ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:35:03Z" - latency: 7.881168ms message: 'load-balancer-api-external: resolved host name ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T08:35:03Z" - latency: 5.573538ms message: 'load-balancer-api-external: tcp connection to ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:34:03Z" - latency: 7.106022ms message: 'load-balancer-api-external: resolved host name ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T08:34:03Z" - latency: 5.665164ms message: 'load-balancer-api-external: tcp connection to ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:33:03Z" - latency: 8.71529ms message: 'load-balancer-api-external: resolved host name ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T08:33:03Z" - latency: 4.77147ms message: 'load-balancer-api-external: tcp connection to ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:32:03Z" - latency: 8.583156ms message: 'load-balancer-api-external: resolved host name ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T08:32:03Z" - latency: 5.344163ms message: 'load-balancer-api-external: tcp connection to ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:31:03Z" - latency: 13.892041ms message: 'load-balancer-api-external: resolved host name ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T08:31:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T06:59:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-129-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-129.ec2.internal uid: 47d35495-327a-412a-80b2-e1f02b60860e resourceVersion: "98385" uid: 21e150fc-384f-49e0-b260-21797059a168 spec: sourcePod: network-check-source-989f8b8dc-fjzgc targetEndpoint: ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T07:05:03Z" message: 'load-balancer-api-internal: tcp connection to ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.672378ms message: 'load-balancer-api-internal: tcp connection to ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:35:03Z" - latency: 7.783166ms message: 'load-balancer-api-internal: resolved host name ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T08:35:03Z" - latency: 5.163777ms message: 'load-balancer-api-internal: tcp connection to ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:34:03Z" - latency: 7.174659ms message: 'load-balancer-api-internal: resolved host name ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T08:34:03Z" - latency: 5.792329ms message: 'load-balancer-api-internal: tcp connection to ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:33:03Z" - latency: 8.725845ms message: 'load-balancer-api-internal: resolved host name ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T08:33:03Z" - latency: 4.801669ms message: 'load-balancer-api-internal: tcp connection to ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:32:03Z" - latency: 8.531225ms message: 'load-balancer-api-internal: resolved host name ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T08:32:03Z" - latency: 5.332352ms message: 'load-balancer-api-internal: tcp connection to ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:31:03Z" - latency: 13.955082ms message: 'load-balancer-api-internal: resolved host name ae8175ce0072f4e5bae938eb7f7adde2-79293de22557334a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T08:31:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T06:59:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-129-to-network-check-target-ip-10-0-129-54 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-129.ec2.internal uid: 47d35495-327a-412a-80b2-e1f02b60860e resourceVersion: "94360" uid: 5044e57a-c86d-4d95-884f-dfd3ea8a95d5 spec: sourcePod: network-check-source-989f8b8dc-fjzgc targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T07:06:03Z" message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.424903ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:30:03Z" - latency: 2.252815ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:29:03Z" - latency: 2.676496ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:28:03Z" - latency: 2.469977ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:27:03Z" - latency: 2.428966ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:26:03Z" - latency: 2.482119ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:25:03Z" - latency: 2.701532ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:24:03Z" - latency: 2.609912ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:23:03Z" - latency: 2.52795ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:22:03Z" - latency: 2.615148ms message: 'network-check-target-ip-10-0-129-54: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:21:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T06:59:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-129-to-network-check-target-ip-10-0-136-129 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-129.ec2.internal uid: 47d35495-327a-412a-80b2-e1f02b60860e resourceVersion: "94358" uid: f4339bca-7f27-4a66-8fb8-982a28fe4894 spec: sourcePod: network-check-source-989f8b8dc-fjzgc targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T07:06:03Z" message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.269056ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:30:03Z" - latency: 1.442333ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:29:03Z" - latency: 980.158µs message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:28:03Z" - latency: 1.733512ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:27:03Z" - latency: 1.179529ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:26:03Z" - latency: 1.187376ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:25:03Z" - latency: 1.936716ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:24:03Z" - latency: 1.024121ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:23:03Z" - latency: 1.604512ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:22:03Z" - latency: 1.869362ms message: 'network-check-target-ip-10-0-136-129: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:21:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T06:59:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-129-to-network-check-target-ip-10-0-140-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-129.ec2.internal uid: 47d35495-327a-412a-80b2-e1f02b60860e resourceVersion: "94359" uid: 696d70d4-68f0-4289-bd66-3a7a0ab73393 spec: sourcePod: network-check-source-989f8b8dc-fjzgc targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T07:06:03Z" message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.294313ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:30:03Z" - latency: 2.288097ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:29:03Z" - latency: 2.316771ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:28:03Z" - latency: 2.150628ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:27:03Z" - latency: 2.779424ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:26:03Z" - latency: 2.200909ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:25:03Z" - latency: 2.446815ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:24:03Z" - latency: 2.213363ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:23:03Z" - latency: 2.535138ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:22:03Z" - latency: 2.4856ms message: 'network-check-target-ip-10-0-140-110: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:21:03Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T06:59:02Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-136-129-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-136-129.ec2.internal uid: 47d35495-327a-412a-80b2-e1f02b60860e resourceVersion: "98383" uid: 6b5e5539-12b4-4fcb-b1ce-a7fc75f2b37f spec: sourcePod: network-check-source-989f8b8dc-fjzgc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T07:05:03Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.192044ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:35:03Z" - latency: 1.938511ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T08:35:03Z" - latency: 942.894µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:34:03Z" - latency: 1.746363ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T08:34:03Z" - latency: 1.426386ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:33:03Z" - latency: 1.844315ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T08:33:03Z" - latency: 1.566786ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:32:03Z" - latency: 2.185198ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T08:32:03Z" - latency: 879.87µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T08:31:03Z" - latency: 1.853417ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T08:31:03Z" kind: List metadata: resourceVersion: ""