apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T20:09:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-227-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-227.ec2.internal uid: 73972175-4d73-4e55-845d-e96439372571 resourceVersion: "32121" uid: 72057bb4-0cbb-4728-8ffe-847a43d46a1f spec: sourcePod: network-check-source-8894fc9bd-6zzrt targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-20T20:16:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 822.384µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:51:36Z" - latency: 825.998µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:50:36Z" - latency: 811.998µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:49:36Z" - latency: 931.825µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:48:36Z" - latency: 1.086794ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:47:36Z" - latency: 812.893µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:46:36Z" - latency: 751.997µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:45:36Z" - latency: 916.474µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:44:36Z" - latency: 853.545µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:43:36Z" - latency: 985.456µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:42:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T20:09:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-227-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-227.ec2.internal uid: 73972175-4d73-4e55-845d-e96439372571 resourceVersion: "32123" uid: 70437038-1499-4ce6-8a76-93a31d5e9d65 spec: sourcePod: network-check-source-8894fc9bd-6zzrt targetEndpoint: ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T20:15:36Z" message: 'load-balancer-api-external: tcp connection to ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.557551ms message: 'load-balancer-api-external: tcp connection to ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:51:36Z" - latency: 6.883377ms message: 'load-balancer-api-external: resolved host name ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:51:36Z" - latency: 4.114995ms message: 'load-balancer-api-external: tcp connection to ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:50:36Z" - latency: 6.389985ms message: 'load-balancer-api-external: resolved host name ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:50:36Z" - latency: 5.246161ms message: 'load-balancer-api-external: tcp connection to ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:49:36Z" - latency: 5.900594ms message: 'load-balancer-api-external: resolved host name ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:49:36Z" - latency: 5.762539ms message: 'load-balancer-api-external: tcp connection to ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:48:36Z" - latency: 6.666342ms message: 'load-balancer-api-external: resolved host name ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:48:36Z" - latency: 5.642836ms message: 'load-balancer-api-external: tcp connection to ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:47:36Z" - latency: 6.236085ms message: 'load-balancer-api-external: resolved host name ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:47:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T20:09:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-227-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-227.ec2.internal uid: 73972175-4d73-4e55-845d-e96439372571 resourceVersion: "32122" uid: e7bc2be4-0dc4-4102-9d31-699698fcdab8 spec: sourcePod: network-check-source-8894fc9bd-6zzrt targetEndpoint: ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T20:15:36Z" message: 'load-balancer-api-internal: tcp connection to ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.295901ms message: 'load-balancer-api-internal: tcp connection to ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:51:36Z" - latency: 6.905122ms message: 'load-balancer-api-internal: resolved host name ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:51:36Z" - latency: 4.122396ms message: 'load-balancer-api-internal: tcp connection to ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:50:36Z" - latency: 6.376864ms message: 'load-balancer-api-internal: resolved host name ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:50:36Z" - latency: 5.211067ms message: 'load-balancer-api-internal: tcp connection to ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:49:36Z" - latency: 5.955706ms message: 'load-balancer-api-internal: resolved host name ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:49:36Z" - latency: 5.793933ms message: 'load-balancer-api-internal: tcp connection to ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:48:36Z" - latency: 6.654989ms message: 'load-balancer-api-internal: resolved host name ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:48:36Z" - latency: 5.651759ms message: 'load-balancer-api-internal: tcp connection to ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:47:36Z" - latency: 6.165925ms message: 'load-balancer-api-internal: resolved host name ab795cb9a00014931be83e23abc420a3-2cdb4e6c41b9d551.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T20:47:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T20:09:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-227-to-network-check-target-ip-10-0-130-227 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-227.ec2.internal uid: 73972175-4d73-4e55-845d-e96439372571 resourceVersion: "32117" uid: 98701990-c112-4b94-b73c-b8edd6b0a3c4 spec: sourcePod: network-check-source-8894fc9bd-6zzrt targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-20T20:16:36Z" message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 756.299µs message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:51:36Z" - latency: 864.68µs message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:50:36Z" - latency: 1.20211ms message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:49:36Z" - latency: 875.311µs message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:48:36Z" - latency: 1.436492ms message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:47:36Z" - latency: 1.065425ms message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:46:36Z" - latency: 803.014µs message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:45:36Z" - latency: 791.114µs message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:44:36Z" - latency: 902.145µs message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:43:36Z" - latency: 1.241471ms message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:42:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T20:09:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-227-to-network-check-target-ip-10-0-131-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-227.ec2.internal uid: 73972175-4d73-4e55-845d-e96439372571 resourceVersion: "32118" uid: 40fac88a-3c0a-4d75-a9e3-26f868b6557b spec: sourcePod: network-check-source-8894fc9bd-6zzrt targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-20T20:16:36Z" message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.682059ms message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:51:36Z" - latency: 1.749133ms message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:50:36Z" - latency: 1.86189ms message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:49:36Z" - latency: 1.87249ms message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:48:36Z" - latency: 1.954151ms message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:47:36Z" - latency: 1.75604ms message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:46:36Z" - latency: 1.800973ms message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:45:36Z" - latency: 1.730009ms message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:44:36Z" - latency: 1.660904ms message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:43:36Z" - latency: 1.791778ms message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:42:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T20:09:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-227-to-network-check-target-ip-10-0-140-19 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-227.ec2.internal uid: 73972175-4d73-4e55-845d-e96439372571 resourceVersion: "32119" uid: 89075f10-7253-4eed-9e60-a91f1506ed25 spec: sourcePod: network-check-source-8894fc9bd-6zzrt targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-20T20:16:36Z" message: 'network-check-target-ip-10-0-140-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.003494ms message: 'network-check-target-ip-10-0-140-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:51:36Z" - latency: 1.99699ms message: 'network-check-target-ip-10-0-140-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:50:36Z" - latency: 1.97585ms message: 'network-check-target-ip-10-0-140-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:49:36Z" - latency: 2.139503ms message: 'network-check-target-ip-10-0-140-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:48:36Z" - latency: 2.022904ms message: 'network-check-target-ip-10-0-140-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:47:36Z" - latency: 1.880266ms message: 'network-check-target-ip-10-0-140-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:46:36Z" - latency: 1.708769ms message: 'network-check-target-ip-10-0-140-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:45:36Z" - latency: 1.829614ms message: 'network-check-target-ip-10-0-140-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:44:36Z" - latency: 1.919503ms message: 'network-check-target-ip-10-0-140-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:43:36Z" - latency: 2.040134ms message: 'network-check-target-ip-10-0-140-19: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:42:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T20:09:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-227-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-227.ec2.internal uid: 73972175-4d73-4e55-845d-e96439372571 resourceVersion: "32120" uid: 191b0443-5a84-4895-99e1-b4d024a1a453 spec: sourcePod: network-check-source-8894fc9bd-6zzrt targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-20T20:15:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 784.144µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:51:36Z" - latency: 1.816836ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T20:51:36Z" - latency: 860.704µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:50:36Z" - latency: 1.650747ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T20:50:36Z" - latency: 901.299µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:49:36Z" - latency: 1.932523ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T20:49:36Z" - latency: 915.576µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:48:36Z" - latency: 1.779524ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T20:48:36Z" - latency: 974.843µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T20:47:36Z" - latency: 1.720753ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T20:47:36Z" kind: List metadata: resourceVersion: ""