apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:20:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-50-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-50.us-west-2.compute.internal uid: 2f2fc63f-beae-4dca-9cf0-a551102b4f4c resourceVersion: "49986" uid: 33a4e644-33d5-4e59-9357-b34c34f03284 spec: sourcePod: network-check-source-6f78d59f99-7lkrx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-04T03:27:46Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.831065ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:48:46Z" - latency: 997.552µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:47:46Z" - latency: 1.223439ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:46:46Z" - latency: 1.140104ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:45:46Z" - latency: 953.001µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:44:46Z" - latency: 1.691804ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:43:46Z" - latency: 2.477798ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:42:46Z" - latency: 1.337456ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:41:46Z" - latency: 1.740863ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:40:46Z" - latency: 1.397457ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:39:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:20:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-50-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-50.us-west-2.compute.internal uid: 2f2fc63f-beae-4dca-9cf0-a551102b4f4c resourceVersion: "52731" uid: 77acd973-40a6-40b4-8dbf-5594a97edab8 spec: sourcePod: network-check-source-6f78d59f99-7lkrx targetEndpoint: acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T03:26:46Z" message: 'load-balancer-api-external: tcp connection to acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.3891ms message: 'load-balancer-api-external: tcp connection to acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:50:46Z" - latency: 6.925052ms message: 'load-balancer-api-external: resolved host name acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:50:46Z" - latency: 56.629442ms message: 'load-balancer-api-external: tcp connection to acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:49:46Z" - latency: 8.246073ms message: 'load-balancer-api-external: resolved host name acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:49:46Z" - latency: 55.685684ms message: 'load-balancer-api-external: tcp connection to acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:48:46Z" - latency: 6.972402ms message: 'load-balancer-api-external: resolved host name acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:48:46Z" - latency: 50.789003ms message: 'load-balancer-api-external: tcp connection to acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:47:46Z" - latency: 6.790461ms message: 'load-balancer-api-external: resolved host name acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:47:46Z" - latency: 50.93196ms message: 'load-balancer-api-external: tcp connection to acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:46:46Z" - latency: 6.527548ms message: 'load-balancer-api-external: resolved host name acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:46:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:20:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-50-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-50.us-west-2.compute.internal uid: 2f2fc63f-beae-4dca-9cf0-a551102b4f4c resourceVersion: "52732" uid: 9adbc8ac-fd6c-4d61-9e8d-08d293da5883 spec: sourcePod: network-check-source-6f78d59f99-7lkrx targetEndpoint: acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-04T03:26:49Z" message: 'load-balancer-api-internal: tcp connection to acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.493774ms message: 'load-balancer-api-internal: tcp connection to acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:50:46Z" - latency: 7.000387ms message: 'load-balancer-api-internal: resolved host name acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:50:46Z" - latency: 49.676746ms message: 'load-balancer-api-internal: tcp connection to acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:49:46Z" - latency: 8.298763ms message: 'load-balancer-api-internal: resolved host name acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:49:46Z" - latency: 55.34005ms message: 'load-balancer-api-internal: tcp connection to acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:48:46Z" - latency: 7.001524ms message: 'load-balancer-api-internal: resolved host name acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:48:46Z" - latency: 54.185204ms message: 'load-balancer-api-internal: tcp connection to acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:47:46Z" - latency: 6.876883ms message: 'load-balancer-api-internal: resolved host name acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:47:46Z" - latency: 53.945439ms message: 'load-balancer-api-internal: tcp connection to acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:46:46Z" - latency: 6.590555ms message: 'load-balancer-api-internal: resolved host name acd60e97cb07342d6a02bc86b8f04d90-7f8ad830d0f07e24.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-04T03:46:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:20:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-50-to-network-check-target-ip-10-0-128-50 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-50.us-west-2.compute.internal uid: 2f2fc63f-beae-4dca-9cf0-a551102b4f4c resourceVersion: "49982" uid: c86030ab-162c-4f1f-bcbe-92861071a1fb spec: sourcePod: network-check-source-6f78d59f99-7lkrx targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-04T03:27:46Z" message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 906.665µs message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:48:46Z" - latency: 974.868µs message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:47:46Z" - latency: 913.898µs message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:46:46Z" - latency: 1.030407ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:45:46Z" - latency: 897.883µs message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:44:46Z" - latency: 1.839873ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:43:46Z" - latency: 2.919518ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:42:46Z" - latency: 1.34402ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:41:46Z" - latency: 1.385168ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:40:46Z" - latency: 1.626586ms message: 'network-check-target-ip-10-0-128-50: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:39:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:20:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-50-to-network-check-target-ip-10-0-133-201 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-50.us-west-2.compute.internal uid: 2f2fc63f-beae-4dca-9cf0-a551102b4f4c resourceVersion: "49983" uid: d7d374a4-0305-40d0-a439-139c2f5a0938 spec: sourcePod: network-check-source-6f78d59f99-7lkrx targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-04T03:27:46Z" message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.346884ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:48:46Z" - latency: 2.044496ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:47:46Z" - latency: 1.916744ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:46:46Z" - latency: 2.280509ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:45:46Z" - latency: 2.096971ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:44:46Z" - latency: 2.265232ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:43:46Z" - latency: 3.770141ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:42:46Z" - latency: 2.718867ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:41:46Z" - latency: 2.467932ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:40:46Z" - latency: 2.237213ms message: 'network-check-target-ip-10-0-133-201: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:39:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:20:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-50-to-network-check-target-ip-10-0-135-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-50.us-west-2.compute.internal uid: 2f2fc63f-beae-4dca-9cf0-a551102b4f4c resourceVersion: "49984" uid: 3acf1213-2561-416f-b863-418455bb6cad spec: sourcePod: network-check-source-6f78d59f99-7lkrx targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-04T03:27:46Z" message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.418516ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:48:46Z" - latency: 2.423717ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:47:46Z" - latency: 2.263085ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:46:46Z" - latency: 2.379854ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:45:46Z" - latency: 2.370927ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:44:46Z" - latency: 2.546793ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:43:46Z" - latency: 3.31764ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:42:46Z" - latency: 2.642737ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:41:46Z" - latency: 2.33202ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:40:46Z" - latency: 2.27933ms message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:39:46Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-04T03:20:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-50-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-50.us-west-2.compute.internal uid: 2f2fc63f-beae-4dca-9cf0-a551102b4f4c resourceVersion: "52729" uid: 81565287-17ba-4534-be3f-19566f2026c3 spec: sourcePod: network-check-source-6f78d59f99-7lkrx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-04T03:26:46Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 949.394µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:50:46Z" - latency: 1.987137ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T03:50:46Z" - latency: 1.023831ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:49:46Z" - latency: 1.700938ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T03:49:46Z" - latency: 1.192518ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:48:46Z" - latency: 1.818614ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T03:48:46Z" - latency: 1.128447ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:47:46Z" - latency: 1.973363ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T03:47:46Z" - latency: 935.738µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-04T03:46:46Z" - latency: 1.793623ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-04T03:46:46Z" kind: List metadata: resourceVersion: ""