apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T12:51:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-209-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-209.us-west-2.compute.internal uid: f2925fcf-2699-4db4-817a-acd3e89c48dd resourceVersion: "24413" uid: 4dc52c40-d97b-4af0-8ce1-789984d92aff spec: sourcePod: network-check-source-6f78d59f99-5ptxj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T12:58:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 944.44µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:26:13Z" - latency: 1.683841ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:25:13Z" - latency: 1.189336ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:24:13Z" - latency: 936.659µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:23:13Z" - latency: 977.907µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:22:13Z" - latency: 1.276922ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:21:13Z" - latency: 1.334155ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:20:13Z" - latency: 1.038799ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:19:13Z" - latency: 1.661533ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:18:13Z" - latency: 1.100826ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:17:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T12:51:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-209-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-209.us-west-2.compute.internal uid: f2925fcf-2699-4db4-817a-acd3e89c48dd resourceVersion: "24780" uid: c967e52c-5c36-42e6-9cea-0914562b4968 spec: sourcePod: network-check-source-6f78d59f99-5ptxj targetEndpoint: a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T12:57:13Z" message: 'load-balancer-api-external: tcp connection to a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.180197ms message: 'load-balancer-api-external: tcp connection to a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:27:13Z" - latency: 7.351412ms message: 'load-balancer-api-external: resolved host name a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:27:13Z" - latency: 50.202151ms message: 'load-balancer-api-external: tcp connection to a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:26:13Z" - latency: 8.924294ms message: 'load-balancer-api-external: resolved host name a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:26:13Z" - latency: 50.921152ms message: 'load-balancer-api-external: tcp connection to a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:25:13Z" - latency: 7.546092ms message: 'load-balancer-api-external: resolved host name a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:25:13Z" - latency: 53.699691ms message: 'load-balancer-api-external: tcp connection to a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:24:13Z" - latency: 7.057041ms message: 'load-balancer-api-external: resolved host name a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:24:13Z" - latency: 52.398415ms message: 'load-balancer-api-external: tcp connection to a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:23:13Z" - latency: 8.930316ms message: 'load-balancer-api-external: resolved host name a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:23:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T12:51:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-209-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-209.us-west-2.compute.internal uid: f2925fcf-2699-4db4-817a-acd3e89c48dd resourceVersion: "24779" uid: 6629c94c-52c6-4a60-8457-5ddc9a695593 spec: sourcePod: network-check-source-6f78d59f99-5ptxj targetEndpoint: a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T12:57:13Z" message: 'load-balancer-api-internal: tcp connection to a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 50.071124ms message: 'load-balancer-api-internal: tcp connection to a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:27:13Z" - latency: 7.331842ms message: 'load-balancer-api-internal: resolved host name a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:27:13Z" - latency: 50.227262ms message: 'load-balancer-api-internal: tcp connection to a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:26:13Z" - latency: 8.870843ms message: 'load-balancer-api-internal: resolved host name a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:26:13Z" - latency: 50.959332ms message: 'load-balancer-api-internal: tcp connection to a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:25:13Z" - latency: 7.632739ms message: 'load-balancer-api-internal: resolved host name a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:25:13Z" - latency: 53.712193ms message: 'load-balancer-api-internal: tcp connection to a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:24:13Z" - latency: 6.970684ms message: 'load-balancer-api-internal: resolved host name a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:24:13Z" - latency: 57.550069ms message: 'load-balancer-api-internal: tcp connection to a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:23:13Z" - latency: 8.968554ms message: 'load-balancer-api-internal: resolved host name a4065eeaf9336427bab0e61e0a91d253-2eee41dc4484d68d.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T13:23:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T12:51:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-209-to-network-check-target-ip-10-0-131-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-209.us-west-2.compute.internal uid: f2925fcf-2699-4db4-817a-acd3e89c48dd resourceVersion: "24411" uid: 05d6710a-72fd-476f-93ad-d56d7838abae spec: sourcePod: network-check-source-6f78d59f99-5ptxj targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T12:58:13Z" message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.037702ms message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:26:13Z" - latency: 2.036111ms message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:25:13Z" - latency: 1.881362ms message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:24:13Z" - latency: 2.073621ms message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:23:13Z" - latency: 1.957969ms message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:22:13Z" - latency: 1.808703ms message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:21:13Z" - latency: 1.894689ms message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:20:13Z" - latency: 2.32806ms message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:19:13Z" - latency: 1.960724ms message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:18:13Z" - latency: 2.094729ms message: 'network-check-target-ip-10-0-131-125: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:17:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T12:51:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-209-to-network-check-target-ip-10-0-137-218 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-209.us-west-2.compute.internal uid: f2925fcf-2699-4db4-817a-acd3e89c48dd resourceVersion: "24412" uid: a3c47779-0f03-4eba-8b71-74e1ad9cf2c2 spec: sourcePod: network-check-source-6f78d59f99-5ptxj targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T12:58:13Z" message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.229784ms message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:26:13Z" - latency: 2.318503ms message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:25:13Z" - latency: 2.105265ms message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:24:13Z" - latency: 2.438969ms message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:23:13Z" - latency: 1.976335ms message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:22:13Z" - latency: 2.00969ms message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:21:13Z" - latency: 2.282286ms message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:20:13Z" - latency: 2.747794ms message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:19:13Z" - latency: 2.086908ms message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:18:13Z" - latency: 2.126767ms message: 'network-check-target-ip-10-0-137-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:17:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T12:51:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-209-to-network-check-target-ip-10-0-139-209 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-209.us-west-2.compute.internal uid: f2925fcf-2699-4db4-817a-acd3e89c48dd resourceVersion: "24410" uid: 6e50defc-bfe0-446a-88ad-212f70e0f2d6 spec: sourcePod: network-check-source-6f78d59f99-5ptxj targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T12:58:13Z" message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 892.07µs message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:26:13Z" - latency: 964.635µs message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:25:13Z" - latency: 1.152064ms message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:24:13Z" - latency: 1.595929ms message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:23:13Z" - latency: 1.410973ms message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:22:13Z" - latency: 1.466399ms message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:21:13Z" - latency: 1.41362ms message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:20:13Z" - latency: 1.456478ms message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:19:13Z" - latency: 1.110344ms message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:18:13Z" - latency: 945.804µs message: 'network-check-target-ip-10-0-139-209: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:17:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T12:51:13Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-209-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-209.us-west-2.compute.internal uid: f2925fcf-2699-4db4-817a-acd3e89c48dd resourceVersion: "24777" uid: 039a938f-3925-4e7b-8a8a-2a6ccddf1fd2 spec: sourcePod: network-check-source-6f78d59f99-5ptxj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T12:57:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.587812ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:27:13Z" - latency: 1.768095ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T13:27:13Z" - latency: 1.303535ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:26:13Z" - latency: 1.837413ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T13:26:13Z" - latency: 1.036907ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:25:13Z" - latency: 2.736439ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T13:25:13Z" - latency: 995.471µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:24:13Z" - latency: 2.035019ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T13:24:13Z" - latency: 875.327µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T13:23:13Z" - latency: 2.459937ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T13:23:13Z" kind: List metadata: resourceVersion: ""