apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T17:46:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-108-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-108.us-west-2.compute.internal uid: f1bd8db0-d4a8-42e5-baa6-9573ff7d6e4c resourceVersion: "90611" uid: 87ec1201-302c-4b59-a9f6-a4d0c5e7fef4 spec: sourcePod: network-check-source-6f78d59f99-nwhnp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T17:53: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.085564ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:42:36Z" - latency: 1.262483ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:41:36Z" - latency: 955.971µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:40:36Z" - latency: 1.497244ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:39:36Z" - latency: 1.400906ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:38:36Z" - latency: 4.868742ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:37:36Z" - latency: 1.808443ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:36:36Z" - latency: 1.439341ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:35:36Z" - latency: 1.271202ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:34:36Z" - latency: 1.651522ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:33:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T17:46:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-108-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-108.us-west-2.compute.internal uid: f1bd8db0-d4a8-42e5-baa6-9573ff7d6e4c resourceVersion: "89543" uid: 6afbcbb4-d504-4ea9-bee2-c26872f679dd spec: sourcePod: network-check-source-6f78d59f99-nwhnp targetEndpoint: ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T17:52:36Z" message: 'load-balancer-api-external: tcp connection to ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 55.43402ms message: 'load-balancer-api-external: tcp connection to ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:40:36Z" - latency: 6.849557ms message: 'load-balancer-api-external: resolved host name ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:40:36Z" - latency: 54.485726ms message: 'load-balancer-api-external: tcp connection to ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:39:36Z" - latency: 7.042528ms message: 'load-balancer-api-external: resolved host name ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:39:36Z" - latency: 58.588635ms message: 'load-balancer-api-external: tcp connection to ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:38:36Z" - latency: 7.390154ms message: 'load-balancer-api-external: resolved host name ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:38:36Z" - latency: 53.637274ms message: 'load-balancer-api-external: tcp connection to ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:37:36Z" - latency: 19.872835ms message: 'load-balancer-api-external: resolved host name ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:37:36Z" - latency: 54.66902ms message: 'load-balancer-api-external: tcp connection to ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:36:36Z" - latency: 6.993193ms message: 'load-balancer-api-external: resolved host name ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:36:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T17:46:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-108-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-108.us-west-2.compute.internal uid: f1bd8db0-d4a8-42e5-baa6-9573ff7d6e4c resourceVersion: "89541" uid: 999a4c52-f85c-4ab6-95d3-c3a930ac4a24 spec: sourcePod: network-check-source-6f78d59f99-nwhnp targetEndpoint: ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T17:52:36Z" message: 'load-balancer-api-internal: tcp connection to ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 50.276507ms message: 'load-balancer-api-internal: tcp connection to ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:40:36Z" - latency: 6.830125ms message: 'load-balancer-api-internal: resolved host name ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:40:36Z" - latency: 55.301566ms message: 'load-balancer-api-internal: tcp connection to ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:39:36Z" - latency: 6.948425ms message: 'load-balancer-api-internal: resolved host name ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:39:36Z" - latency: 57.203562ms message: 'load-balancer-api-internal: tcp connection to ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:38:36Z" - latency: 7.438195ms message: 'load-balancer-api-internal: resolved host name ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:38:36Z" - latency: 53.058212ms message: 'load-balancer-api-internal: tcp connection to ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:37:36Z" - latency: 20.394502ms message: 'load-balancer-api-internal: resolved host name ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:37:36Z" - latency: 56.888407ms message: 'load-balancer-api-internal: tcp connection to ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:36:36Z" - latency: 7.001289ms message: 'load-balancer-api-internal: resolved host name ad185ca6b177f4c7286538684ef3f4ce-d7e05c9bd6f41af3.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:36:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T17:46:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-108-to-network-check-target-ip-10-0-128-204 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-108.us-west-2.compute.internal uid: f1bd8db0-d4a8-42e5-baa6-9573ff7d6e4c resourceVersion: "90608" uid: c14d1877-0090-4507-903d-3e3e90afe628 spec: sourcePod: network-check-source-6f78d59f99-nwhnp targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T17:53:36Z" message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 741.801µs message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:42:36Z" - latency: 782.395µs message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:41:36Z" - latency: 754.8µs message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:40:36Z" - latency: 2.093802ms message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:39:36Z" - latency: 2.198447ms message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:38:36Z" - latency: 9.056864ms message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:37:36Z" - latency: 791.815µs message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:36:36Z" - latency: 1.945572ms message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:35:36Z" - latency: 2.250438ms message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:34:36Z" - latency: 759.249µs message: 'network-check-target-ip-10-0-128-204: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:33:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T17:46:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-108-to-network-check-target-ip-10-0-137-164 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-108.us-west-2.compute.internal uid: f1bd8db0-d4a8-42e5-baa6-9573ff7d6e4c resourceVersion: "90609" uid: 8a89fffd-81fa-4fd8-ac34-82f33a171016 spec: sourcePod: network-check-source-6f78d59f99-nwhnp targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T17:53:36Z" message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.782726ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:42:36Z" - latency: 1.751791ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:41:36Z" - latency: 1.69589ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:40:36Z" - latency: 597.375µs message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:39:36Z" - latency: 717.71µs message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:38:36Z" - latency: 8.725651ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:37:36Z" - latency: 1.849223ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:36:36Z" - latency: 628.871µs message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:35:36Z" - latency: 1.827537ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:34:36Z" - latency: 1.90426ms message: 'network-check-target-ip-10-0-137-164: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:33:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T17:46:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-108-to-network-check-target-ip-10-0-141-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-108.us-west-2.compute.internal uid: f1bd8db0-d4a8-42e5-baa6-9573ff7d6e4c resourceVersion: "90607" uid: 00bb61fa-aa79-491a-8b47-e298e549657a spec: sourcePod: network-check-source-6f78d59f99-nwhnp targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T17:53:36Z" message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.189301ms message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:42:36Z" - latency: 1.556302ms message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:41:36Z" - latency: 1.093119ms message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:40:36Z" - latency: 1.222522ms message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:39:36Z" - latency: 1.346466ms message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:38:36Z" - latency: 4.699643ms message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:37:36Z" - latency: 1.12674ms message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:36:36Z" - latency: 1.67475ms message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:35:36Z" - latency: 1.459637ms message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:34:36Z" - latency: 1.902082ms message: 'network-check-target-ip-10-0-141-108: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:33:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T17:46:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-108-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-108.us-west-2.compute.internal uid: f1bd8db0-d4a8-42e5-baa6-9573ff7d6e4c resourceVersion: "89540" uid: 7c915e82-a7d2-4987-99db-d59a9ae0c445 spec: sourcePod: network-check-source-6f78d59f99-nwhnp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T17:52:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.182305ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:40:36Z" - latency: 1.973986ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T18:40:36Z" - latency: 2.061389ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:39:36Z" - latency: 2.000594ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T18:39:36Z" - latency: 2.314453ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:38:36Z" - latency: 1.986777ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T18:38:36Z" - latency: 1.55162ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:37:36Z" - latency: 13.756382ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T18:37:36Z" - latency: 2.520966ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:36:36Z" - latency: 1.997053ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T18:36:36Z" kind: List metadata: resourceVersion: ""