apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:40:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-74-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-74.us-west-2.compute.internal uid: 6b9e1f11-db7f-40ff-9bd7-79c5759e3917 resourceVersion: "23289" uid: 9e9351bf-5d6e-411d-86c4-87909068a547 spec: sourcePod: network-check-source-6f78d59f99-d9fjm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T18:47:45Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 604.158µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:15:45Z" - latency: 604.778µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:14:45Z" - latency: 784.558µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:13:45Z" - latency: 629.941µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:12:45Z" - latency: 603.262µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:11:45Z" - latency: 630.252µ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:45Z" - latency: 612.838µ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:45Z" - latency: 609.443µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:08:45Z" - latency: 759.409µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:07:45Z" - latency: 621.973µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:06:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:40:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-74-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-74.us-west-2.compute.internal uid: 6b9e1f11-db7f-40ff-9bd7-79c5759e3917 resourceVersion: "23554" uid: a4e71990-66a3-4e02-848c-3704ed056445 spec: sourcePod: network-check-source-6f78d59f99-d9fjm targetEndpoint: a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T18:46:45Z" message: 'load-balancer-api-external: tcp connection to a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 50.933665ms message: 'load-balancer-api-external: tcp connection to a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:16:45Z" - latency: 2.107505ms message: 'load-balancer-api-external: resolved host name a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:16:45Z" - latency: 53.700089ms message: 'load-balancer-api-external: tcp connection to a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:15:45Z" - latency: 2.077935ms message: 'load-balancer-api-external: resolved host name a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:15:45Z" - latency: 55.442165ms message: 'load-balancer-api-external: tcp connection to a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:14:45Z" - latency: 3.3549ms message: 'load-balancer-api-external: resolved host name a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:14:45Z" - latency: 48.573775ms message: 'load-balancer-api-external: tcp connection to a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:13:45Z" - latency: 2.060588ms message: 'load-balancer-api-external: resolved host name a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:13:45Z" - latency: 48.03953ms message: 'load-balancer-api-external: tcp connection to a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:12:45Z" - latency: 2.07417ms message: 'load-balancer-api-external: resolved host name a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:12:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:40:44Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-74-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-74.us-west-2.compute.internal uid: 6b9e1f11-db7f-40ff-9bd7-79c5759e3917 resourceVersion: "23553" uid: 8858d66e-6f4e-4455-bde8-197ae1ce77c5 spec: sourcePod: network-check-source-6f78d59f99-d9fjm targetEndpoint: a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T18:46:48Z" message: 'load-balancer-api-internal: tcp connection to a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 51.418382ms message: 'load-balancer-api-internal: tcp connection to a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:16:45Z" - latency: 8.089013ms message: 'load-balancer-api-internal: resolved host name a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:16:45Z" - latency: 3.387241742s message: 'load-balancer-api-internal: tcp connection to a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:15:45Z" - latency: 6.413204ms message: 'load-balancer-api-internal: resolved host name a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:15:45Z" - latency: 51.16531ms message: 'load-balancer-api-internal: tcp connection to a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:14:45Z" - latency: 6.063165ms message: 'load-balancer-api-internal: resolved host name a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:14:45Z" - latency: 51.374491ms message: 'load-balancer-api-internal: tcp connection to a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:13:45Z" - latency: 10.803043ms message: 'load-balancer-api-internal: resolved host name a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:13:45Z" - latency: 54.0818ms message: 'load-balancer-api-internal: tcp connection to a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:12:45Z" - latency: 7.355264ms message: 'load-balancer-api-internal: resolved host name a1170fdc21ac14235b67aafb8b26d5e9-34204dc823c30344.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:12:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:40:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-74-to-network-check-target-ip-10-0-132-74 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-74.us-west-2.compute.internal uid: 6b9e1f11-db7f-40ff-9bd7-79c5759e3917 resourceVersion: "23286" uid: 02b2c576-a978-4df3-b4b7-603ab3b86894 spec: sourcePod: network-check-source-6f78d59f99-d9fjm targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:47:45Z" message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 826.878µs message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:15:45Z" - latency: 992.076µs message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:14:45Z" - latency: 1.480306ms message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:13:45Z" - latency: 1.330148ms message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:12:45Z" - latency: 1.660048ms message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:11:45Z" - latency: 859.116µs message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:10:45Z" - latency: 1.09783ms message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:09:45Z" - latency: 1.086052ms message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:08:45Z" - latency: 1.093835ms message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:07:45Z" - latency: 1.438739ms message: 'network-check-target-ip-10-0-132-74: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:06:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:40:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-74-to-network-check-target-ip-10-0-133-244 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-74.us-west-2.compute.internal uid: 6b9e1f11-db7f-40ff-9bd7-79c5759e3917 resourceVersion: "23288" uid: 756bc74c-6132-4628-98f6-e859592b540e spec: sourcePod: network-check-source-6f78d59f99-d9fjm targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:47:45Z" message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.927104ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:15:45Z" - latency: 1.839817ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:14:45Z" - latency: 1.797551ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:13:45Z" - latency: 1.677916ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:12:45Z" - latency: 1.943834ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:11:45Z" - latency: 1.875119ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:10:45Z" - latency: 1.878906ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:09:45Z" - latency: 1.596506ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:08:45Z" - latency: 1.765128ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:07:45Z" - latency: 1.475454ms message: 'network-check-target-ip-10-0-133-244: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:06:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:40:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-74-to-network-check-target-ip-10-0-133-248 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-74.us-west-2.compute.internal uid: 6b9e1f11-db7f-40ff-9bd7-79c5759e3917 resourceVersion: "23287" uid: c7db9554-d52e-466b-921d-1ac3b7064c1d spec: sourcePod: network-check-source-6f78d59f99-d9fjm targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:47:45Z" message: 'network-check-target-ip-10-0-133-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.110563ms message: 'network-check-target-ip-10-0-133-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:15:45Z" - latency: 2.079816ms message: 'network-check-target-ip-10-0-133-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:14:45Z" - latency: 2.212084ms message: 'network-check-target-ip-10-0-133-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:13:45Z" - latency: 2.307092ms message: 'network-check-target-ip-10-0-133-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:12:45Z" - latency: 2.222341ms message: 'network-check-target-ip-10-0-133-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:11:45Z" - latency: 2.208911ms message: 'network-check-target-ip-10-0-133-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:10:45Z" - latency: 2.291747ms message: 'network-check-target-ip-10-0-133-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:09:45Z" - latency: 2.165941ms message: 'network-check-target-ip-10-0-133-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:08:45Z" - latency: 2.146463ms message: 'network-check-target-ip-10-0-133-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:07:45Z" - latency: 2.239519ms message: 'network-check-target-ip-10-0-133-248: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:06:45Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:40:45Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-74-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-74.us-west-2.compute.internal uid: 6b9e1f11-db7f-40ff-9bd7-79c5759e3917 resourceVersion: "23552" uid: 1ed21a98-b25f-4420-89d3-c2679f832c58 spec: sourcePod: network-check-source-6f78d59f99-d9fjm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T18:46:45Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 693.769µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:16:45Z" - latency: 2.27621ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:16:45Z" - latency: 809.892µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:15:45Z" - latency: 1.583032ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:15:45Z" - latency: 1.07501ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:14:45Z" - latency: 1.489888ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:14:45Z" - latency: 975.555µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:13:45Z" - latency: 1.967265ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:13:45Z" - latency: 1.650798ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:12:45Z" - latency: 1.981711ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:12:45Z" kind: List metadata: resourceVersion: ""