apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:24:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-102-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-102.ec2.internal uid: 2830d1ae-d329-4681-a038-e4000aee7a7e resourceVersion: "27383" uid: dc61d3fa-68bb-42f9-8a29-dbc2ec75925e spec: sourcePod: network-check-source-7d88cb55d8-4jlnf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-24T15:31:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.03282ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:38:22Z" - latency: 1.020257ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:37:22Z" - latency: 869.499µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:36:22Z" - latency: 1.101058ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:35:22Z" - latency: 881.159µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:34:22Z" - latency: 996.968µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:33:22Z" - latency: 991.517µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:32:22Z" - latency: 1.956565ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:31:22Z" - latency: 1.067029ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:30:22Z" - latency: 793.752µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:29:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:24:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-102-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-102.ec2.internal uid: 2830d1ae-d329-4681-a038-e4000aee7a7e resourceVersion: "26178" uid: c0121749-523e-47d5-a2be-0c6a4eca3c83 spec: sourcePod: network-check-source-7d88cb55d8-4jlnf targetEndpoint: a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T15:30:22Z" message: 'load-balancer-api-external: tcp connection to a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.197011ms message: 'load-balancer-api-external: tcp connection to a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:36:22Z" - latency: 8.592038ms message: 'load-balancer-api-external: resolved host name a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:36:22Z" - latency: 4.26881ms message: 'load-balancer-api-external: tcp connection to a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:35:22Z" - latency: 8.745686ms message: 'load-balancer-api-external: resolved host name a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:35:22Z" - latency: 5.96753ms message: 'load-balancer-api-external: tcp connection to a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:34:22Z" - latency: 7.774347ms message: 'load-balancer-api-external: resolved host name a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:34:22Z" - latency: 4.427968ms message: 'load-balancer-api-external: tcp connection to a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:33:22Z" - latency: 8.28717ms message: 'load-balancer-api-external: resolved host name a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:33:22Z" - latency: 4.960474ms message: 'load-balancer-api-external: tcp connection to a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:32:22Z" - latency: 8.63376ms message: 'load-balancer-api-external: resolved host name a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:32:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:24:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-102-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-102.ec2.internal uid: 2830d1ae-d329-4681-a038-e4000aee7a7e resourceVersion: "26179" uid: 54fe762d-9548-453f-beb9-392046373ae8 spec: sourcePod: network-check-source-7d88cb55d8-4jlnf targetEndpoint: a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-24T15:30:22Z" message: 'load-balancer-api-internal: tcp connection to a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.998324ms message: 'load-balancer-api-internal: tcp connection to a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:36:22Z" - latency: 8.619287ms message: 'load-balancer-api-internal: resolved host name a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:36:22Z" - latency: 4.296277ms message: 'load-balancer-api-internal: tcp connection to a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:35:22Z" - latency: 8.874655ms message: 'load-balancer-api-internal: resolved host name a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:35:22Z" - latency: 3.199566ms message: 'load-balancer-api-internal: tcp connection to a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:34:22Z" - latency: 7.691022ms message: 'load-balancer-api-internal: resolved host name a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:34:22Z" - latency: 4.256248ms message: 'load-balancer-api-internal: tcp connection to a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:33:22Z" - latency: 8.402898ms message: 'load-balancer-api-internal: resolved host name a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:33:22Z" - latency: 4.948628ms message: 'load-balancer-api-internal: tcp connection to a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:32:22Z" - latency: 8.68469ms message: 'load-balancer-api-internal: resolved host name a63e419d0c5554cfcaf951c5e3d0fc4e-441466461a1d1427.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-24T15:32:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:24:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-102-to-network-check-target-ip-10-0-133-102 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-102.ec2.internal uid: 2830d1ae-d329-4681-a038-e4000aee7a7e resourceVersion: "27380" uid: c50dd3e8-d5ed-41a5-b046-e392c3058ff2 spec: sourcePod: network-check-source-7d88cb55d8-4jlnf targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T15:31:22Z" message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.144072ms message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:38:22Z" - latency: 1.471665ms message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:37:22Z" - latency: 780.446µs message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:36:22Z" - latency: 897.037µs message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:35:22Z" - latency: 890.5µs message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:34:22Z" - latency: 1.342486ms message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:33:22Z" - latency: 865.71µs message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:32:22Z" - latency: 1.058584ms message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:31:22Z" - latency: 925.048µs message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:30:22Z" - latency: 915.554µs message: 'network-check-target-ip-10-0-133-102: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:29:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:24:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-102-to-network-check-target-ip-10-0-138-121 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-102.ec2.internal uid: 2830d1ae-d329-4681-a038-e4000aee7a7e resourceVersion: "27382" uid: de3fd54a-0f24-477b-941a-e039b286bc66 spec: sourcePod: network-check-source-7d88cb55d8-4jlnf targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-24T15:31:22Z" message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.38638ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:38:22Z" - latency: 2.297177ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:37:22Z" - latency: 2.144726ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:36:22Z" - latency: 2.364502ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:35:22Z" - latency: 2.263311ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:34:22Z" - latency: 2.706989ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:33:22Z" - latency: 2.368702ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:32:22Z" - latency: 2.727704ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:31:22Z" - latency: 2.322018ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:30:22Z" - latency: 2.223237ms message: 'network-check-target-ip-10-0-138-121: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:29:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:24:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-102-to-network-check-target-ip-10-0-143-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-102.ec2.internal uid: 2830d1ae-d329-4681-a038-e4000aee7a7e resourceVersion: "27381" uid: e7d57b65-45ee-41f5-a5bf-6ef205823e05 spec: sourcePod: network-check-source-7d88cb55d8-4jlnf targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-24T15:31:22Z" message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.301034ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:38:22Z" - latency: 2.648821ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:37:22Z" - latency: 2.144148ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:36:22Z" - latency: 2.508049ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:35:22Z" - latency: 2.608846ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:34:22Z" - latency: 2.202173ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:33:22Z" - latency: 2.315976ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:32:22Z" - latency: 2.312447ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:31:22Z" - latency: 2.260657ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:30:22Z" - latency: 2.416962ms message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:29:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-24T15:24:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-102-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-102.ec2.internal uid: 2830d1ae-d329-4681-a038-e4000aee7a7e resourceVersion: "26177" uid: 98d4ae34-970e-4f5e-b78c-78e3050ed23c spec: sourcePod: network-check-source-7d88cb55d8-4jlnf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-24T15:30:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 730.715µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:36:22Z" - latency: 1.634405ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:36:22Z" - latency: 871.358µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:35:22Z" - latency: 1.765768ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:35:22Z" - latency: 885.3µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:34:22Z" - latency: 1.507432ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:34:22Z" - latency: 1.184135ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:33:22Z" - latency: 1.475067ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:33:22Z" - latency: 818.946µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-24T15:32:22Z" - latency: 1.756107ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-24T15:32:22Z" kind: List metadata: resourceVersion: ""