apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:15:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-58-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-58.ec2.internal uid: 407bcf77-47e6-45d6-bda5-e89ebcfa1fcd resourceVersion: "18825" uid: 4df98354-041a-4756-b9c2-cf7aa0414c2c spec: sourcePod: network-check-source-7f44b6dd87-7hxq9 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-29T10:22:50Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 956.655µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:50Z" - latency: 1.503554ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:35:50Z" - latency: 906.795µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:34:50Z" - latency: 827.021µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:33:50Z" - latency: 876.526µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:32:50Z" - latency: 899.228µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:31:50Z" - latency: 1.519309ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:30:50Z" - latency: 898.406µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:29:50Z" - latency: 1.364841ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:28:50Z" - latency: 1.066682ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:27:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:15:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-58-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-58.ec2.internal uid: 407bcf77-47e6-45d6-bda5-e89ebcfa1fcd resourceVersion: "19983" uid: 37c28ba4-fff2-4a21-ad54-68f08a3f3c3a spec: sourcePod: network-check-source-7f44b6dd87-7hxq9 targetEndpoint: ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T10:21:50Z" message: 'load-balancer-api-external: tcp connection to ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.607422ms message: 'load-balancer-api-external: tcp connection to ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:39:50Z" - latency: 8.268368ms message: 'load-balancer-api-external: resolved host name ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:39:50Z" - latency: 4.499956ms message: 'load-balancer-api-external: tcp connection to ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:38:50Z" - latency: 8.563393ms message: 'load-balancer-api-external: resolved host name ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:38:50Z" - latency: 3.855609ms message: 'load-balancer-api-external: tcp connection to ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:37:50Z" - latency: 13.705765ms message: 'load-balancer-api-external: resolved host name ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:37:50Z" - latency: 4.557299ms message: 'load-balancer-api-external: tcp connection to ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:50Z" - latency: 8.423608ms message: 'load-balancer-api-external: resolved host name ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:36:50Z" - latency: 3.814747ms message: 'load-balancer-api-external: tcp connection to ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:35:50Z" - latency: 7.688803ms message: 'load-balancer-api-external: resolved host name ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:35:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:15:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-58-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-58.ec2.internal uid: 407bcf77-47e6-45d6-bda5-e89ebcfa1fcd resourceVersion: "19984" uid: 416e97f1-4555-417b-8d12-6f111520e256 spec: sourcePod: network-check-source-7f44b6dd87-7hxq9 targetEndpoint: ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T10:21:50Z" message: 'load-balancer-api-internal: tcp connection to ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.387981ms message: 'load-balancer-api-internal: tcp connection to ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:39:50Z" - latency: 8.289667ms message: 'load-balancer-api-internal: resolved host name ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:39:50Z" - latency: 4.000346ms message: 'load-balancer-api-internal: tcp connection to ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:38:50Z" - latency: 8.644176ms message: 'load-balancer-api-internal: resolved host name ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:38:50Z" - latency: 5.396184ms message: 'load-balancer-api-internal: tcp connection to ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:37:50Z" - latency: 13.655206ms message: 'load-balancer-api-internal: resolved host name ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:37:50Z" - latency: 4.552074ms message: 'load-balancer-api-internal: tcp connection to ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:50Z" - latency: 8.315991ms message: 'load-balancer-api-internal: resolved host name ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:36:50Z" - latency: 3.794656ms message: 'load-balancer-api-internal: tcp connection to ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:35:50Z" - latency: 7.67318ms message: 'load-balancer-api-internal: resolved host name ab2bbce5e226445a2a36652db8d85793-3ded8c4a4cfbc292.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T10:35:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:15:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-58-to-network-check-target-ip-10-0-130-137 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-58.ec2.internal uid: 407bcf77-47e6-45d6-bda5-e89ebcfa1fcd resourceVersion: "18824" uid: 20c71635-d5f0-4e6a-b642-7c50b14e3ff0 spec: sourcePod: network-check-source-7f44b6dd87-7hxq9 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-29T10:22:50Z" message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.052318ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:50Z" - latency: 2.198224ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:35:50Z" - latency: 2.083097ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:34:50Z" - latency: 2.163714ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:33:50Z" - latency: 2.148518ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:32:50Z" - latency: 2.164671ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:31:50Z" - latency: 2.691027ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:30:50Z" - latency: 2.057312ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:29:50Z" - latency: 2.163365ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:28:50Z" - latency: 2.092016ms message: 'network-check-target-ip-10-0-130-137: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:27:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:15:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-58-to-network-check-target-ip-10-0-132-181 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-58.ec2.internal uid: 407bcf77-47e6-45d6-bda5-e89ebcfa1fcd resourceVersion: "18823" uid: 7180a1f9-89e1-4ffa-8770-c0940b213ab5 spec: sourcePod: network-check-source-7f44b6dd87-7hxq9 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-29T10:22:50Z" message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.849692ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:50Z" - latency: 1.769928ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:35:50Z" - latency: 2.074546ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:34:50Z" - latency: 1.917196ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:33:50Z" - latency: 1.87295ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:32:50Z" - latency: 1.735605ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:31:50Z" - latency: 1.877968ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:30:50Z" - latency: 1.853272ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:29:50Z" - latency: 1.864293ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:28:50Z" - latency: 1.905257ms message: 'network-check-target-ip-10-0-132-181: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:27:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:15:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-58-to-network-check-target-ip-10-0-143-58 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-58.ec2.internal uid: 407bcf77-47e6-45d6-bda5-e89ebcfa1fcd resourceVersion: "18822" uid: 153d387f-8939-4bd0-b241-36a0c3549ee0 spec: sourcePod: network-check-source-7f44b6dd87-7hxq9 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-29T10:22:50Z" message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 856.384µs message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:50Z" - latency: 841.353µs message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:35:50Z" - latency: 1.425453ms message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:34:50Z" - latency: 1.303903ms message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:33:50Z" - latency: 855.174µs message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:32:50Z" - latency: 795.3µs message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:31:50Z" - latency: 1.308587ms message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:30:50Z" - latency: 856.422µs message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:29:50Z" - latency: 940.866µs message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:28:50Z" - latency: 850.09µs message: 'network-check-target-ip-10-0-143-58: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:27:50Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T10:15:48Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-58-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-58.ec2.internal uid: 407bcf77-47e6-45d6-bda5-e89ebcfa1fcd resourceVersion: "19982" uid: 40790dda-776d-4b58-80d7-3eff9e170b87 spec: sourcePod: network-check-source-7f44b6dd87-7hxq9 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-29T10:21:50Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 887.801µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:39:50Z" - latency: 1.678724ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T10:39:50Z" - latency: 788.731µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:38:50Z" - latency: 1.477448ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T10:38:50Z" - latency: 857.144µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:37:50Z" - latency: 1.550316ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T10:37:50Z" - latency: 948.644µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:36:50Z" - latency: 1.913079ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T10:36:50Z" - latency: 1.127155ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T10:35:50Z" - latency: 1.668089ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T10:35:50Z" kind: List metadata: resourceVersion: ""