apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T12:49:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-90-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-90.ec2.internal uid: 14ab5bcc-7f25-4950-845c-a26f1b810627 resourceVersion: "60541" uid: 1b84c9bc-7e7d-42b2-8aa0-fe27a7011839 spec: sourcePod: network-check-source-869dcfcdcd-w7kfb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-10T12:56:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.023929ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:31:22Z" - latency: 850.922µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:30:22Z" - latency: 954.753µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:29:22Z" - latency: 1.070815ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:28:22Z" - latency: 947.952µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:27:22Z" - latency: 821.991µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:26:22Z" - latency: 1.434778ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:25:22Z" - latency: 864.072µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:24:22Z" - latency: 1.158319ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:23:22Z" - latency: 1.068626ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:22:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T12:49:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-90-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-90.ec2.internal uid: 14ab5bcc-7f25-4950-845c-a26f1b810627 resourceVersion: "60542" uid: 435f1a2d-0975-4073-be8d-3477c93fca17 spec: sourcePod: network-check-source-869dcfcdcd-w7kfb targetEndpoint: a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T12:55:22Z" message: 'load-balancer-api-external: tcp connection to a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.208743ms message: 'load-balancer-api-external: tcp connection to a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:31:22Z" - latency: 6.151153ms message: 'load-balancer-api-external: resolved host name a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:31:22Z" - latency: 6.935234ms message: 'load-balancer-api-external: tcp connection to a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:30:22Z" - latency: 7.674647ms message: 'load-balancer-api-external: resolved host name a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:30:22Z" - latency: 4.212331ms message: 'load-balancer-api-external: tcp connection to a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:29:22Z" - latency: 7.193447ms message: 'load-balancer-api-external: resolved host name a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:29:22Z" - latency: 5.165654ms message: 'load-balancer-api-external: tcp connection to a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:28:22Z" - latency: 7.118197ms message: 'load-balancer-api-external: resolved host name a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:28:22Z" - latency: 4.264538ms message: 'load-balancer-api-external: tcp connection to a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:27:22Z" - latency: 6.526732ms message: 'load-balancer-api-external: resolved host name a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:27:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T12:49:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-90-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-90.ec2.internal uid: 14ab5bcc-7f25-4950-845c-a26f1b810627 resourceVersion: "60543" uid: f9f47643-16b3-4495-9e8a-73658f1804d1 spec: sourcePod: network-check-source-869dcfcdcd-w7kfb targetEndpoint: a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-10T12:55:22Z" message: 'load-balancer-api-internal: tcp connection to a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.730518ms message: 'load-balancer-api-internal: tcp connection to a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:31:22Z" - latency: 6.193784ms message: 'load-balancer-api-internal: resolved host name a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:31:22Z" - latency: 5.477259ms message: 'load-balancer-api-internal: tcp connection to a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:30:22Z" - latency: 7.77657ms message: 'load-balancer-api-internal: resolved host name a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:30:22Z" - latency: 4.201091ms message: 'load-balancer-api-internal: tcp connection to a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:29:22Z" - latency: 7.132056ms message: 'load-balancer-api-internal: resolved host name a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:29:22Z" - latency: 5.127955ms message: 'load-balancer-api-internal: tcp connection to a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:28:22Z" - latency: 7.101881ms message: 'load-balancer-api-internal: resolved host name a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:28:22Z" - latency: 4.238526ms message: 'load-balancer-api-internal: tcp connection to a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:27:22Z" - latency: 6.629317ms message: 'load-balancer-api-internal: resolved host name a6586de5180e14f63a5bfb0a4219ea9a-1fb53a9cc0638331.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-10T13:27:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T12:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-90-to-network-check-target-ip-10-0-134-90 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-90.ec2.internal uid: 14ab5bcc-7f25-4950-845c-a26f1b810627 resourceVersion: "60537" uid: 84ef6e65-c8a9-4a52-b57b-b85284697793 spec: sourcePod: network-check-source-869dcfcdcd-w7kfb targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-10T12:56:22Z" message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 886.467µs message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:31:22Z" - latency: 1.227934ms message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:30:22Z" - latency: 900.448µs message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:29:22Z" - latency: 944.725µs message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:28:22Z" - latency: 1.407759ms message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:27:22Z" - latency: 875.8µs message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:26:22Z" - latency: 710.623µs message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:25:22Z" - latency: 1.0786ms message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:24:22Z" - latency: 892.91µs message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:23:22Z" - latency: 877.026µs message: 'network-check-target-ip-10-0-134-90: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:22:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T12:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-90-to-network-check-target-ip-10-0-135-152 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-90.ec2.internal uid: 14ab5bcc-7f25-4950-845c-a26f1b810627 resourceVersion: "60539" uid: d6aee8cf-ca3c-4e61-862e-46b6aa879d77 spec: sourcePod: network-check-source-869dcfcdcd-w7kfb targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-10T12:56:22Z" message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.243219ms message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:31:22Z" - latency: 2.132164ms message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:30:22Z" - latency: 2.360923ms message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:29:22Z" - latency: 2.074706ms message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:28:22Z" - latency: 2.542498ms message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:27:22Z" - latency: 2.299713ms message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:26:22Z" - latency: 2.551867ms message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:25:22Z" - latency: 2.024657ms message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:24:22Z" - latency: 2.164086ms message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:23:22Z" - latency: 2.089881ms message: 'network-check-target-ip-10-0-135-152: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:22:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T12:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-90-to-network-check-target-ip-10-0-143-162 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-90.ec2.internal uid: 14ab5bcc-7f25-4950-845c-a26f1b810627 resourceVersion: "60538" uid: fe23af3a-9dcc-41fc-b262-31f03f0ff72e spec: sourcePod: network-check-source-869dcfcdcd-w7kfb targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-10T12:56:22Z" message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.304769ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:31:22Z" - latency: 2.062358ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:30:22Z" - latency: 2.345525ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:29:22Z" - latency: 2.062987ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:28:22Z" - latency: 2.113031ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:27:22Z" - latency: 2.001472ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:26:22Z" - latency: 2.189199ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:25:22Z" - latency: 2.145235ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:24:22Z" - latency: 2.389802ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:23:22Z" - latency: 2.296131ms message: 'network-check-target-ip-10-0-143-162: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:22:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-10T12:49:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-90-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-90.ec2.internal uid: 14ab5bcc-7f25-4950-845c-a26f1b810627 resourceVersion: "60540" uid: 4e312011-0e10-46a8-a926-5cdd7b2825ec spec: sourcePod: network-check-source-869dcfcdcd-w7kfb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-10T12:55:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.109952ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:31:22Z" - latency: 1.714378ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T13:31:22Z" - latency: 824.863µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:30:22Z" - latency: 1.79833ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T13:30:22Z" - latency: 790.682µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:29:22Z" - latency: 2.068281ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T13:29:22Z" - latency: 808.947µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:28:22Z" - latency: 1.7436ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T13:28:22Z" - latency: 842.093µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-10T13:27:22Z" - latency: 1.900202ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-10T13:27:22Z" kind: List metadata: resourceVersion: ""