apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T15:54:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-161-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-161.ec2.internal uid: 400dfc75-9f2d-4729-8b36-a2b5a04826ab resourceVersion: "63286" uid: 29ccfafa-7cfa-4558-b7ca-ca1875065bdc spec: sourcePod: network-check-source-7bc5b6bf85-fjt5l targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T16:01:43Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 851.147µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:36:43Z" - latency: 1.327499ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:35:43Z" - latency: 884.57µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:34:43Z" - latency: 1.271442ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:33:43Z" - latency: 846.33µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:32:43Z" - latency: 980.397µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:31:43Z" - latency: 1.328628ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:30:43Z" - latency: 1.547057ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:29:43Z" - latency: 1.262454ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:28:43Z" - latency: 1.004795ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:27:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T15:54:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-161-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-161.ec2.internal uid: 400dfc75-9f2d-4729-8b36-a2b5a04826ab resourceVersion: "63288" uid: 78e803aa-0499-4aeb-a2c5-c9b964cec682 spec: sourcePod: network-check-source-7bc5b6bf85-fjt5l targetEndpoint: a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T16:00:43Z" message: 'load-balancer-api-external: tcp connection to a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.846591ms message: 'load-balancer-api-external: tcp connection to a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:36:43Z" - latency: 8.778725ms message: 'load-balancer-api-external: resolved host name a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T16:36:43Z" - latency: 3.96564ms message: 'load-balancer-api-external: tcp connection to a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:35:43Z" - latency: 20.376891ms message: 'load-balancer-api-external: resolved host name a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T16:35:43Z" - latency: 4.85612ms message: 'load-balancer-api-external: tcp connection to a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:34:43Z" - latency: 7.939793ms message: 'load-balancer-api-external: resolved host name a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T16:34:43Z" - latency: 5.85201ms message: 'load-balancer-api-external: tcp connection to a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:33:43Z" - latency: 9.39887ms message: 'load-balancer-api-external: resolved host name a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T16:33:43Z" - latency: 4.453892ms message: 'load-balancer-api-external: tcp connection to a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:32:43Z" - latency: 8.783639ms message: 'load-balancer-api-external: resolved host name a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T16:32:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T15:54:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-161-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-161.ec2.internal uid: 400dfc75-9f2d-4729-8b36-a2b5a04826ab resourceVersion: "63287" uid: 916d3ed8-8e99-4949-a656-73792dbe4895 spec: sourcePod: network-check-source-7bc5b6bf85-fjt5l targetEndpoint: a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T16:00:43Z" message: 'load-balancer-api-internal: tcp connection to a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.300882ms message: 'load-balancer-api-internal: tcp connection to a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:36:43Z" - latency: 8.833556ms message: 'load-balancer-api-internal: resolved host name a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T16:36:43Z" - latency: 3.862851ms message: 'load-balancer-api-internal: tcp connection to a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:35:43Z" - latency: 20.551632ms message: 'load-balancer-api-internal: resolved host name a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T16:35:43Z" - latency: 4.832632ms message: 'load-balancer-api-internal: tcp connection to a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:34:43Z" - latency: 8.030949ms message: 'load-balancer-api-internal: resolved host name a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T16:34:43Z" - latency: 4.544348ms message: 'load-balancer-api-internal: tcp connection to a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:33:43Z" - latency: 9.458093ms message: 'load-balancer-api-internal: resolved host name a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T16:33:43Z" - latency: 3.728586ms message: 'load-balancer-api-internal: tcp connection to a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:32:43Z" - latency: 8.8412ms message: 'load-balancer-api-internal: resolved host name a35ee617a4b69484da3c9322b02555ce-da10a5f43d5d3655.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T16:32:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T15:54:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-161-to-network-check-target-ip-10-0-130-166 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-161.ec2.internal uid: 400dfc75-9f2d-4729-8b36-a2b5a04826ab resourceVersion: "63284" uid: 676061a3-5ca0-44d5-a94b-4b5c4aec1f1a spec: sourcePod: network-check-source-7bc5b6bf85-fjt5l targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T16:01:43Z" message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.972481ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:36:43Z" - latency: 2.122387ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:35:43Z" - latency: 2.232946ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:34:43Z" - latency: 2.42767ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:33:43Z" - latency: 2.182041ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:32:43Z" - latency: 2.340622ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:31:43Z" - latency: 2.237401ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:30:43Z" - latency: 3.461746ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:29:43Z" - latency: 2.378917ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:28:43Z" - latency: 2.307261ms message: 'network-check-target-ip-10-0-130-166: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:27:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T15:54:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-161-to-network-check-target-ip-10-0-135-218 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-161.ec2.internal uid: 400dfc75-9f2d-4729-8b36-a2b5a04826ab resourceVersion: "63282" uid: 4481612d-8b6e-471b-a34e-8cbedc369b8b spec: sourcePod: network-check-source-7bc5b6bf85-fjt5l targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-23T16:01:43Z" message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.929196ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:36:43Z" - latency: 2.842598ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:35:43Z" - latency: 2.633707ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:34:43Z" - latency: 2.501408ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:33:43Z" - latency: 2.082844ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:32:43Z" - latency: 2.78919ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:31:43Z" - latency: 2.939022ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:30:43Z" - latency: 2.135537ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:29:43Z" - latency: 2.510197ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:28:43Z" - latency: 2.351348ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:27:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T15:54:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-161-to-network-check-target-ip-10-0-139-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-161.ec2.internal uid: 400dfc75-9f2d-4729-8b36-a2b5a04826ab resourceVersion: "63283" uid: 8f944277-24de-4b19-84d7-69596c3e101f spec: sourcePod: network-check-source-7bc5b6bf85-fjt5l targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-23T16:01:43Z" message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 815.211µs message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:36:43Z" - latency: 753.249µs message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:35:43Z" - latency: 1.073224ms message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:34:43Z" - latency: 842.902µs message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:33:43Z" - latency: 1.143586ms message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:32:43Z" - latency: 829.288µs message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:31:43Z" - latency: 1.595727ms message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:30:43Z" - latency: 1.118132ms message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:29:43Z" - latency: 1.512081ms message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:28:43Z" - latency: 1.208226ms message: 'network-check-target-ip-10-0-139-161: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:27:43Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T15:54:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-161-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-161.ec2.internal uid: 400dfc75-9f2d-4729-8b36-a2b5a04826ab resourceVersion: "63285" uid: bba422e8-ef6f-47ee-a800-555f96a50a8b spec: sourcePod: network-check-source-7bc5b6bf85-fjt5l targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T16:00:43Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.2042ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:36:43Z" - latency: 1.664303ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T16:36:43Z" - latency: 1.080224ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:35:43Z" - latency: 2.039899ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T16:35:43Z" - latency: 794.067µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:34:43Z" - latency: 1.611904ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T16:34:43Z" - latency: 1.061761ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:33:43Z" - latency: 1.712487ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T16:33:43Z" - latency: 927.029µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T16:32:43Z" - latency: 1.624629ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T16:32:43Z" kind: List metadata: resourceVersion: ""