apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T01:50:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-196-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-196.ec2.internal uid: 0efc3744-32ad-48fb-83be-ba642262a89d resourceVersion: "30386" uid: a2ae2d8f-b7ea-42a1-a96d-fe1bb10eb9e8 spec: sourcePod: network-check-source-6947749cfc-k74jj targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-15T01:57:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.315287ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:04:37Z" - latency: 1.833134ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:03:37Z" - latency: 1.394427ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:02:37Z" - latency: 1.566293ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:01:37Z" - latency: 960.82µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:00:37Z" - latency: 828.243µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:59:37Z" - latency: 1.448981ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:58:37Z" - latency: 764.948µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:57:37Z" - latency: 2.966074ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:56:37Z" - latency: 774.895µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:55:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T01:50:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-196-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-196.ec2.internal uid: 0efc3744-32ad-48fb-83be-ba642262a89d resourceVersion: "29126" uid: f4c47e51-cdc1-42b6-97e9-10a6a53217ab spec: sourcePod: network-check-source-6947749cfc-k74jj targetEndpoint: acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T01:56:37Z" message: 'load-balancer-api-external: tcp connection to acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.121022ms message: 'load-balancer-api-external: tcp connection to acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:02:37Z" - latency: 8.071802ms message: 'load-balancer-api-external: resolved host name acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T02:02:37Z" - latency: 5.056191ms message: 'load-balancer-api-external: tcp connection to acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:01:37Z" - latency: 9.310122ms message: 'load-balancer-api-external: resolved host name acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T02:01:37Z" - latency: 4.781416ms message: 'load-balancer-api-external: tcp connection to acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:00:37Z" - latency: 8.320286ms message: 'load-balancer-api-external: resolved host name acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T02:00:37Z" - latency: 4.445902ms message: 'load-balancer-api-external: tcp connection to acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:59:37Z" - latency: 8.765217ms message: 'load-balancer-api-external: resolved host name acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T01:59:37Z" - latency: 5.209929ms message: 'load-balancer-api-external: tcp connection to acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:58:37Z" - latency: 8.819115ms message: 'load-balancer-api-external: resolved host name acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T01:58:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T01:50:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-196-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-196.ec2.internal uid: 0efc3744-32ad-48fb-83be-ba642262a89d resourceVersion: "29127" uid: 907b42f4-4022-4702-8bcb-085c43506197 spec: sourcePod: network-check-source-6947749cfc-k74jj targetEndpoint: acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T01:56:37Z" message: 'load-balancer-api-internal: tcp connection to acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.938512ms message: 'load-balancer-api-internal: tcp connection to acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:02:37Z" - latency: 8.123286ms message: 'load-balancer-api-internal: resolved host name acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T02:02:37Z" - latency: 5.013905ms message: 'load-balancer-api-internal: tcp connection to acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:01:37Z" - latency: 9.342116ms message: 'load-balancer-api-internal: resolved host name acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T02:01:37Z" - latency: 4.714621ms message: 'load-balancer-api-internal: tcp connection to acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:00:37Z" - latency: 8.42407ms message: 'load-balancer-api-internal: resolved host name acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T02:00:37Z" - latency: 4.96011ms message: 'load-balancer-api-internal: tcp connection to acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:59:37Z" - latency: 8.816631ms message: 'load-balancer-api-internal: resolved host name acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T01:59:37Z" - latency: 5.908204ms message: 'load-balancer-api-internal: tcp connection to acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:58:37Z" - latency: 8.858932ms message: 'load-balancer-api-internal: resolved host name acb9f4b78a8ee4bb3bece9a9b1687f52-cd37e5389ce2e1f6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T01:58:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T01:50:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-196-to-network-check-target-ip-10-0-141-3 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-196.ec2.internal uid: 0efc3744-32ad-48fb-83be-ba642262a89d resourceVersion: "30384" uid: 15c88b7f-a545-4edf-b2d9-9cc2e287d5ef spec: sourcePod: network-check-source-6947749cfc-k74jj targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-15T01:57:37Z" message: 'network-check-target-ip-10-0-141-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.458001ms message: 'network-check-target-ip-10-0-141-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:04:37Z" - latency: 2.252819ms message: 'network-check-target-ip-10-0-141-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:03:37Z" - latency: 2.425501ms message: 'network-check-target-ip-10-0-141-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:02:37Z" - latency: 1.906417ms message: 'network-check-target-ip-10-0-141-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:01:37Z" - latency: 1.959561ms message: 'network-check-target-ip-10-0-141-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:00:37Z" - latency: 2.323067ms message: 'network-check-target-ip-10-0-141-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:59:37Z" - latency: 2.866321ms message: 'network-check-target-ip-10-0-141-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:58:37Z" - latency: 2.265195ms message: 'network-check-target-ip-10-0-141-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:57:37Z" - latency: 2.293992ms message: 'network-check-target-ip-10-0-141-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:56:37Z" - latency: 2.20374ms message: 'network-check-target-ip-10-0-141-3: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:55:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T01:50:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-196-to-network-check-target-ip-10-0-141-68 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-196.ec2.internal uid: 0efc3744-32ad-48fb-83be-ba642262a89d resourceVersion: "30385" uid: 382bc077-9a7a-4770-9f47-35a1ec4b98dd spec: sourcePod: network-check-source-6947749cfc-k74jj targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-15T01:57:37Z" message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.648719ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:04:37Z" - latency: 2.115207ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:03:37Z" - latency: 2.054021ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:02:37Z" - latency: 2.056663ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:01:37Z" - latency: 2.031805ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:00:37Z" - latency: 2.027547ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:59:37Z" - latency: 2.043665ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:58:37Z" - latency: 1.729299ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:57:37Z" - latency: 4.453914ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:56:37Z" - latency: 1.750157ms message: 'network-check-target-ip-10-0-141-68: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:55:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T01:50:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-196-to-network-check-target-ip-10-0-143-196 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-196.ec2.internal uid: 0efc3744-32ad-48fb-83be-ba642262a89d resourceVersion: "30383" uid: ed4632ce-53b5-42e9-a350-31a14f8a06f1 spec: sourcePod: network-check-source-6947749cfc-k74jj targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-15T01:57:37Z" message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.565723ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:04:37Z" - latency: 1.424276ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:03:37Z" - latency: 982.8µs message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:02:37Z" - latency: 867.985µs message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:01:37Z" - latency: 1.046618ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:00:37Z" - latency: 1.022443ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:59:37Z" - latency: 889.619µs message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:58:37Z" - latency: 1.489063ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:57:37Z" - latency: 1.313244ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:56:37Z" - latency: 920.516µs message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:55:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T01:50:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-196-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-196.ec2.internal uid: 0efc3744-32ad-48fb-83be-ba642262a89d resourceVersion: "29125" uid: f3099e51-6552-494a-a7d1-3849fc68a5bf spec: sourcePod: network-check-source-6947749cfc-k74jj targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-15T01:56:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 851.178µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:02:37Z" - latency: 1.832208ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T02:02:37Z" - latency: 769.014µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:01:37Z" - latency: 1.815694ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T02:01:37Z" - latency: 1.056113ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T02:00:37Z" - latency: 1.900331ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T02:00:37Z" - latency: 1.012477ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:59:37Z" - latency: 1.784873ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T01:59:37Z" - latency: 938.773µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T01:58:37Z" - latency: 2.095488ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T01:58:37Z" kind: List metadata: resourceVersion: ""