apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:19:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-15-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-15.ec2.internal uid: a9bb0845-8a0f-4de3-bdac-7a212ed42110 resourceVersion: "42590" uid: 344d715a-ed23-4926-bbdd-4eca1817547f spec: sourcePod: network-check-source-8894fc9bd-kc9q6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T21:26:10Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.050165ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:54:10Z" - latency: 1.044314ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:53:10Z" - latency: 1.087288ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:52:10Z" - latency: 994.856µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:51:10Z" - latency: 1.343233ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:50:10Z" - latency: 1.017092ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:49:10Z" - latency: 867.024µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:48:10Z" - latency: 1.034584ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:47:10Z" - latency: 1.078427ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:46:10Z" - latency: 1.315541ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:45:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:19:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-15-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-15.ec2.internal uid: a9bb0845-8a0f-4de3-bdac-7a212ed42110 resourceVersion: "43234" uid: f49814e6-d38d-4e26-bfae-d62f87bd3d90 spec: sourcePod: network-check-source-8894fc9bd-kc9q6 targetEndpoint: ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:25:10Z" message: 'load-balancer-api-external: tcp connection to ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.829231ms message: 'load-balancer-api-external: tcp connection to ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:55:10Z" - latency: 7.676698ms message: 'load-balancer-api-external: resolved host name ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:55:10Z" - latency: 4.965122ms message: 'load-balancer-api-external: tcp connection to ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:54:10Z" - latency: 7.248992ms message: 'load-balancer-api-external: resolved host name ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:54:10Z" - latency: 4.721549ms message: 'load-balancer-api-external: tcp connection to ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:53:10Z" - latency: 9.483544ms message: 'load-balancer-api-external: resolved host name ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:53:10Z" - latency: 4.703655ms message: 'load-balancer-api-external: tcp connection to ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:52:10Z" - latency: 7.994165ms message: 'load-balancer-api-external: resolved host name ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:52:10Z" - latency: 5.100943ms message: 'load-balancer-api-external: tcp connection to ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:51:10Z" - latency: 8.433357ms message: 'load-balancer-api-external: resolved host name ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:51:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:19:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-15-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-15.ec2.internal uid: a9bb0845-8a0f-4de3-bdac-7a212ed42110 resourceVersion: "43235" uid: 90f3c3b3-4e20-4a6d-be7c-85144f7b04a1 spec: sourcePod: network-check-source-8894fc9bd-kc9q6 targetEndpoint: ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:25:10Z" message: 'load-balancer-api-internal: tcp connection to ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.858238ms message: 'load-balancer-api-internal: tcp connection to ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:55:10Z" - latency: 7.620475ms message: 'load-balancer-api-internal: resolved host name ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:55:10Z" - latency: 4.936182ms message: 'load-balancer-api-internal: tcp connection to ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:54:10Z" - latency: 7.129397ms message: 'load-balancer-api-internal: resolved host name ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:54:10Z" - latency: 4.773161ms message: 'load-balancer-api-internal: tcp connection to ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:53:10Z" - latency: 9.299779ms message: 'load-balancer-api-internal: resolved host name ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:53:10Z" - latency: 4.736169ms message: 'load-balancer-api-internal: tcp connection to ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:52:10Z" - latency: 7.961473ms message: 'load-balancer-api-internal: resolved host name ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:52:10Z" - latency: 5.16676ms message: 'load-balancer-api-internal: tcp connection to ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:51:10Z" - latency: 8.395883ms message: 'load-balancer-api-internal: resolved host name ae9386c5fe22f415e8fda6b4f93b96ec-45f0f6f9761ab0b9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:51:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:19:08Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-15-to-network-check-target-ip-10-0-128-142 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-15.ec2.internal uid: a9bb0845-8a0f-4de3-bdac-7a212ed42110 resourceVersion: "42589" uid: ac68544c-c9fe-468e-8f15-da174ae6238e spec: sourcePod: network-check-source-8894fc9bd-kc9q6 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:26:10Z" message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.118891ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:54:10Z" - latency: 2.425287ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:53:10Z" - latency: 2.348504ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:52:10Z" - latency: 2.132912ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:51:10Z" - latency: 2.232109ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:50:10Z" - latency: 2.375878ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:49:10Z" - latency: 2.218855ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:48:10Z" - latency: 2.430091ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:47:10Z" - latency: 2.063914ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:46:10Z" - latency: 1.744416ms message: 'network-check-target-ip-10-0-128-142: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:45:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:19:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-15-to-network-check-target-ip-10-0-131-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-15.ec2.internal uid: a9bb0845-8a0f-4de3-bdac-7a212ed42110 resourceVersion: "42588" uid: ada56a4b-5cee-4f57-8c03-052497a75579 spec: sourcePod: network-check-source-8894fc9bd-kc9q6 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:26:10Z" message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.46668ms message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:54:10Z" - latency: 2.403554ms message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:53:10Z" - latency: 2.118344ms message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:52:10Z" - latency: 2.125838ms message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:51:10Z" - latency: 2.37262ms message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:50:10Z" - latency: 2.020262ms message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:49:10Z" - latency: 2.021942ms message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:48:10Z" - latency: 2.361046ms message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:47:10Z" - latency: 1.855893ms message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:46:10Z" - latency: 2.083774ms message: 'network-check-target-ip-10-0-131-162: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:45:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:19:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-15-to-network-check-target-ip-10-0-139-15 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-15.ec2.internal uid: a9bb0845-8a0f-4de3-bdac-7a212ed42110 resourceVersion: "42587" uid: c970c566-46e1-4434-993a-29459556c97a spec: sourcePod: network-check-source-8894fc9bd-kc9q6 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:26:10Z" message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 996.474µs message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:54:10Z" - latency: 794.236µs message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:53:10Z" - latency: 841.725µs message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:52:10Z" - latency: 1.169521ms message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:51:10Z" - latency: 819.504µs message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:50:10Z" - latency: 993.719µs message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:49:10Z" - latency: 765.253µs message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:48:10Z" - latency: 1.543508ms message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:47:10Z" - latency: 891.062µs message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:46:10Z" - latency: 841.16µs message: 'network-check-target-ip-10-0-139-15: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:45:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:19:09Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-15-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-15.ec2.internal uid: a9bb0845-8a0f-4de3-bdac-7a212ed42110 resourceVersion: "43232" uid: 5a794a7f-4237-4a22-9dcb-93e2081a6899 spec: sourcePod: network-check-source-8894fc9bd-kc9q6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T21:25:10Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 832.825µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:55:10Z" - latency: 1.713327ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:55:10Z" - latency: 819.063µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:54:10Z" - latency: 1.735335ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:54:10Z" - latency: 741.01µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:53:10Z" - latency: 2.327849ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:53:10Z" - latency: 806.779µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:52:10Z" - latency: 1.71302ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:52:10Z" - latency: 952.058µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:51:10Z" - latency: 1.730404ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:51:10Z" kind: List metadata: resourceVersion: ""