apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:37:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-110-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-110.ec2.internal uid: abbb40eb-b274-4721-ae7f-b98c49d49e42 resourceVersion: "38756" uid: aeed41a6-6ede-4ead-b812-ddfe4a93bd06 spec: sourcePod: network-check-source-8894fc9bd-4jx4z targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-23T16:44:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 848.576µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:33:55Z" - latency: 1.152472ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:32:55Z" - latency: 1.072389ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:31:55Z" - latency: 1.278249ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:30:55Z" - latency: 977.806µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:29:55Z" - latency: 954.862µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:28:55Z" - latency: 1.00866ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:27:55Z" - latency: 960.746µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:26:55Z" - latency: 1.011861ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:25:55Z" - latency: 1.355998ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:24:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:37:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-110-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-110.ec2.internal uid: abbb40eb-b274-4721-ae7f-b98c49d49e42 resourceVersion: "37804" uid: e6e0d4d0-95dd-4638-acd6-edb58c2984c6 spec: sourcePod: network-check-source-8894fc9bd-4jx4z targetEndpoint: a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T16:43:55Z" message: 'load-balancer-api-external: tcp connection to a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.26122ms message: 'load-balancer-api-external: tcp connection to a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:31:55Z" - latency: 8.244203ms message: 'load-balancer-api-external: resolved host name a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:31:55Z" - latency: 4.260783ms message: 'load-balancer-api-external: tcp connection to a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:30:55Z" - latency: 8.770724ms message: 'load-balancer-api-external: resolved host name a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:30:55Z" - latency: 19.901601ms message: 'load-balancer-api-external: tcp connection to a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:29:55Z" - latency: 8.737555ms message: 'load-balancer-api-external: resolved host name a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:29:55Z" - latency: 4.422321ms message: 'load-balancer-api-external: tcp connection to a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:28:55Z" - latency: 11.667447ms message: 'load-balancer-api-external: resolved host name a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:28:55Z" - latency: 4.779779ms message: 'load-balancer-api-external: tcp connection to a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:27:55Z" - latency: 8.320551ms message: 'load-balancer-api-external: resolved host name a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:27:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:37:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-110-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-110.ec2.internal uid: abbb40eb-b274-4721-ae7f-b98c49d49e42 resourceVersion: "37805" uid: fce9b6a0-507c-44c7-808a-9b9f6c5629e5 spec: sourcePod: network-check-source-8894fc9bd-4jx4z targetEndpoint: a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-23T16:43:55Z" message: 'load-balancer-api-internal: tcp connection to a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.301362ms message: 'load-balancer-api-internal: tcp connection to a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:31:55Z" - latency: 8.142534ms message: 'load-balancer-api-internal: resolved host name a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:31:55Z" - latency: 3.825551ms message: 'load-balancer-api-internal: tcp connection to a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:30:55Z" - latency: 8.727048ms message: 'load-balancer-api-internal: resolved host name a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:30:55Z" - latency: 9.724669ms message: 'load-balancer-api-internal: tcp connection to a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:29:55Z" - latency: 8.613371ms message: 'load-balancer-api-internal: resolved host name a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:29:55Z" - latency: 4.482898ms message: 'load-balancer-api-internal: tcp connection to a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:28:55Z" - latency: 11.594479ms message: 'load-balancer-api-internal: resolved host name a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:28:55Z" - latency: 4.737421ms message: 'load-balancer-api-internal: tcp connection to a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:27:55Z" - latency: 8.242526ms message: 'load-balancer-api-internal: resolved host name a58fe27c00c7b431797f7c7ce402db1d-83edc0d6467e7308.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-23T17:27:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:37:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-110-to-network-check-target-ip-10-0-130-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-110.ec2.internal uid: abbb40eb-b274-4721-ae7f-b98c49d49e42 resourceVersion: "38753" uid: e546f6bd-b551-42d2-b278-0764aec07725 spec: sourcePod: network-check-source-8894fc9bd-4jx4z targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-23T16:44:55Z" message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 820.821µs message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:33:55Z" - latency: 870.352µs message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:32:55Z" - latency: 772.567µs message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:31:55Z" - latency: 1.442213ms message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:30:55Z" - latency: 828.269µs message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:29:55Z" - latency: 1.01603ms message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:28:55Z" - latency: 743.489µs message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:27:55Z" - latency: 831.238µs message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:26:55Z" - latency: 833.311µs message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:25:55Z" - latency: 704.255µs message: 'network-check-target-ip-10-0-130-110: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:24:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:37:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-110-to-network-check-target-ip-10-0-134-187 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-110.ec2.internal uid: abbb40eb-b274-4721-ae7f-b98c49d49e42 resourceVersion: "38755" uid: ce3fcab5-6ac1-4a49-a828-05623082a8c6 spec: sourcePod: network-check-source-8894fc9bd-4jx4z targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-23T16:44:55Z" message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.130872ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:33:55Z" - latency: 2.175518ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:32:55Z" - latency: 2.03008ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:31:55Z" - latency: 1.929675ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:30:55Z" - latency: 2.207261ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:29:55Z" - latency: 2.160299ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:28:55Z" - latency: 2.244585ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:27:55Z" - latency: 2.003575ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:26:55Z" - latency: 2.322277ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:25:55Z" - latency: 2.136208ms message: 'network-check-target-ip-10-0-134-187: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:24:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:37:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-110-to-network-check-target-ip-10-0-135-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-110.ec2.internal uid: abbb40eb-b274-4721-ae7f-b98c49d49e42 resourceVersion: "38754" uid: 89b86382-956b-400a-8d2e-8c4d606939f5 spec: sourcePod: network-check-source-8894fc9bd-4jx4z targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-23T16:44:55Z" message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.804208ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:33:55Z" - latency: 2.026146ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:32:55Z" - latency: 1.789715ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:31:55Z" - latency: 1.970642ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:30:55Z" - latency: 1.883109ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:29:55Z" - latency: 1.810616ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:28:55Z" - latency: 1.836766ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:27:55Z" - latency: 1.736553ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:26:55Z" - latency: 1.961589ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:25:55Z" - latency: 1.918287ms message: 'network-check-target-ip-10-0-135-57: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:24:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-23T16:37:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-110-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-110.ec2.internal uid: abbb40eb-b274-4721-ae7f-b98c49d49e42 resourceVersion: "37803" uid: 116609ef-297d-45a2-b07f-d98e468e2c03 spec: sourcePod: network-check-source-8894fc9bd-4jx4z targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-23T16:43:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.152202ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:31:55Z" - latency: 1.74622ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T17:31:55Z" - latency: 1.070728ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:30:55Z" - latency: 1.746534ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T17:30:55Z" - latency: 1.040193ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:29:55Z" - latency: 1.629624ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T17:29:55Z" - latency: 852.161µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:28:55Z" - latency: 1.797963ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T17:28:55Z" - latency: 864.379µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-23T17:27:55Z" - latency: 1.620166ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-23T17:27:55Z" kind: List metadata: resourceVersion: ""