apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:48:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-17-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-17.us-west-2.compute.internal uid: fba5a3d0-12a0-4982-96c8-a9f2ef1e8f00 resourceVersion: "124179" uid: 094be46e-8726-46f3-ae88-f3c1710c99a2 spec: sourcePod: network-check-source-6f78d59f99-qzvdr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T21:55:43Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.127622ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:58:42Z" - latency: 904.157µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:57:42Z" - latency: 1.507274ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:56:42Z" - latency: 1.333077ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:55:42Z" - latency: 1.899384ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:42Z" - latency: 886.69µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:42Z" - latency: 1.453367ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:42Z" - latency: 1.381805ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:42Z" - latency: 1.426529ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:42Z" - latency: 1.29937ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:48:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-17-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-17.us-west-2.compute.internal uid: fba5a3d0-12a0-4982-96c8-a9f2ef1e8f00 resourceVersion: "118223" uid: 5f5c9230-2aa3-4064-bac2-f8c24f4f68ce spec: sourcePod: network-check-source-6f78d59f99-qzvdr targetEndpoint: a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:54:43Z" message: 'load-balancer-api-external: tcp connection to a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 51.101148ms message: 'load-balancer-api-external: tcp connection to a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:42Z" - latency: 8.519871ms message: 'load-balancer-api-external: resolved host name a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:54:42Z" - latency: 54.854719ms message: 'load-balancer-api-external: tcp connection to a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:42Z" - latency: 7.212679ms message: 'load-balancer-api-external: resolved host name a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:53:42Z" - latency: 56.096895ms message: 'load-balancer-api-external: tcp connection to a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:42Z" - latency: 7.987886ms message: 'load-balancer-api-external: resolved host name a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:52:42Z" - latency: 60.550472ms message: 'load-balancer-api-external: tcp connection to a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:42Z" - latency: 6.719729ms message: 'load-balancer-api-external: resolved host name a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:51:42Z" - latency: 56.561051ms message: 'load-balancer-api-external: tcp connection to a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:42Z" - latency: 8.203147ms message: 'load-balancer-api-external: resolved host name a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:50:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:48:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-17-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-17.us-west-2.compute.internal uid: fba5a3d0-12a0-4982-96c8-a9f2ef1e8f00 resourceVersion: "118224" uid: bf085d07-1704-4559-adb6-39343e861c3b spec: sourcePod: network-check-source-6f78d59f99-qzvdr targetEndpoint: a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:54:43Z" message: 'load-balancer-api-internal: tcp connection to a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.320703ms message: 'load-balancer-api-internal: tcp connection to a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:42Z" - latency: 8.576568ms message: 'load-balancer-api-internal: resolved host name a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:54:42Z" - latency: 50.355455ms message: 'load-balancer-api-internal: tcp connection to a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:42Z" - latency: 7.325027ms message: 'load-balancer-api-internal: resolved host name a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:53:42Z" - latency: 56.208725ms message: 'load-balancer-api-internal: tcp connection to a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:42Z" - latency: 7.901987ms message: 'load-balancer-api-internal: resolved host name a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:52:42Z" - latency: 56.714467ms message: 'load-balancer-api-internal: tcp connection to a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:42Z" - latency: 6.798689ms message: 'load-balancer-api-internal: resolved host name a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:51:42Z" - latency: 51.330893ms message: 'load-balancer-api-internal: tcp connection to a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:42Z" - latency: 8.117414ms message: 'load-balancer-api-internal: resolved host name a26314a26c7f3463b9bcb9cfe0458715-c9cd20b13308b9a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:50:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:48:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-17-to-network-check-target-ip-10-0-133-91 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-17.us-west-2.compute.internal uid: fba5a3d0-12a0-4982-96c8-a9f2ef1e8f00 resourceVersion: "124175" uid: 8b5e8d8e-ae82-4e99-96a8-fc926c7921f5 spec: sourcePod: network-check-source-6f78d59f99-qzvdr targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:55:42Z" message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.160771ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:58:42Z" - latency: 2.512334ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:57:42Z" - latency: 2.35841ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:56:42Z" - latency: 2.440173ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:55:42Z" - latency: 2.333188ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:42Z" - latency: 2.134704ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:42Z" - latency: 2.953004ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:42Z" - latency: 2.61956ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:42Z" - latency: 2.574255ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:42Z" - latency: 2.289567ms message: 'network-check-target-ip-10-0-133-91: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:48:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-17-to-network-check-target-ip-10-0-137-17 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-17.us-west-2.compute.internal uid: fba5a3d0-12a0-4982-96c8-a9f2ef1e8f00 resourceVersion: "124173" uid: f68dda5b-6d97-4bf7-83ba-a7d851260ba1 spec: sourcePod: network-check-source-6f78d59f99-qzvdr targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:55:42Z" message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.140677ms message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:58:42Z" - latency: 1.153405ms message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:57:42Z" - latency: 850.142µs message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:56:42Z" - latency: 984.453µs message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:55:42Z" - latency: 2.096188ms message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:42Z" - latency: 964.847µs message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:42Z" - latency: 2.496508ms message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:42Z" - latency: 1.727628ms message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:42Z" - latency: 1.249083ms message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:42Z" - latency: 912.636µs message: 'network-check-target-ip-10-0-137-17: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:48:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-17-to-network-check-target-ip-10-0-141-86 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-17.us-west-2.compute.internal uid: fba5a3d0-12a0-4982-96c8-a9f2ef1e8f00 resourceVersion: "124174" uid: c8c4e004-2ddd-4659-b80a-4e031764912c spec: sourcePod: network-check-source-6f78d59f99-qzvdr targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:55:42Z" message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.130744ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:58:42Z" - latency: 2.431241ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:57:42Z" - latency: 2.254643ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:56:42Z" - latency: 2.281889ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:55:42Z" - latency: 2.502967ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:42Z" - latency: 1.912075ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:42Z" - latency: 2.557623ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:42Z" - latency: 2.52933ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:42Z" - latency: 2.093362ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:42Z" - latency: 2.056518ms message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:49:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:48:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-17-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-17.us-west-2.compute.internal uid: fba5a3d0-12a0-4982-96c8-a9f2ef1e8f00 resourceVersion: "118220" uid: ec55bbfc-3a39-40c7-ac2c-d7a9c6fdc4dd spec: sourcePod: network-check-source-6f78d59f99-qzvdr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T21:54:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.478144ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:42Z" - latency: 2.628683ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:54:42Z" - latency: 1.172375ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:42Z" - latency: 1.749412ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:53:42Z" - latency: 1.012521ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:42Z" - latency: 3.358461ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:52:42Z" - latency: 1.157243ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:42Z" - latency: 1.853112ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:51:42Z" - latency: 1.093729ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:42Z" - latency: 2.145817ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:50:42Z" kind: List metadata: resourceVersion: ""