apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T13:06:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-63-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-63.us-west-2.compute.internal uid: f916f6e2-4e66-441c-864e-b36fc633d89e resourceVersion: "167001" uid: 40588678-8862-482e-a619-1cb948c19e15 spec: sourcePod: network-check-source-6f78d59f99-4nxqr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T13:13:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.278277ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:58:36Z" - latency: 1.444565ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:57:36Z" - latency: 997.604µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:56:36Z" - latency: 977.926µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:55:36Z" - latency: 1.714685ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:54:36Z" - latency: 2.072694ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:53:36Z" - latency: 1.42894ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:52:36Z" - latency: 979.743µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:51:36Z" - latency: 1.133204ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:50:36Z" - latency: 1.048038ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:49:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T13:06:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-63-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-63.us-west-2.compute.internal uid: f916f6e2-4e66-441c-864e-b36fc633d89e resourceVersion: "168562" uid: 5df658ca-daff-4c93-93cb-5372d2535038 spec: sourcePod: network-check-source-6f78d59f99-4nxqr targetEndpoint: a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T13:12:36Z" message: 'load-balancer-api-external: tcp connection to a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 50.703639ms message: 'load-balancer-api-external: tcp connection to a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:00:36Z" - latency: 7.073607ms message: 'load-balancer-api-external: resolved host name a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T15:00:36Z" - latency: 68.853124ms message: 'load-balancer-api-external: tcp connection to a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:59:36Z" - latency: 7.730496ms message: 'load-balancer-api-external: resolved host name a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:59:36Z" - latency: 55.544527ms message: 'load-balancer-api-external: tcp connection to a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:58:36Z" - latency: 6.923823ms message: 'load-balancer-api-external: resolved host name a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:58:36Z" - latency: 51.782255ms message: 'load-balancer-api-external: tcp connection to a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:57:36Z" - latency: 7.790446ms message: 'load-balancer-api-external: resolved host name a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:57:36Z" - latency: 51.133741ms message: 'load-balancer-api-external: tcp connection to a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:56:36Z" - latency: 9.001115ms message: 'load-balancer-api-external: resolved host name a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:56:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T13:06:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-63-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-63.us-west-2.compute.internal uid: f916f6e2-4e66-441c-864e-b36fc633d89e resourceVersion: "168563" uid: 5dc9ed7c-cc30-4ddd-86e6-2f6d25205c87 spec: sourcePod: network-check-source-6f78d59f99-4nxqr targetEndpoint: a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T13:12:36Z" message: 'load-balancer-api-internal: tcp connection to a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 50.759295ms message: 'load-balancer-api-internal: tcp connection to a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:00:36Z" - latency: 6.965511ms message: 'load-balancer-api-internal: resolved host name a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T15:00:36Z" - latency: 86.580623ms message: 'load-balancer-api-internal: tcp connection to a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:59:36Z" - latency: 7.699941ms message: 'load-balancer-api-internal: resolved host name a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:59:36Z" - latency: 55.590844ms message: 'load-balancer-api-internal: tcp connection to a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:58:36Z" - latency: 6.900801ms message: 'load-balancer-api-internal: resolved host name a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:58:36Z" - latency: 54.890079ms message: 'load-balancer-api-internal: tcp connection to a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:57:36Z" - latency: 7.750428ms message: 'load-balancer-api-internal: resolved host name a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:57:36Z" - latency: 51.137924ms message: 'load-balancer-api-internal: tcp connection to a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:56:36Z" - latency: 8.960238ms message: 'load-balancer-api-internal: resolved host name a16aeb6c627d247dd9f516a896748b1c-7174c5b4c9fb5a11.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T14:56:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T13:06:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-63-to-network-check-target-ip-10-0-129-63 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-63.us-west-2.compute.internal uid: f916f6e2-4e66-441c-864e-b36fc633d89e resourceVersion: "166994" uid: c7119e8d-45cd-4695-a3ac-f3f8d02e7bd0 spec: sourcePod: network-check-source-6f78d59f99-4nxqr targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T13:13:36Z" message: 'network-check-target-ip-10-0-129-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.035998ms message: 'network-check-target-ip-10-0-129-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:58:36Z" - latency: 982.962µs message: 'network-check-target-ip-10-0-129-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:57:36Z" - latency: 1.738995ms message: 'network-check-target-ip-10-0-129-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:56:36Z" - latency: 1.444291ms message: 'network-check-target-ip-10-0-129-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:55:36Z" - latency: 822.548µs message: 'network-check-target-ip-10-0-129-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:54:36Z" - latency: 1.75381ms message: 'network-check-target-ip-10-0-129-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:53:36Z" - latency: 1.636835ms message: 'network-check-target-ip-10-0-129-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:52:36Z" - latency: 971.727µs message: 'network-check-target-ip-10-0-129-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:51:36Z" - latency: 1.530878ms message: 'network-check-target-ip-10-0-129-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:50:36Z" - latency: 896.254µs message: 'network-check-target-ip-10-0-129-63: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:49:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T13:06:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-63-to-network-check-target-ip-10-0-130-198 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-63.us-west-2.compute.internal uid: f916f6e2-4e66-441c-864e-b36fc633d89e resourceVersion: "166995" uid: 1a0e566d-8488-4c98-b805-fbd490b8eaed spec: sourcePod: network-check-source-6f78d59f99-4nxqr targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T13:13:36Z" message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.099307ms message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:58:36Z" - latency: 2.832962ms message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:57:36Z" - latency: 2.909257ms message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:56:36Z" - latency: 2.596776ms message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:55:36Z" - latency: 2.70776ms message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:54:36Z" - latency: 2.370414ms message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:53:36Z" - latency: 2.553045ms message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:52:36Z" - latency: 2.484629ms message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:51:36Z" - latency: 2.244808ms message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:50:36Z" - latency: 2.544488ms message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:49:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T13:06:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-63-to-network-check-target-ip-10-0-132-174 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-63.us-west-2.compute.internal uid: f916f6e2-4e66-441c-864e-b36fc633d89e resourceVersion: "166998" uid: 4e9a6589-1e84-40f6-877c-2446a495a84a spec: sourcePod: network-check-source-6f78d59f99-4nxqr targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T13:13:36Z" message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.112148ms message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:58:36Z" - latency: 2.387189ms message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:57:36Z" - latency: 2.747224ms message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:56:36Z" - latency: 2.580051ms message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:55:36Z" - latency: 2.49609ms message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:54:36Z" - latency: 2.882939ms message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:53:36Z" - latency: 2.529368ms message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:52:36Z" - latency: 2.584566ms message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:51:36Z" - latency: 2.843914ms message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:50:36Z" - latency: 1.97475ms message: 'network-check-target-ip-10-0-132-174: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:49:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T13:06:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-63-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-63.us-west-2.compute.internal uid: f916f6e2-4e66-441c-864e-b36fc633d89e resourceVersion: "168561" uid: 1b44b540-0989-41c2-a925-222bfbb02807 spec: sourcePod: network-check-source-6f78d59f99-4nxqr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T13:12:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.30071ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T15:00:36Z" - latency: 2.104209ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T15:00:36Z" - latency: 906.425µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:59:36Z" - latency: 2.217156ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T14:59:36Z" - latency: 969.103µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:58:36Z" - latency: 2.039025ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T14:58:36Z" - latency: 1.048094ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:57:36Z" - latency: 2.219605ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T14:57:36Z" - latency: 871.439µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T14:56:36Z" - latency: 2.152359ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T14:56:36Z" kind: List metadata: resourceVersion: ""