apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T23:54:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-103-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-103.ec2.internal uid: fef723c7-4e34-4ca5-914e-a17321f13376 resourceVersion: "43969" uid: f1a5a4df-a6d1-4523-ab99-1835bf791083 spec: sourcePod: network-check-source-8894fc9bd-hz2rt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-17T00:01:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.11314ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:22:33Z" - latency: 898.357µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:21:33Z" - latency: 911.557µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:20:33Z" - latency: 840.377µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:19:33Z" - latency: 1.008193ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:18:33Z" - latency: 1.247394ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:17:33Z" - latency: 1.233353ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:16:33Z" - latency: 1.089106ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:15:33Z" - latency: 1.226715ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:14:33Z" - latency: 1.001619ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:13:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T23:54:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-103-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-103.ec2.internal uid: fef723c7-4e34-4ca5-914e-a17321f13376 resourceVersion: "46223" uid: 0958aaf9-b0d1-4317-ade3-6c91d45fdbc4 spec: sourcePod: network-check-source-8894fc9bd-hz2rt targetEndpoint: a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T00:00:33Z" message: 'load-balancer-api-external: tcp connection to a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.790265ms message: 'load-balancer-api-external: tcp connection to a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:24:33Z" - latency: 7.242075ms message: 'load-balancer-api-external: resolved host name a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T00:24:33Z" - latency: 5.661815ms message: 'load-balancer-api-external: tcp connection to a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:23:33Z" - latency: 8.390882ms message: 'load-balancer-api-external: resolved host name a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T00:23:33Z" - latency: 5.066704ms message: 'load-balancer-api-external: tcp connection to a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:22:33Z" - latency: 6.558626ms message: 'load-balancer-api-external: resolved host name a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T00:22:33Z" - latency: 4.964879ms message: 'load-balancer-api-external: tcp connection to a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:21:33Z" - latency: 6.292872ms message: 'load-balancer-api-external: resolved host name a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T00:21:33Z" - latency: 5.825707ms message: 'load-balancer-api-external: tcp connection to a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:20:33Z" - latency: 7.367669ms message: 'load-balancer-api-external: resolved host name a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T00:20:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T23:54:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-103-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-103.ec2.internal uid: fef723c7-4e34-4ca5-914e-a17321f13376 resourceVersion: "46222" uid: c811d78e-7071-4f9c-ae93-c68afdd984e8 spec: sourcePod: network-check-source-8894fc9bd-hz2rt targetEndpoint: a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-17T00:00:33Z" message: 'load-balancer-api-internal: tcp connection to a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.761798ms message: 'load-balancer-api-internal: tcp connection to a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:24:33Z" - latency: 7.159918ms message: 'load-balancer-api-internal: resolved host name a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T00:24:33Z" - latency: 4.154289ms message: 'load-balancer-api-internal: tcp connection to a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:23:33Z" - latency: 8.368215ms message: 'load-balancer-api-internal: resolved host name a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T00:23:33Z" - latency: 5.082334ms message: 'load-balancer-api-internal: tcp connection to a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:22:33Z" - latency: 6.510594ms message: 'load-balancer-api-internal: resolved host name a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T00:22:33Z" - latency: 5.0048ms message: 'load-balancer-api-internal: tcp connection to a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:21:33Z" - latency: 6.324696ms message: 'load-balancer-api-internal: resolved host name a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T00:21:33Z" - latency: 5.662922ms message: 'load-balancer-api-internal: tcp connection to a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:20:33Z" - latency: 7.313261ms message: 'load-balancer-api-internal: resolved host name a9a027ecb637049c58ae5502b4d4b211-122023c3d5f8c0df.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-17T00:20:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T23:54:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-103-to-network-check-target-ip-10-0-128-98 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-103.ec2.internal uid: fef723c7-4e34-4ca5-914e-a17321f13376 resourceVersion: "43967" uid: 3130ad60-91f6-44a3-b57a-afbc0057d0f8 spec: sourcePod: network-check-source-8894fc9bd-hz2rt targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T00:01:33Z" message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.936894ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:22:33Z" - latency: 1.861592ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:21:33Z" - latency: 1.742723ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:20:33Z" - latency: 1.735378ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:19:33Z" - latency: 1.780444ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:18:33Z" - latency: 1.776431ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:17:33Z" - latency: 1.633457ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:16:33Z" - latency: 1.938566ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:15:33Z" - latency: 1.765364ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:14:33Z" - latency: 1.602828ms message: 'network-check-target-ip-10-0-128-98: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:13:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T23:54:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-103-to-network-check-target-ip-10-0-133-231 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-103.ec2.internal uid: fef723c7-4e34-4ca5-914e-a17321f13376 resourceVersion: "43968" uid: 1b9eebf1-ba85-454e-a030-659bdf99cffe spec: sourcePod: network-check-source-8894fc9bd-hz2rt targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-17T00:01:33Z" message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.277638ms message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:22:33Z" - latency: 1.94632ms message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:21:33Z" - latency: 1.61461ms message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:20:33Z" - latency: 1.976262ms message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:19:33Z" - latency: 1.971039ms message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:18:33Z" - latency: 2.114456ms message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:17:33Z" - latency: 2.123537ms message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:16:33Z" - latency: 2.39143ms message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:15:33Z" - latency: 2.132275ms message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:14:33Z" - latency: 1.838053ms message: 'network-check-target-ip-10-0-133-231: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:13:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T23:54:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-103-to-network-check-target-ip-10-0-134-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-103.ec2.internal uid: fef723c7-4e34-4ca5-914e-a17321f13376 resourceVersion: "43966" uid: fc76dba7-a806-44e1-bbc0-f4896097a653 spec: sourcePod: network-check-source-8894fc9bd-hz2rt targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-17T00:01:33Z" message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.008847ms message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:22:33Z" - latency: 919.985µs message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:21:33Z" - latency: 880.702µs message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:20:33Z" - latency: 1.085578ms message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:19:33Z" - latency: 763.19µs message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:18:33Z" - latency: 1.489885ms message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:17:33Z" - latency: 1.344448ms message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:16:33Z" - latency: 969.304µs message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:15:33Z" - latency: 873.021µs message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:14:33Z" - latency: 992.065µs message: 'network-check-target-ip-10-0-134-103: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:13:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T23:54:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-103-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-103.ec2.internal uid: fef723c7-4e34-4ca5-914e-a17321f13376 resourceVersion: "46219" uid: 6814ac17-72c4-4ee1-adc7-b65615990474 spec: sourcePod: network-check-source-8894fc9bd-hz2rt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-17T00:00:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 888.282µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:24:33Z" - latency: 2.376175ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T00:24:33Z" - latency: 801.386µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:23:33Z" - latency: 2.278337ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T00:23:33Z" - latency: 887.87µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:22:33Z" - latency: 1.556522ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T00:22:33Z" - latency: 799.921µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:21:33Z" - latency: 1.598965ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T00:21:33Z" - latency: 871.908µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-17T00:20:33Z" - latency: 1.629012ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-17T00:20:33Z" kind: List metadata: resourceVersion: ""