apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T09:39:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-109-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-109.ec2.internal uid: b5d704be-8e62-43fd-b1bf-ca81c1719b9c resourceVersion: "22850" uid: 59ed7e93-1982-4cce-b946-3a29690d58d9 spec: sourcePod: network-check-source-dbd9cf844-brxsz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-09T09:46:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.211252ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:07:44Z" - latency: 931.505µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:06:44Z" - latency: 999.306µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:05:44Z" - latency: 962.016µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:04:44Z" - latency: 1.008935ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:03:44Z" - latency: 1.013203ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:02:44Z" - latency: 879.909µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:01:44Z" - latency: 1.051816ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:00:44Z" - latency: 990.086µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T09:59:44Z" - latency: 812.357µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-09T09:58:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T09:39:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-109-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-109.ec2.internal uid: b5d704be-8e62-43fd-b1bf-ca81c1719b9c resourceVersion: "23621" uid: cf4e041c-c33a-4f31-862a-e4ce8037db01 spec: sourcePod: network-check-source-dbd9cf844-brxsz targetEndpoint: aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T09:45:44Z" message: 'load-balancer-api-external: tcp connection to aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.459792ms message: 'load-balancer-api-external: tcp connection to aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:09:44Z" - latency: 8.696387ms message: 'load-balancer-api-external: resolved host name aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:09:44Z" - latency: 4.123055ms message: 'load-balancer-api-external: tcp connection to aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:08:44Z" - latency: 7.697943ms message: 'load-balancer-api-external: resolved host name aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:08:44Z" - latency: 4.875684ms message: 'load-balancer-api-external: tcp connection to aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:07:44Z" - latency: 8.906913ms message: 'load-balancer-api-external: resolved host name aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:07:44Z" - latency: 5.510294ms message: 'load-balancer-api-external: tcp connection to aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:06:44Z" - latency: 11.844815ms message: 'load-balancer-api-external: resolved host name aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:06:44Z" - latency: 5.004311ms message: 'load-balancer-api-external: tcp connection to aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:05:44Z" - latency: 8.149146ms message: 'load-balancer-api-external: resolved host name aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:05:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T09:39:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-109-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-109.ec2.internal uid: b5d704be-8e62-43fd-b1bf-ca81c1719b9c resourceVersion: "23622" uid: b837364f-5d6a-46db-86e8-0d57ac900b79 spec: sourcePod: network-check-source-dbd9cf844-brxsz targetEndpoint: aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-09T09:45:44Z" message: 'load-balancer-api-internal: tcp connection to aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.579315ms message: 'load-balancer-api-internal: tcp connection to aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:09:44Z" - latency: 8.787922ms message: 'load-balancer-api-internal: resolved host name aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:09:44Z" - latency: 4.104328ms message: 'load-balancer-api-internal: tcp connection to aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:08:44Z" - latency: 7.817069ms message: 'load-balancer-api-internal: resolved host name aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:08:44Z" - latency: 4.866046ms message: 'load-balancer-api-internal: tcp connection to aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:07:44Z" - latency: 9.010538ms message: 'load-balancer-api-internal: resolved host name aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:07:44Z" - latency: 5.479517ms message: 'load-balancer-api-internal: tcp connection to aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:06:44Z" - latency: 11.995147ms message: 'load-balancer-api-internal: resolved host name aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:06:44Z" - latency: 5.044991ms message: 'load-balancer-api-internal: tcp connection to aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:05:44Z" - latency: 8.187275ms message: 'load-balancer-api-internal: resolved host name aa289dfd165b4403ebe1cea095c5ccdb-15bd476f03ce17f2.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-09T10:05:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T09:39:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-109-to-network-check-target-ip-10-0-131-231 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-109.ec2.internal uid: b5d704be-8e62-43fd-b1bf-ca81c1719b9c resourceVersion: "22848" uid: f30774fe-4d00-4ad6-9e05-ac08a370468d spec: sourcePod: network-check-source-dbd9cf844-brxsz targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T09:46:44Z" message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.136841ms message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:07:44Z" - latency: 2.21223ms message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:06:44Z" - latency: 2.004481ms message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:05:44Z" - latency: 1.79884ms message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:04:44Z" - latency: 2.366301ms message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:03:44Z" - latency: 2.258541ms message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:02:44Z" - latency: 2.033745ms message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:01:44Z" - latency: 2.178093ms message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:00:44Z" - latency: 1.810744ms message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T09:59:44Z" - latency: 2.225115ms message: 'network-check-target-ip-10-0-131-231: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T09:58:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T09:39:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-109-to-network-check-target-ip-10-0-133-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-109.ec2.internal uid: b5d704be-8e62-43fd-b1bf-ca81c1719b9c resourceVersion: "22847" uid: 3b0962ea-6f60-4484-be14-cb835268b24c spec: sourcePod: network-check-source-dbd9cf844-brxsz targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-09T09:46:44Z" message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 831.282µs message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:07:44Z" - latency: 1.183803ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:06:44Z" - latency: 952.368µs message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:05:44Z" - latency: 830.645µs message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:04:44Z" - latency: 1.2397ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:03:44Z" - latency: 1.366295ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:02:44Z" - latency: 931.037µs message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:01:44Z" - latency: 1.250694ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:00:44Z" - latency: 1.01235ms message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T09:59:44Z" - latency: 980.181µs message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T09:58:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T09:39:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-109-to-network-check-target-ip-10-0-135-66 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-109.ec2.internal uid: b5d704be-8e62-43fd-b1bf-ca81c1719b9c resourceVersion: "22849" uid: e69e6551-f282-4168-977f-99f4ec1c3726 spec: sourcePod: network-check-source-dbd9cf844-brxsz targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-09T09:46:44Z" message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.644202ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:07:44Z" - latency: 2.28834ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:06:44Z" - latency: 2.628644ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:05:44Z" - latency: 2.474433ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:04:44Z" - latency: 2.427318ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:03:44Z" - latency: 2.449206ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:02:44Z" - latency: 2.093811ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:01:44Z" - latency: 2.163416ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:00:44Z" - latency: 2.399798ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T09:59:44Z" - latency: 2.398821ms message: 'network-check-target-ip-10-0-135-66: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-09T09:58:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-09T09:39:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-133-109-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-133-109.ec2.internal uid: b5d704be-8e62-43fd-b1bf-ca81c1719b9c resourceVersion: "23619" uid: b4d4daa0-579a-475d-8189-8767dafd9e35 spec: sourcePod: network-check-source-dbd9cf844-brxsz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-09T09:45:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 930.071µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:09:44Z" - latency: 1.679672ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T10:09:44Z" - latency: 1.065974ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:08:44Z" - latency: 1.653059ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T10:08:44Z" - latency: 889.974µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:07:44Z" - latency: 1.762509ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T10:07:44Z" - latency: 794.848µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:06:44Z" - latency: 1.829956ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T10:06:44Z" - latency: 1.133779ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-09T10:05:44Z" - latency: 1.840791ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-09T10:05:44Z" kind: List metadata: resourceVersion: ""