apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:18:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-184-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-184.us-west-1.compute.internal uid: cfe58540-48f2-42ec-aa9b-c59546bb4bab resourceVersion: "50322" uid: 49e22dc4-ce0a-431a-83ae-b4eb1a0ea3b3 spec: sourcePod: network-check-source-6f78d59f99-27kkj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-04T03:25:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.094727ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:46:38Z" - latency: 865.997µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:45:38Z" - latency: 1.996719ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:44:38Z" - latency: 1.671435ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:43:38Z" - latency: 1.335406ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:42:38Z" - latency: 1.498831ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:41:38Z" - latency: 1.182219ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:40:38Z" - latency: 5.267834ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:39:38Z" - latency: 1.488252ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:38:38Z" - latency: 1.409581ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:37:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:18:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-184-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-184.us-west-1.compute.internal uid: cfe58540-48f2-42ec-aa9b-c59546bb4bab resourceVersion: "53049" uid: 830dcea4-feff-4dae-b297-37c3983f6c7b spec: sourcePod: network-check-source-6f78d59f99-27kkj targetEndpoint: a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T03:24:38Z" message: 'load-balancer-api-external: tcp connection to a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.533339ms message: 'load-balancer-api-external: tcp connection to a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:48:38Z" - latency: 6.669849ms message: 'load-balancer-api-external: resolved host name a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:48:38Z" - latency: 3.387556589s message: 'load-balancer-api-external: tcp connection to a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:47:38Z" - latency: 6.304772ms message: 'load-balancer-api-external: resolved host name a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:47:38Z" - latency: 54.126575ms message: 'load-balancer-api-external: tcp connection to a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:46:38Z" - latency: 7.022017ms message: 'load-balancer-api-external: resolved host name a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:46:38Z" - latency: 54.020701ms message: 'load-balancer-api-external: tcp connection to a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:45:38Z" - latency: 7.437882ms message: 'load-balancer-api-external: resolved host name a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:45:38Z" - latency: 54.61392ms message: 'load-balancer-api-external: tcp connection to a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:44:38Z" - latency: 7.579167ms message: 'load-balancer-api-external: resolved host name a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:44:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:18:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-184-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-184.us-west-1.compute.internal uid: cfe58540-48f2-42ec-aa9b-c59546bb4bab resourceVersion: "53050" uid: 0aa7bb51-4b12-406c-a42f-1485cafe8175 spec: sourcePod: network-check-source-6f78d59f99-27kkj targetEndpoint: a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T03:24:38Z" message: 'load-balancer-api-internal: tcp connection to a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.524454ms message: 'load-balancer-api-internal: tcp connection to a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:48:38Z" - latency: 6.638049ms message: 'load-balancer-api-internal: resolved host name a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:48:38Z" - latency: 55.970524ms message: 'load-balancer-api-internal: tcp connection to a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:47:38Z" - latency: 6.268304ms message: 'load-balancer-api-internal: resolved host name a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:47:38Z" - latency: 54.157807ms message: 'load-balancer-api-internal: tcp connection to a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:46:38Z" - latency: 7.002478ms message: 'load-balancer-api-internal: resolved host name a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:46:38Z" - latency: 54.13197ms message: 'load-balancer-api-internal: tcp connection to a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:45:38Z" - latency: 7.386855ms message: 'load-balancer-api-internal: resolved host name a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:45:38Z" - latency: 54.887019ms message: 'load-balancer-api-internal: tcp connection to a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:44:38Z" - latency: 7.474517ms message: 'load-balancer-api-internal: resolved host name a0eed642b5924453b9c4f38476315c56-78f2aa2176e6b7a4.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:44:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:18:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-184-to-network-check-target-ip-10-0-132-184 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-184.us-west-1.compute.internal uid: cfe58540-48f2-42ec-aa9b-c59546bb4bab resourceVersion: "50315" uid: bc7fee86-b6cf-4cb6-9369-7c7e0975c782 spec: sourcePod: network-check-source-6f78d59f99-27kkj targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-04T03:25:38Z" message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 943.003µs message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:46:38Z" - latency: 1.617877ms message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:45:38Z" - latency: 2.765167ms message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:44:38Z" - latency: 1.076893ms message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:43:38Z" - latency: 1.592892ms message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:42:38Z" - latency: 1.16546ms message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:41:38Z" - latency: 1.375574ms message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:40:38Z" - latency: 6.107266ms message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:39:38Z" - latency: 1.759521ms message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:38:38Z" - latency: 1.10039ms message: 'network-check-target-ip-10-0-132-184: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:37:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:18:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-184-to-network-check-target-ip-10-0-133-235 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-184.us-west-1.compute.internal uid: cfe58540-48f2-42ec-aa9b-c59546bb4bab resourceVersion: "50316" uid: a704d50c-02ca-4a73-a900-230884a40a5d spec: sourcePod: network-check-source-6f78d59f99-27kkj targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-04T03:25:38Z" message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.096766ms message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:46:38Z" - latency: 2.312417ms message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:45:38Z" - latency: 2.538893ms message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:44:38Z" - latency: 2.367225ms message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:43:38Z" - latency: 2.428939ms message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:42:38Z" - latency: 2.2867ms message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:41:38Z" - latency: 3.470184ms message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:40:38Z" - latency: 4.4876ms message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:39:38Z" - latency: 2.485995ms message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:38:38Z" - latency: 2.021569ms message: 'network-check-target-ip-10-0-133-235: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:37:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:18:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-184-to-network-check-target-ip-10-0-133-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-184.us-west-1.compute.internal uid: cfe58540-48f2-42ec-aa9b-c59546bb4bab resourceVersion: "50319" uid: 62fc0dd8-359f-4ed3-b0db-51236bd124c9 spec: sourcePod: network-check-source-6f78d59f99-27kkj targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-04T03:25:38Z" message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.479108ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:46:38Z" - latency: 2.978427ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:45:38Z" - latency: 2.316255ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:44:38Z" - latency: 2.039953ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:43:38Z" - latency: 2.597786ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:42:38Z" - latency: 2.316479ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:41:38Z" - latency: 2.128986ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:40:38Z" - latency: 4.761233ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:39:38Z" - latency: 2.625335ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:38:38Z" - latency: 2.606924ms message: 'network-check-target-ip-10-0-133-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:37:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:18:38Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-184-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-184.us-west-1.compute.internal uid: cfe58540-48f2-42ec-aa9b-c59546bb4bab resourceVersion: "53048" uid: 0e4f47b1-fa52-4bfe-9986-8fee15fa693f spec: sourcePod: network-check-source-6f78d59f99-27kkj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-04T03:24:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 964.898µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:48:38Z" - latency: 2.231349ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T03:48:38Z" - latency: 990.645µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:47:38Z" - latency: 1.792511ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T03:47:38Z" - latency: 857.764µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:46:38Z" - latency: 2.521ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T03:46:38Z" - latency: 921.724µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:45:38Z" - latency: 1.92198ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T03:45:38Z" - latency: 1.330549ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:44:38Z" - latency: 2.685007ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T03:44:38Z" kind: List metadata: resourceVersion: ""