apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:02:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-195-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-195.ec2.internal uid: f311508a-6fdf-48d9-b2cd-6b58e9b99f75 resourceVersion: "31538" uid: 01c5f965-39ae-493a-9b0f-607fd8902026 spec: sourcePod: network-check-source-7b678d77c7-55pdr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T14:09:02Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.150555ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:44:02Z" - latency: 1.235727ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:43:02Z" - latency: 1.055545ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:42:02Z" - latency: 1.129591ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:41:02Z" - latency: 1.063108ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:40:02Z" - latency: 995.601µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:39:02Z" - latency: 1.089044ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:38:02Z" - latency: 1.024016ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:37:02Z" - latency: 906.953µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:36:02Z" - latency: 999.813µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:35:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:02:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-195-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-195.ec2.internal uid: f311508a-6fdf-48d9-b2cd-6b58e9b99f75 resourceVersion: "31540" uid: d33d5a82-f91b-4c84-b51a-1d24751d326d spec: sourcePod: network-check-source-7b678d77c7-55pdr targetEndpoint: aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T14:08:02Z" message: 'load-balancer-api-external: tcp connection to aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.146358ms message: 'load-balancer-api-external: tcp connection to aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:44:02Z" - latency: 6.99512ms message: 'load-balancer-api-external: resolved host name aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:44:02Z" - latency: 4.440592ms message: 'load-balancer-api-external: tcp connection to aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:43:02Z" - latency: 8.124688ms message: 'load-balancer-api-external: resolved host name aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:43:02Z" - latency: 5.220075ms message: 'load-balancer-api-external: tcp connection to aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:42:02Z" - latency: 7.835809ms message: 'load-balancer-api-external: resolved host name aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:42:02Z" - latency: 4.112433ms message: 'load-balancer-api-external: tcp connection to aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:41:02Z" - latency: 6.49954ms message: 'load-balancer-api-external: resolved host name aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:41:02Z" - latency: 4.89417ms message: 'load-balancer-api-external: tcp connection to aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:40:02Z" - latency: 7.427434ms message: 'load-balancer-api-external: resolved host name aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:40:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:02:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-195-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-195.ec2.internal uid: f311508a-6fdf-48d9-b2cd-6b58e9b99f75 resourceVersion: "31539" uid: c3610b11-773c-4ec4-8f57-452629c4108b spec: sourcePod: network-check-source-7b678d77c7-55pdr targetEndpoint: aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T14:08:02Z" message: 'load-balancer-api-internal: tcp connection to aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.764898ms message: 'load-balancer-api-internal: tcp connection to aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:44:02Z" - latency: 6.918077ms message: 'load-balancer-api-internal: resolved host name aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:44:02Z" - latency: 4.479915ms message: 'load-balancer-api-internal: tcp connection to aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:43:02Z" - latency: 8.021748ms message: 'load-balancer-api-internal: resolved host name aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:43:02Z" - latency: 5.21839ms message: 'load-balancer-api-internal: tcp connection to aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:42:02Z" - latency: 7.697309ms message: 'load-balancer-api-internal: resolved host name aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:42:02Z" - latency: 4.341028ms message: 'load-balancer-api-internal: tcp connection to aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:41:02Z" - latency: 6.307009ms message: 'load-balancer-api-internal: resolved host name aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:41:02Z" - latency: 5.224184ms message: 'load-balancer-api-internal: tcp connection to aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:40:02Z" - latency: 7.351404ms message: 'load-balancer-api-internal: resolved host name aa22c6e33ed9b4b378e2e3a1bf575a79-4f3c9e7b309d7e7f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T14:40:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:02:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-195-to-network-check-target-ip-10-0-128-129 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-195.ec2.internal uid: f311508a-6fdf-48d9-b2cd-6b58e9b99f75 resourceVersion: "31537" uid: 88aa43f7-deab-485f-8adb-bff959854503 spec: sourcePod: network-check-source-7b678d77c7-55pdr targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:09:02Z" message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.679267ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:44:02Z" - latency: 1.878344ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:43:02Z" - latency: 2.060205ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:42:02Z" - latency: 1.574658ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:41:02Z" - latency: 1.955103ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:40:02Z" - latency: 1.86491ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:39:02Z" - latency: 1.779586ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:38:02Z" - latency: 1.93168ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:37:02Z" - latency: 1.803665ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:36:02Z" - latency: 1.954677ms message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:35:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:02:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-195-to-network-check-target-ip-10-0-130-195 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-195.ec2.internal uid: f311508a-6fdf-48d9-b2cd-6b58e9b99f75 resourceVersion: "31534" uid: 8860fdae-4d8b-4fb9-93f1-5405a696dc89 spec: sourcePod: network-check-source-7b678d77c7-55pdr targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:09:02Z" message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 855.174µs message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:44:02Z" - latency: 1.477915ms message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:43:02Z" - latency: 839.877µs message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:42:02Z" - latency: 772.487µs message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:41:02Z" - latency: 975.519µs message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:40:02Z" - latency: 809.974µs message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:39:02Z" - latency: 809.24µs message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:38:02Z" - latency: 1.469774ms message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:37:02Z" - latency: 975.152µs message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:36:02Z" - latency: 899.014µs message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:35:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:02:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-195-to-network-check-target-ip-10-0-136-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-195.ec2.internal uid: f311508a-6fdf-48d9-b2cd-6b58e9b99f75 resourceVersion: "31535" uid: b62f24a8-4eb3-4191-a31f-fda597255885 spec: sourcePod: network-check-source-7b678d77c7-55pdr targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T14:09:02Z" message: 'network-check-target-ip-10-0-136-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.215015ms message: 'network-check-target-ip-10-0-136-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:44:02Z" - latency: 2.062757ms message: 'network-check-target-ip-10-0-136-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:43:02Z" - latency: 2.423901ms message: 'network-check-target-ip-10-0-136-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:42:02Z" - latency: 2.064328ms message: 'network-check-target-ip-10-0-136-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:41:02Z" - latency: 2.458134ms message: 'network-check-target-ip-10-0-136-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:40:02Z" - latency: 2.02006ms message: 'network-check-target-ip-10-0-136-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:39:02Z" - latency: 2.05975ms message: 'network-check-target-ip-10-0-136-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:38:02Z" - latency: 1.920061ms message: 'network-check-target-ip-10-0-136-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:37:02Z" - latency: 2.08237ms message: 'network-check-target-ip-10-0-136-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:36:02Z" - latency: 1.972481ms message: 'network-check-target-ip-10-0-136-109: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:35:02Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T14:02:00Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-195-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-195.ec2.internal uid: f311508a-6fdf-48d9-b2cd-6b58e9b99f75 resourceVersion: "31536" uid: b53841cc-b82e-4111-8b99-e7953ea612b6 spec: sourcePod: network-check-source-7b678d77c7-55pdr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T14:08:02Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 731.814µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:44:02Z" - latency: 1.852131ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:44:02Z" - latency: 868.91µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:43:02Z" - latency: 1.985488ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:43:02Z" - latency: 824.404µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:42:02Z" - latency: 1.819684ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:42:02Z" - latency: 753.481µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:41:02Z" - latency: 1.850876ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:41:02Z" - latency: 949.439µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T14:40:02Z" - latency: 1.725405ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T14:40:02Z" kind: List metadata: resourceVersion: ""