apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:31:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-252-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-252.us-east-2.compute.internal uid: 6c0ff36a-9f69-4cfb-8984-83bc3bb4e25e resourceVersion: "18826" uid: 7e6aec1b-a11c-4f23-b88d-b5c88c7cb5e4 spec: sourcePod: network-check-source-6f78d59f99-pvkk4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-31T00:38:48Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 988.836µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:52:48Z" - latency: 1.123481ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:48Z" - latency: 869.807µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:50:48Z" - latency: 1.188413ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:49:48Z" - latency: 1.2857ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:48:48Z" - latency: 1.133594ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:47:48Z" - latency: 1.265242ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:46:48Z" - latency: 1.070045ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:45:48Z" - latency: 946.846µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:44:48Z" - latency: 1.461917ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:43:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:31:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-252-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-252.us-east-2.compute.internal uid: 6c0ff36a-9f69-4cfb-8984-83bc3bb4e25e resourceVersion: "20340" uid: 1969510d-1dec-4096-aae5-f3c8015e33ff spec: sourcePod: network-check-source-6f78d59f99-pvkk4 targetEndpoint: afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T00:37:48Z" message: 'load-balancer-api-external: tcp connection to afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.466196ms message: 'load-balancer-api-external: tcp connection to afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:55:48Z" - latency: 9.138907ms message: 'load-balancer-api-external: resolved host name afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:55:48Z" - latency: 5.228328ms message: 'load-balancer-api-external: tcp connection to afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:54:48Z" - latency: 8.459405ms message: 'load-balancer-api-external: resolved host name afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:54:48Z" - latency: 5.033288ms message: 'load-balancer-api-external: tcp connection to afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:53:48Z" - latency: 7.959212ms message: 'load-balancer-api-external: resolved host name afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:53:48Z" - latency: 5.307578ms message: 'load-balancer-api-external: tcp connection to afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:52:48Z" - latency: 8.985222ms message: 'load-balancer-api-external: resolved host name afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:52:48Z" - latency: 4.735687ms message: 'load-balancer-api-external: tcp connection to afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:48Z" - latency: 9.274316ms message: 'load-balancer-api-external: resolved host name afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:51:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:31:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-252-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-252.us-east-2.compute.internal uid: 6c0ff36a-9f69-4cfb-8984-83bc3bb4e25e resourceVersion: "20339" uid: c9fbb659-69b0-4921-a3ee-6414957b6c8e spec: sourcePod: network-check-source-6f78d59f99-pvkk4 targetEndpoint: afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-31T00:37:48Z" message: 'load-balancer-api-internal: tcp connection to afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.881165ms message: 'load-balancer-api-internal: tcp connection to afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:55:48Z" - latency: 9.098316ms message: 'load-balancer-api-internal: resolved host name afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:55:48Z" - latency: 5.245382ms message: 'load-balancer-api-internal: tcp connection to afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:54:48Z" - latency: 8.422169ms message: 'load-balancer-api-internal: resolved host name afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:54:48Z" - latency: 4.671164ms message: 'load-balancer-api-internal: tcp connection to afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:53:48Z" - latency: 7.938272ms message: 'load-balancer-api-internal: resolved host name afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:53:48Z" - latency: 5.271757ms message: 'load-balancer-api-internal: tcp connection to afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:52:48Z" - latency: 8.906548ms message: 'load-balancer-api-internal: resolved host name afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:52:48Z" - latency: 4.884201ms message: 'load-balancer-api-internal: tcp connection to afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:48Z" - latency: 9.187122ms message: 'load-balancer-api-internal: resolved host name afe38d44af1df49419ac0bf49162ee29-e283946b6dd9ec29.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-31T00:51:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:31:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-252-to-network-check-target-ip-10-0-134-145 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-252.us-east-2.compute.internal uid: 6c0ff36a-9f69-4cfb-8984-83bc3bb4e25e resourceVersion: "18825" uid: fbc5dcc9-3bfc-4223-a3d9-f45c418c32cd spec: sourcePod: network-check-source-6f78d59f99-pvkk4 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-31T00:38:48Z" message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.014983ms message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:52:48Z" - latency: 2.077143ms message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:48Z" - latency: 2.164997ms message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:50:48Z" - latency: 2.328667ms message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:49:48Z" - latency: 2.186315ms message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:48:48Z" - latency: 2.366895ms message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:47:48Z" - latency: 2.373204ms message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:46:48Z" - latency: 2.271139ms message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:45:48Z" - latency: 1.820616ms message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:44:48Z" - latency: 2.709774ms message: 'network-check-target-ip-10-0-134-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:43:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:31:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-252-to-network-check-target-ip-10-0-134-252 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-252.us-east-2.compute.internal uid: 6c0ff36a-9f69-4cfb-8984-83bc3bb4e25e resourceVersion: "18824" uid: 5da1798d-b400-4b5a-b7e4-bbb6a8869c15 spec: sourcePod: network-check-source-6f78d59f99-pvkk4 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T00:38:48Z" message: 'network-check-target-ip-10-0-134-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.686016ms message: 'network-check-target-ip-10-0-134-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:52:48Z" - latency: 1.902255ms message: 'network-check-target-ip-10-0-134-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:48Z" - latency: 2.060143ms message: 'network-check-target-ip-10-0-134-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:50:48Z" - latency: 2.001286ms message: 'network-check-target-ip-10-0-134-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:49:48Z" - latency: 1.904908ms message: 'network-check-target-ip-10-0-134-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:48:48Z" - latency: 1.975572ms message: 'network-check-target-ip-10-0-134-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:47:48Z" - latency: 2.080517ms message: 'network-check-target-ip-10-0-134-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:46:48Z" - latency: 1.935014ms message: 'network-check-target-ip-10-0-134-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:45:48Z" - latency: 1.988131ms message: 'network-check-target-ip-10-0-134-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:44:48Z" - latency: 2.116961ms message: 'network-check-target-ip-10-0-134-252: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:43:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:31:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-252-to-network-check-target-ip-10-0-143-252 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-252.us-east-2.compute.internal uid: 6c0ff36a-9f69-4cfb-8984-83bc3bb4e25e resourceVersion: "18823" uid: e6d6cc44-7251-4f94-817d-1193fa5bf39d spec: sourcePod: network-check-source-6f78d59f99-pvkk4 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-31T00:38:48Z" message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.570303ms message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:52:48Z" - latency: 831.646µs message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:48Z" - latency: 877.745µs message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:50:48Z" - latency: 988.29µs message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:49:48Z" - latency: 1.355154ms message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:48:48Z" - latency: 1.293222ms message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:47:48Z" - latency: 929.643µs message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:46:48Z" - latency: 886.407µs message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:45:48Z" - latency: 861.468µs message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:44:48Z" - latency: 1.508113ms message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:43:48Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-31T00:31:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-252-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-252.us-east-2.compute.internal uid: 6c0ff36a-9f69-4cfb-8984-83bc3bb4e25e resourceVersion: "20338" uid: dd72625f-a698-4ae5-9393-c50d6f4314a6 spec: sourcePod: network-check-source-6f78d59f99-pvkk4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-31T00:37:48Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 843.605µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:55:48Z" - latency: 2.645324ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:55:48Z" - latency: 1.1383ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:54:48Z" - latency: 1.746167ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:54:48Z" - latency: 862.577µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:53:48Z" - latency: 1.767864ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:53:48Z" - latency: 948.053µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:52:48Z" - latency: 1.728668ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:52:48Z" - latency: 732.374µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-31T00:51:48Z" - latency: 2.367856ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-31T00:51:48Z" kind: List metadata: resourceVersion: ""