apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T15:40:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-6-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-6.ec2.internal uid: db0b2624-0c64-4ca4-9e15-0acfd5602eaf resourceVersion: "52067" uid: 12a3e899-46bb-4cfe-b1b8-8cf5acaeddee spec: sourcePod: network-check-source-dbd9cf844-49brf targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T15:47:33Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.102018ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:15:33Z" - latency: 937.293µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:14:33Z" - latency: 1.091699ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:13:33Z" - latency: 1.049689ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:12:33Z" - latency: 996.689µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:11:33Z" - latency: 1.133308ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:10:33Z" - latency: 942.426µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:09:33Z" - latency: 950.518µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:08:33Z" - latency: 905.65µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:07:33Z" - latency: 1.518682ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:06:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T15:40:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-6-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-6.ec2.internal uid: db0b2624-0c64-4ca4-9e15-0acfd5602eaf resourceVersion: "46520" uid: 94bad9b2-cb4e-4487-9155-5f3b50575e2b spec: sourcePod: network-check-source-dbd9cf844-49brf targetEndpoint: a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T15:46:33Z" message: 'load-balancer-api-external: tcp connection to a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.708888ms message: 'load-balancer-api-external: tcp connection to a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:10:33Z" - latency: 6.772123ms message: 'load-balancer-api-external: resolved host name a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T16:10:33Z" - latency: 3.919612ms message: 'load-balancer-api-external: tcp connection to a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:09:33Z" - latency: 6.080563ms message: 'load-balancer-api-external: resolved host name a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T16:09:33Z" - latency: 3.170607ms message: 'load-balancer-api-external: tcp connection to a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:08:33Z" - latency: 6.798299ms message: 'load-balancer-api-external: resolved host name a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T16:08:33Z" - latency: 6.479311ms message: 'load-balancer-api-external: tcp connection to a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:07:33Z" - latency: 7.142745ms message: 'load-balancer-api-external: resolved host name a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T16:07:33Z" - latency: 6.170985ms message: 'load-balancer-api-external: tcp connection to a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:06:33Z" - latency: 11.879088ms message: 'load-balancer-api-external: resolved host name a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T16:06:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T15:40:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-6-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-6.ec2.internal uid: db0b2624-0c64-4ca4-9e15-0acfd5602eaf resourceVersion: "46521" uid: 66d89abf-9af7-4494-9000-0b8734009cde spec: sourcePod: network-check-source-dbd9cf844-49brf targetEndpoint: a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T15:46:33Z" message: 'load-balancer-api-internal: tcp connection to a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.697366ms message: 'load-balancer-api-internal: tcp connection to a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:10:33Z" - latency: 6.674105ms message: 'load-balancer-api-internal: resolved host name a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T16:10:33Z" - latency: 3.971873ms message: 'load-balancer-api-internal: tcp connection to a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:09:33Z" - latency: 5.984139ms message: 'load-balancer-api-internal: resolved host name a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T16:09:33Z" - latency: 3.395755ms message: 'load-balancer-api-internal: tcp connection to a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:08:33Z" - latency: 6.709413ms message: 'load-balancer-api-internal: resolved host name a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T16:08:33Z" - latency: 4.154281ms message: 'load-balancer-api-internal: tcp connection to a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:07:33Z" - latency: 7.008836ms message: 'load-balancer-api-internal: resolved host name a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T16:07:33Z" - latency: 6.184838ms message: 'load-balancer-api-internal: tcp connection to a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:06:33Z" - latency: 11.856479ms message: 'load-balancer-api-internal: resolved host name a1d6dc1a29c73488fa6b18c05a105004-4e66aef1876f11c2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T16:06:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T15:40:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-6-to-network-check-target-ip-10-0-134-81 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-6.ec2.internal uid: db0b2624-0c64-4ca4-9e15-0acfd5602eaf resourceVersion: "52066" uid: 7073cc46-e03d-43f1-bc03-fa9f2754100c spec: sourcePod: network-check-source-dbd9cf844-49brf targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T15:47:33Z" message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.997636ms message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:15:33Z" - latency: 2.151787ms message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:14:33Z" - latency: 2.171672ms message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:13:33Z" - latency: 2.288219ms message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:12:33Z" - latency: 2.25096ms message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:11:33Z" - latency: 2.324374ms message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:10:33Z" - latency: 2.527377ms message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:09:33Z" - latency: 2.165418ms message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:08:33Z" - latency: 2.256133ms message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:07:33Z" - latency: 2.652948ms message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:06:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T15:40:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-6-to-network-check-target-ip-10-0-141-19 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-6.ec2.internal uid: db0b2624-0c64-4ca4-9e15-0acfd5602eaf resourceVersion: "52065" uid: f3d6c997-4a60-4295-807c-4e2d0a8c4dd1 spec: sourcePod: network-check-source-dbd9cf844-49brf targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T15:47:33Z" message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.372833ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:15:33Z" - latency: 2.389089ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:14:33Z" - latency: 1.962867ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:13:33Z" - latency: 2.737688ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:12:33Z" - latency: 2.214347ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:11:33Z" - latency: 2.366033ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:10:33Z" - latency: 2.809646ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:09:33Z" - latency: 2.208765ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:08:33Z" - latency: 2.069985ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:07:33Z" - latency: 2.093867ms message: 'network-check-target-ip-10-0-141-19: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:06:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T15:40:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-6-to-network-check-target-ip-10-0-142-6 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-6.ec2.internal uid: db0b2624-0c64-4ca4-9e15-0acfd5602eaf resourceVersion: "52064" uid: 4f52c017-320a-4c49-8321-37fa6f94c0a7 spec: sourcePod: network-check-source-dbd9cf844-49brf targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T15:47:33Z" message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 862.981µs message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:15:33Z" - latency: 906.869µs message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:14:33Z" - latency: 916.005µs message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:13:33Z" - latency: 1.120188ms message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:12:33Z" - latency: 1.512427ms message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:11:33Z" - latency: 1.295673ms message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:10:33Z" - latency: 989.763µs message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:09:33Z" - latency: 891.977µs message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:08:33Z" - latency: 911.848µs message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:07:33Z" - latency: 815.678µs message: 'network-check-target-ip-10-0-142-6: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:06:33Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T15:40:32Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-6-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-6.ec2.internal uid: db0b2624-0c64-4ca4-9e15-0acfd5602eaf resourceVersion: "46519" uid: 2642960e-fe3c-411e-952a-f6ded65c29ee spec: sourcePod: network-check-source-dbd9cf844-49brf targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T15:46:33Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 833.934µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:10:33Z" - latency: 1.647999ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T16:10:33Z" - latency: 1.016545ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:09:33Z" - latency: 1.676648ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T16:09:33Z" - latency: 1.38007ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:08:33Z" - latency: 1.77445ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T16:08:33Z" - latency: 854.382µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:07:33Z" - latency: 2.128774ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T16:07:33Z" - latency: 1.177354ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T16:06:33Z" - latency: 2.058053ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T16:06:33Z" kind: List metadata: resourceVersion: ""