apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:02:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-235-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-235.us-west-1.compute.internal uid: e3485da1-1e24-45be-a754-b3a6a9c54f91 resourceVersion: "36294" uid: 1e6e757b-bcf2-4e0e-aacd-8b802df3fbe7 spec: sourcePod: network-check-source-6f78d59f99-sqkq6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T20:09:15Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.255302ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:26:14Z" - latency: 1.335993ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:25:14Z" - latency: 1.546448ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:24:14Z" - latency: 1.033193ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:23:14Z" - latency: 1.122561ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:22:14Z" - latency: 766.165µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:21:14Z" - latency: 995.383µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:20:14Z" - latency: 948.155µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:19:14Z" - latency: 1.088245ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:18:14Z" - latency: 1.002644ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:17:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:02:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-235-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-235.us-west-1.compute.internal uid: e3485da1-1e24-45be-a754-b3a6a9c54f91 resourceVersion: "36295" uid: 24389560-4c5f-4a28-a1dc-72c902f4429f spec: sourcePod: network-check-source-6f78d59f99-sqkq6 targetEndpoint: a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T20:08:15Z" message: 'load-balancer-api-external: tcp connection to a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.576723ms message: 'load-balancer-api-external: tcp connection to a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:26:14Z" - latency: 7.983761ms message: 'load-balancer-api-external: resolved host name a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:26:14Z" - latency: 54.084362ms message: 'load-balancer-api-external: tcp connection to a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:25:14Z" - latency: 7.724884ms message: 'load-balancer-api-external: resolved host name a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:25:14Z" - latency: 54.812148ms message: 'load-balancer-api-external: tcp connection to a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:24:14Z" - latency: 50.436904ms message: 'load-balancer-api-external: resolved host name a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:24:14Z" - latency: 52.848344ms message: 'load-balancer-api-external: tcp connection to a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:23:14Z" - latency: 7.104532ms message: 'load-balancer-api-external: resolved host name a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:23:14Z" - latency: 53.655836ms message: 'load-balancer-api-external: tcp connection to a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:22:14Z" - latency: 7.543103ms message: 'load-balancer-api-external: resolved host name a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:22:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:02:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-235-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-235.us-west-1.compute.internal uid: e3485da1-1e24-45be-a754-b3a6a9c54f91 resourceVersion: "36296" uid: 06a15723-0527-4e27-9c92-d3e28fbd6de1 spec: sourcePod: network-check-source-6f78d59f99-sqkq6 targetEndpoint: a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T20:08:15Z" message: 'load-balancer-api-internal: tcp connection to a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.745284ms message: 'load-balancer-api-internal: tcp connection to a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:26:14Z" - latency: 7.963716ms message: 'load-balancer-api-internal: resolved host name a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:26:14Z" - latency: 54.78252ms message: 'load-balancer-api-internal: tcp connection to a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:25:14Z" - latency: 7.694745ms message: 'load-balancer-api-internal: resolved host name a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:25:14Z" - latency: 54.843355ms message: 'load-balancer-api-internal: tcp connection to a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:24:14Z" - latency: 50.397751ms message: 'load-balancer-api-internal: resolved host name a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:24:14Z" - latency: 52.964532ms message: 'load-balancer-api-internal: tcp connection to a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:23:14Z" - latency: 7.198673ms message: 'load-balancer-api-internal: resolved host name a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:23:14Z" - latency: 54.404714ms message: 'load-balancer-api-internal: tcp connection to a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:22:14Z" - latency: 7.472397ms message: 'load-balancer-api-internal: resolved host name a295bc2c6542f4b488dcdf284527d8bd-cfb3317acbd8a81f.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:22:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:02:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-235-to-network-check-target-ip-10-0-140-181 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-235.us-west-1.compute.internal uid: e3485da1-1e24-45be-a754-b3a6a9c54f91 resourceVersion: "36292" uid: 3fd3055d-c50b-469f-83e3-67153786f955 spec: sourcePod: network-check-source-6f78d59f99-sqkq6 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:09:14Z" message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.373188ms message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:26:14Z" - latency: 2.502765ms message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:25:14Z" - latency: 2.444412ms message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:24:14Z" - latency: 2.030675ms message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:23:14Z" - latency: 1.933751ms message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:22:14Z" - latency: 1.876538ms message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:21:14Z" - latency: 1.771514ms message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:20:14Z" - latency: 2.139849ms message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:19:14Z" - latency: 2.129923ms message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:18:14Z" - latency: 2.24627ms message: 'network-check-target-ip-10-0-140-181: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:17:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:02:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-235-to-network-check-target-ip-10-0-140-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-235.us-west-1.compute.internal uid: e3485da1-1e24-45be-a754-b3a6a9c54f91 resourceVersion: "36291" uid: ef2ce804-db8c-41ed-b652-3e813e491eb8 spec: sourcePod: network-check-source-6f78d59f99-sqkq6 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:09:14Z" message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.883851ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:26:14Z" - latency: 2.027449ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:25:14Z" - latency: 1.859742ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:24:14Z" - latency: 1.82418ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:23:14Z" - latency: 2.230341ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:22:14Z" - latency: 1.908348ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:21:14Z" - latency: 1.986779ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:20:14Z" - latency: 1.876974ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:19:14Z" - latency: 1.833608ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:18:14Z" - latency: 2.837918ms message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:17:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:02:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-235-to-network-check-target-ip-10-0-143-235 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-235.us-west-1.compute.internal uid: e3485da1-1e24-45be-a754-b3a6a9c54f91 resourceVersion: "36290" uid: 8685bea9-e662-4438-96b0-c77afac6239a spec: sourcePod: network-check-source-6f78d59f99-sqkq6 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:09:14Z" message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.291839ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:26:14Z" - latency: 1.175212ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:25:14Z" - latency: 837.022µs message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:24:14Z" - latency: 836.705µs message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:23:14Z" - latency: 1.259843ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:22:14Z" - latency: 878.387µs message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:21:14Z" - latency: 1.126502ms message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:20:14Z" - latency: 979.909µs message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:19:14Z" - latency: 796.705µs message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:18:14Z" - latency: 874.63µs message: 'network-check-target-ip-10-0-143-235: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:17:14Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:02:14Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-235-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-235.us-west-1.compute.internal uid: e3485da1-1e24-45be-a754-b3a6a9c54f91 resourceVersion: "36293" uid: 796019ba-8c09-4435-9c6c-c577adaa71c4 spec: sourcePod: network-check-source-6f78d59f99-sqkq6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T20:08:14Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 823.361µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:26:14Z" - latency: 1.807062ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:26:14Z" - latency: 833.391µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:25:14Z" - latency: 1.775543ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:25:14Z" - latency: 749.12µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:24:14Z" - latency: 1.703713ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:24:14Z" - latency: 860.643µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:23:14Z" - latency: 1.655129ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:23:14Z" - latency: 922.524µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:22:14Z" - latency: 1.516019ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:22:14Z" kind: List metadata: resourceVersion: ""