apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:14:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-149-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-149.ec2.internal uid: 37bf5c2a-8f55-4752-a0f2-22fd096dc1c5 resourceVersion: "149672" uid: 8627fae1-2298-41ac-a5e8-e779af4da9c8 spec: sourcePod: network-check-source-6f78d59f99-dq7ch targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T21:21:20Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.671667ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:20Z" - latency: 1.117907ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:09:20Z" - latency: 805.623µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:08:20Z" - latency: 1.331664ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:07:20Z" - latency: 1.240625ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:06:20Z" - latency: 8.851343ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:05:20Z" - latency: 2.336973ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:04:20Z" - latency: 855.547µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:03:20Z" - latency: 1.220599ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:02:20Z" - latency: 959.365µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:01:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:14:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-149-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-149.ec2.internal uid: 37bf5c2a-8f55-4752-a0f2-22fd096dc1c5 resourceVersion: "158699" uid: d9f95435-fa8d-48c4-a43d-bfb96ec17a0d spec: sourcePod: network-check-source-6f78d59f99-dq7ch targetEndpoint: a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:20:20Z" message: 'load-balancer-api-external: tcp connection to a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.407924ms message: 'load-balancer-api-external: tcp connection to a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:14:20Z" - latency: 41.551991ms message: 'load-balancer-api-external: resolved host name a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:14:20Z" - latency: 14.933814ms message: 'load-balancer-api-external: tcp connection to a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:13:20Z" - latency: 7.293931ms message: 'load-balancer-api-external: resolved host name a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:13:20Z" - latency: 18.494131ms message: 'load-balancer-api-external: tcp connection to a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:12:20Z" - latency: 8.129092ms message: 'load-balancer-api-external: resolved host name a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:12:20Z" - latency: 15.494769ms message: 'load-balancer-api-external: tcp connection to a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:11:20Z" - latency: 6.673433ms message: 'load-balancer-api-external: resolved host name a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:11:20Z" - latency: 17.375332ms message: 'load-balancer-api-external: tcp connection to a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:20Z" - latency: 7.427042ms message: 'load-balancer-api-external: resolved host name a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:10:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:14:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-149-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-149.ec2.internal uid: 37bf5c2a-8f55-4752-a0f2-22fd096dc1c5 resourceVersion: "158698" uid: 189d5a3f-a60d-44b1-8ed6-73765bd7788b spec: sourcePod: network-check-source-6f78d59f99-dq7ch targetEndpoint: a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:20:20Z" message: 'load-balancer-api-internal: tcp connection to a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.395324ms message: 'load-balancer-api-internal: tcp connection to a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:14:20Z" - latency: 41.620108ms message: 'load-balancer-api-internal: resolved host name a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:14:20Z" - latency: 17.683504ms message: 'load-balancer-api-internal: tcp connection to a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:13:20Z" - latency: 7.217101ms message: 'load-balancer-api-internal: resolved host name a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:13:20Z" - latency: 13.518376ms message: 'load-balancer-api-internal: tcp connection to a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:12:20Z" - latency: 8.177974ms message: 'load-balancer-api-internal: resolved host name a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:12:20Z" - latency: 17.019645ms message: 'load-balancer-api-internal: tcp connection to a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:11:20Z" - latency: 6.626386ms message: 'load-balancer-api-internal: resolved host name a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:11:20Z" - latency: 15.846718ms message: 'load-balancer-api-internal: tcp connection to a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:20Z" - latency: 7.39807ms message: 'load-balancer-api-internal: resolved host name a684b1ccd511c4728b56d83348d69821-be62a566440ea101.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:10:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:14:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-149-to-network-check-target-ip-10-0-129-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-149.ec2.internal uid: 37bf5c2a-8f55-4752-a0f2-22fd096dc1c5 resourceVersion: "149671" uid: 2d8a8c68-cdcf-4e8c-bb30-70be8fc79af1 spec: sourcePod: network-check-source-6f78d59f99-dq7ch targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:21:20Z" message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.471288ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:20Z" - latency: 2.58216ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:09:20Z" - latency: 2.243028ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:08:20Z" - latency: 2.751858ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:07:20Z" - latency: 2.898491ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:06:20Z" - latency: 6.242147ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:05:20Z" - latency: 17.330765ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:04:20Z" - latency: 2.368941ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:03:20Z" - latency: 2.548891ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:02:20Z" - latency: 2.387566ms message: 'network-check-target-ip-10-0-129-84: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:01:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:14:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-149-to-network-check-target-ip-10-0-133-149 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-149.ec2.internal uid: 37bf5c2a-8f55-4752-a0f2-22fd096dc1c5 resourceVersion: "149669" uid: 77e95893-4061-441c-b5c8-8a627f0a0981 spec: sourcePod: network-check-source-6f78d59f99-dq7ch targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:21:20Z" message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 877.442µs message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:20Z" - latency: 943.576µs message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:09:20Z" - latency: 1.199565ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:08:20Z" - latency: 1.184895ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:07:20Z" - latency: 801.916µs message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:06:20Z" - latency: 8.959953ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:05:20Z" - latency: 4.439069ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:04:20Z" - latency: 959.818µs message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:03:20Z" - latency: 1.411617ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:02:20Z" - latency: 1.196073ms message: 'network-check-target-ip-10-0-133-149: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:01:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:14:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-149-to-network-check-target-ip-10-0-142-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-149.ec2.internal uid: 37bf5c2a-8f55-4752-a0f2-22fd096dc1c5 resourceVersion: "149670" uid: ba57442d-bd38-4aaa-9d2b-9a62616c16dd spec: sourcePod: network-check-source-6f78d59f99-dq7ch targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:21:20Z" message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.307925ms message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:20Z" - latency: 2.590638ms message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:09:20Z" - latency: 2.207553ms message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:08:20Z" - latency: 2.867155ms message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:07:20Z" - latency: 1.86618ms message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:06:20Z" - latency: 15.148928ms message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:05:20Z" - latency: 16.735925ms message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:04:20Z" - latency: 2.692104ms message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:03:20Z" - latency: 2.9158ms message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:02:20Z" - latency: 2.186908ms message: 'network-check-target-ip-10-0-142-232: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:01:20Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:14:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-149-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-149.ec2.internal uid: 37bf5c2a-8f55-4752-a0f2-22fd096dc1c5 resourceVersion: "158695" uid: 32580859-1d86-4fc3-bda1-dbf43d564fd9 spec: sourcePod: network-check-source-6f78d59f99-dq7ch targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T21:20:20Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 988.879µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:14:20Z" - latency: 2.34391ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:14:20Z" - latency: 911.517µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:13:20Z" - latency: 1.953822ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:13:20Z" - latency: 990.73µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:12:20Z" - latency: 2.025331ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:12:20Z" - latency: 1.05636ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:11:20Z" - latency: 1.896542ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:11:20Z" - latency: 958.637µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:10:20Z" - latency: 1.86559ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:10:20Z" kind: List metadata: resourceVersion: ""