apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:00:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-246-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-246.ec2.internal uid: 383a78b0-b9e7-4278-96be-df69ea9a3dee resourceVersion: "180741" uid: 00e6df74-cbdf-44f6-b7cf-7c05ba7471a0 spec: sourcePod: network-check-source-6f78d59f99-rrfpm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T18:07:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.482234ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:17:19Z" - latency: 840.764µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:16:19Z" - latency: 1.355943ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:15:19Z" - latency: 1.339048ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:14:19Z" - latency: 13.882484ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:13:19Z" - latency: 1.547301ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:12:19Z" - latency: 1.592876ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:11:19Z" - latency: 991.229µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:10:19Z" - latency: 980.425µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:09:19Z" - latency: 1.594026ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:08:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:00:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-246-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-246.ec2.internal uid: 383a78b0-b9e7-4278-96be-df69ea9a3dee resourceVersion: "170248" uid: fdd4d659-2cba-48e8-9c91-84071f0249d5 spec: sourcePod: network-check-source-6f78d59f99-rrfpm targetEndpoint: a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T18:06:19Z" message: 'load-balancer-api-external: tcp connection to a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.237748ms message: 'load-balancer-api-external: tcp connection to a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:12:19Z" - latency: 10.355031ms message: 'load-balancer-api-external: resolved host name a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:12:19Z" - latency: 17.994479ms message: 'load-balancer-api-external: tcp connection to a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:11:19Z" - latency: 9.465354ms message: 'load-balancer-api-external: resolved host name a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:11:19Z" - latency: 18.494411ms message: 'load-balancer-api-external: tcp connection to a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:10:19Z" - latency: 9.151737ms message: 'load-balancer-api-external: resolved host name a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:10:19Z" - latency: 18.168684ms message: 'load-balancer-api-external: tcp connection to a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:09:19Z" - latency: 7.42825ms message: 'load-balancer-api-external: resolved host name a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:09:19Z" - latency: 16.377231ms message: 'load-balancer-api-external: tcp connection to a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:08:19Z" - latency: 7.970114ms message: 'load-balancer-api-external: resolved host name a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:08:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:00:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-246-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-246.ec2.internal uid: 383a78b0-b9e7-4278-96be-df69ea9a3dee resourceVersion: "170249" uid: 51a18f0c-cca9-492d-8ebe-ce41a79204c5 spec: sourcePod: network-check-source-6f78d59f99-rrfpm targetEndpoint: a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T18:06:19Z" message: 'load-balancer-api-internal: tcp connection to a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.086684ms message: 'load-balancer-api-internal: tcp connection to a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:12:19Z" - latency: 10.449646ms message: 'load-balancer-api-internal: resolved host name a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:12:19Z" - latency: 18.062796ms message: 'load-balancer-api-internal: tcp connection to a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:11:19Z" - latency: 9.498628ms message: 'load-balancer-api-internal: resolved host name a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:11:19Z" - latency: 19.103365ms message: 'load-balancer-api-internal: tcp connection to a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:10:19Z" - latency: 9.254437ms message: 'load-balancer-api-internal: resolved host name a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:10:19Z" - latency: 16.521543ms message: 'load-balancer-api-internal: tcp connection to a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:09:19Z" - latency: 7.448111ms message: 'load-balancer-api-internal: resolved host name a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:09:19Z" - latency: 15.379605ms message: 'load-balancer-api-internal: tcp connection to a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:08:19Z" - latency: 7.956413ms message: 'load-balancer-api-internal: resolved host name a8a5d1ce0b3ef42df9f020855898109b-5d3174c2d71d53cd.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:08:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:00:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-246-to-network-check-target-ip-10-0-128-246 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-246.ec2.internal uid: 383a78b0-b9e7-4278-96be-df69ea9a3dee resourceVersion: "180737" uid: 2d583961-e117-4b9b-ae34-6d95933a9a2b spec: sourcePod: network-check-source-6f78d59f99-rrfpm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:07:19Z" message: 'network-check-target-ip-10-0-128-246: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.120748ms message: 'network-check-target-ip-10-0-128-246: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:17:19Z" - latency: 924.421µs message: 'network-check-target-ip-10-0-128-246: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:16:19Z" - latency: 1.42772ms message: 'network-check-target-ip-10-0-128-246: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:15:19Z" - latency: 997.347µs message: 'network-check-target-ip-10-0-128-246: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:14:19Z" - latency: 4.006833ms message: 'network-check-target-ip-10-0-128-246: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:13:19Z" - latency: 2.137432ms message: 'network-check-target-ip-10-0-128-246: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:12:19Z" - latency: 1.428818ms message: 'network-check-target-ip-10-0-128-246: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:11:19Z" - latency: 2.513405ms message: 'network-check-target-ip-10-0-128-246: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:10:19Z" - latency: 1.006847ms message: 'network-check-target-ip-10-0-128-246: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:09:19Z" - latency: 1.239079ms message: 'network-check-target-ip-10-0-128-246: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:08:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:00:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-246-to-network-check-target-ip-10-0-133-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-246.ec2.internal uid: 383a78b0-b9e7-4278-96be-df69ea9a3dee resourceVersion: "180738" uid: b611f207-cd63-445c-acc0-68dea27a8264 spec: sourcePod: network-check-source-6f78d59f99-rrfpm targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:07:19Z" message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.919125ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:17:19Z" - latency: 1.775335ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:16:19Z" - latency: 2.508641ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:15:19Z" - latency: 2.34077ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:14:19Z" - latency: 5.593801ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:13:19Z" - latency: 2.765979ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:12:19Z" - latency: 2.219724ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:11:19Z" - latency: 3.000491ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:10:19Z" - latency: 2.628135ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:09:19Z" - latency: 2.938653ms message: 'network-check-target-ip-10-0-133-124: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:08:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:00:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-246-to-network-check-target-ip-10-0-138-176 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-246.ec2.internal uid: 383a78b0-b9e7-4278-96be-df69ea9a3dee resourceVersion: "180739" uid: fae45627-3cd0-4938-857b-72ebb789ec5f spec: sourcePod: network-check-source-6f78d59f99-rrfpm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:07:19Z" message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.158923ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:17:19Z" - latency: 2.051578ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:16:19Z" - latency: 2.441055ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:15:19Z" - latency: 2.26219ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:14:19Z" - latency: 13.75418ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:13:19Z" - latency: 4.676416ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:12:19Z" - latency: 2.690462ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:11:19Z" - latency: 2.914949ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:10:19Z" - latency: 2.8627ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:09:19Z" - latency: 2.335803ms message: 'network-check-target-ip-10-0-138-176: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:08:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:00:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-246-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-246.ec2.internal uid: 383a78b0-b9e7-4278-96be-df69ea9a3dee resourceVersion: "170246" uid: f6389d86-8ecf-47bf-b6dd-47e973c3c469 spec: sourcePod: network-check-source-6f78d59f99-rrfpm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T18:06:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.251702ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:12:19Z" - latency: 2.356348ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:12:19Z" - latency: 989.477µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:11:19Z" - latency: 2.097424ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:11:19Z" - latency: 1.754165ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:10:19Z" - latency: 3.081248ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:10:19Z" - latency: 1.708157ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:09:19Z" - latency: 2.052186ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:09:19Z" - latency: 1.456434ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:08:19Z" - latency: 2.03929ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:08:19Z" kind: List metadata: resourceVersion: ""