apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T10:08:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-122-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-122.ec2.internal uid: 6c0e3a17-8d49-419f-aa5e-ef58399cb596 resourceVersion: "19031" uid: e4a5bd8c-b004-49b3-885a-a874a40bf025 spec: sourcePod: network-check-source-7f44b6dd87-dzkx4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T10:15:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 826.164µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:29:21Z" - latency: 1.030804ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:28:21Z" - latency: 967.945µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:27:21Z" - latency: 1.096756ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:26:21Z" - latency: 1.260936ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:25:21Z" - latency: 989.691µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:24:21Z" - latency: 1.509143ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:23:21Z" - latency: 1.525372ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:22:21Z" - latency: 760.948µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:21:21Z" - latency: 841.029µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:20:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T10:08:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-122-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-122.ec2.internal uid: 6c0e3a17-8d49-419f-aa5e-ef58399cb596 resourceVersion: "20189" uid: 5d431b8e-8475-4884-9f27-9068fea634d5 spec: sourcePod: network-check-source-7f44b6dd87-dzkx4 targetEndpoint: a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T10:14:21Z" message: 'load-balancer-api-external: tcp connection to a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.645719ms message: 'load-balancer-api-external: tcp connection to a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:32:21Z" - latency: 8.020581ms message: 'load-balancer-api-external: resolved host name a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:32:21Z" - latency: 4.867305ms message: 'load-balancer-api-external: tcp connection to a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:31:21Z" - latency: 8.392174ms message: 'load-balancer-api-external: resolved host name a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:31:21Z" - latency: 5.236428ms message: 'load-balancer-api-external: tcp connection to a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:30:21Z" - latency: 7.121007ms message: 'load-balancer-api-external: resolved host name a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:30:21Z" - latency: 4.833057ms message: 'load-balancer-api-external: tcp connection to a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:29:21Z" - latency: 8.485225ms message: 'load-balancer-api-external: resolved host name a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:29:21Z" - latency: 4.959573ms message: 'load-balancer-api-external: tcp connection to a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:28:21Z" - latency: 8.643344ms message: 'load-balancer-api-external: resolved host name a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:28:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T10:08:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-122-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-122.ec2.internal uid: 6c0e3a17-8d49-419f-aa5e-ef58399cb596 resourceVersion: "20188" uid: 91180e8e-df4d-47f5-a4ce-333981368305 spec: sourcePod: network-check-source-7f44b6dd87-dzkx4 targetEndpoint: a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T10:14:21Z" message: 'load-balancer-api-internal: tcp connection to a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.63718ms message: 'load-balancer-api-internal: tcp connection to a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:32:21Z" - latency: 8.071566ms message: 'load-balancer-api-internal: resolved host name a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:32:21Z" - latency: 5.396045ms message: 'load-balancer-api-internal: tcp connection to a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:31:21Z" - latency: 8.449729ms message: 'load-balancer-api-internal: resolved host name a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:31:21Z" - latency: 4.180086ms message: 'load-balancer-api-internal: tcp connection to a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:30:21Z" - latency: 7.082881ms message: 'load-balancer-api-internal: resolved host name a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:30:21Z" - latency: 3.705939ms message: 'load-balancer-api-internal: tcp connection to a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:29:21Z" - latency: 8.50753ms message: 'load-balancer-api-internal: resolved host name a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:29:21Z" - latency: 4.94852ms message: 'load-balancer-api-internal: tcp connection to a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:28:21Z" - latency: 8.709129ms message: 'load-balancer-api-internal: resolved host name a0fd83f23ac89456fa6f77acf5ef98ab-6e36d02e449096ed.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T10:28:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T10:08:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-122-to-network-check-target-ip-10-0-128-206 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-122.ec2.internal uid: 6c0e3a17-8d49-419f-aa5e-ef58399cb596 resourceVersion: "19029" uid: adc78a7d-48ed-4b0e-847a-7750518a687d spec: sourcePod: network-check-source-7f44b6dd87-dzkx4 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T10:15:21Z" message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.001096ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:29:21Z" - latency: 1.643656ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:28:21Z" - latency: 1.900334ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:27:21Z" - latency: 1.51686ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:26:21Z" - latency: 1.974816ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:25:21Z" - latency: 1.796194ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:24:21Z" - latency: 1.721668ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:23:21Z" - latency: 1.932899ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:22:21Z" - latency: 1.770888ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:21:21Z" - latency: 1.524221ms message: 'network-check-target-ip-10-0-128-206: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:20:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T10:08:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-122-to-network-check-target-ip-10-0-129-122 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-122.ec2.internal uid: 6c0e3a17-8d49-419f-aa5e-ef58399cb596 resourceVersion: "19028" uid: 338cbc53-7bd4-4a29-8792-572dd8cdc3e3 spec: sourcePod: network-check-source-7f44b6dd87-dzkx4 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-28T10:15:21Z" message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.175902ms message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:29:21Z" - latency: 779.807µs message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:28:21Z" - latency: 1.481325ms message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:27:21Z" - latency: 881.166µs message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:26:21Z" - latency: 973.679µs message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:25:21Z" - latency: 868.874µs message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:24:21Z" - latency: 884.204µs message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:23:21Z" - latency: 819.716µs message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:22:21Z" - latency: 882.779µs message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:21:21Z" - latency: 990.82µs message: 'network-check-target-ip-10-0-129-122: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:20:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T10:08:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-122-to-network-check-target-ip-10-0-133-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-122.ec2.internal uid: 6c0e3a17-8d49-419f-aa5e-ef58399cb596 resourceVersion: "19030" uid: 011bf751-9770-47ac-b435-45e22e6ade1a spec: sourcePod: network-check-source-7f44b6dd87-dzkx4 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T10:15:21Z" message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.006972ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:29:21Z" - latency: 1.995728ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:28:21Z" - latency: 2.191233ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:27:21Z" - latency: 2.150202ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:26:21Z" - latency: 2.064162ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:25:21Z" - latency: 2.238021ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:24:21Z" - latency: 2.120083ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:23:21Z" - latency: 2.016164ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:22:21Z" - latency: 1.691657ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:21:21Z" - latency: 1.953224ms message: 'network-check-target-ip-10-0-133-103: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:20:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T10:08:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-122-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-122.ec2.internal uid: 6c0e3a17-8d49-419f-aa5e-ef58399cb596 resourceVersion: "20187" uid: 32ed7941-6b08-472e-990a-5172cfb15aa3 spec: sourcePod: network-check-source-7f44b6dd87-dzkx4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T10:14:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 761.686µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:32:21Z" - latency: 1.93749ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T10:32:21Z" - latency: 1.045038ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:31:21Z" - latency: 1.712152ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T10:31:21Z" - latency: 819.957µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:30:21Z" - latency: 1.804609ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T10:30:21Z" - latency: 728.981µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:29:21Z" - latency: 2.036647ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T10:29:21Z" - latency: 799.416µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T10:28:21Z" - latency: 1.77609ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T10:28:21Z" kind: List metadata: resourceVersion: ""