apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T03:19:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-194-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-194.ec2.internal uid: 9f3db8f4-de31-4f0d-b351-ad35cfc59fee resourceVersion: "51812" uid: db9e7ea4-2eb3-4234-b249-c54acbff950b spec: sourcePod: network-check-source-6947749cfc-5tw5w targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-14T03:26:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 778.956µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:54:08Z" - latency: 816.32µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:53:08Z" - latency: 783.964µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:52:08Z" - latency: 821.346µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:51:08Z" - latency: 984.456µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:50:08Z" - latency: 825.727µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:49:08Z" - latency: 790.386µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:48:08Z" - latency: 1.332117ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:47:08Z" - latency: 1.30897ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:46:08Z" - latency: 1.47608ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:45:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T03:19:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-194-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-194.ec2.internal uid: 9f3db8f4-de31-4f0d-b351-ad35cfc59fee resourceVersion: "46324" uid: b3c03371-f169-4bbe-bb3a-45acc60104b7 spec: sourcePod: network-check-source-6947749cfc-5tw5w targetEndpoint: aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-14T03:25:08Z" message: 'load-balancer-api-external: tcp connection to aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.452221ms message: 'load-balancer-api-external: tcp connection to aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:49:08Z" - latency: 11.709335ms message: 'load-balancer-api-external: resolved host name aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T03:49:08Z" - latency: 4.275858ms message: 'load-balancer-api-external: tcp connection to aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:48:08Z" - latency: 8.590616ms message: 'load-balancer-api-external: resolved host name aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T03:48:08Z" - latency: 5.556777ms message: 'load-balancer-api-external: tcp connection to aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:47:08Z" - latency: 8.099439ms message: 'load-balancer-api-external: resolved host name aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T03:47:08Z" - latency: 6.205864ms message: 'load-balancer-api-external: tcp connection to aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:46:08Z" - latency: 7.411706ms message: 'load-balancer-api-external: resolved host name aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T03:46:08Z" - latency: 3.689389ms message: 'load-balancer-api-external: tcp connection to aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:45:08Z" - latency: 8.592731ms message: 'load-balancer-api-external: resolved host name aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T03:45:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T03:19:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-194-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-194.ec2.internal uid: 9f3db8f4-de31-4f0d-b351-ad35cfc59fee resourceVersion: "46325" uid: 95ea8422-fa81-481e-984f-0a8a4077afcc spec: sourcePod: network-check-source-6947749cfc-5tw5w targetEndpoint: aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-14T03:25:08Z" message: 'load-balancer-api-internal: tcp connection to aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.507736ms message: 'load-balancer-api-internal: tcp connection to aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:49:08Z" - latency: 11.634551ms message: 'load-balancer-api-internal: resolved host name aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T03:49:08Z" - latency: 5.104925ms message: 'load-balancer-api-internal: tcp connection to aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:48:08Z" - latency: 8.566345ms message: 'load-balancer-api-internal: resolved host name aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T03:48:08Z" - latency: 5.518698ms message: 'load-balancer-api-internal: tcp connection to aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:47:08Z" - latency: 8.065932ms message: 'load-balancer-api-internal: resolved host name aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T03:47:08Z" - latency: 5.467459ms message: 'load-balancer-api-internal: tcp connection to aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:46:08Z" - latency: 7.375199ms message: 'load-balancer-api-internal: resolved host name aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T03:46:08Z" - latency: 3.516088ms message: 'load-balancer-api-internal: tcp connection to aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:45:08Z" - latency: 8.571502ms message: 'load-balancer-api-internal: resolved host name aabc19e34964e4a7bb2d6960945e9ea2-710c0f2faf4059ec.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T03:45:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T03:19:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-194-to-network-check-target-ip-10-0-137-82 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-194.ec2.internal uid: 9f3db8f4-de31-4f0d-b351-ad35cfc59fee resourceVersion: "51810" uid: b14de203-8853-43b2-acf6-29c6e469a20b spec: sourcePod: network-check-source-6947749cfc-5tw5w targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-14T03:26:08Z" message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.231569ms message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:54:08Z" - latency: 2.437486ms message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:53:08Z" - latency: 2.113634ms message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:52:08Z" - latency: 2.528615ms message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:51:08Z" - latency: 2.230389ms message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:50:08Z" - latency: 2.173162ms message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:49:08Z" - latency: 1.935531ms message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:48:08Z" - latency: 2.28916ms message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:47:08Z" - latency: 2.019708ms message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:46:08Z" - latency: 2.454165ms message: 'network-check-target-ip-10-0-137-82: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:45:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T03:19:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-194-to-network-check-target-ip-10-0-138-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-194.ec2.internal uid: 9f3db8f4-de31-4f0d-b351-ad35cfc59fee resourceVersion: "51811" uid: 004cb019-9a64-4a4a-9259-46846e74c25c spec: sourcePod: network-check-source-6947749cfc-5tw5w targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-14T03:26:08Z" message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.267854ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:54:08Z" - latency: 2.265285ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:53:08Z" - latency: 1.865508ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:52:08Z" - latency: 1.989659ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:51:08Z" - latency: 2.206182ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:50:08Z" - latency: 2.197945ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:49:08Z" - latency: 2.024288ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:48:08Z" - latency: 2.236228ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:47:08Z" - latency: 1.916793ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:46:08Z" - latency: 2.243524ms message: 'network-check-target-ip-10-0-138-133: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:45:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T03:19:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-194-to-network-check-target-ip-10-0-141-194 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-194.ec2.internal uid: 9f3db8f4-de31-4f0d-b351-ad35cfc59fee resourceVersion: "51809" uid: ad0f2360-e70a-4a73-90ce-c6fe2a256a6d spec: sourcePod: network-check-source-6947749cfc-5tw5w targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-14T03:26:08Z" message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.309829ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:54:08Z" - latency: 967.604µs message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:53:08Z" - latency: 791.954µs message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:52:08Z" - latency: 952.695µs message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:51:08Z" - latency: 981.295µs message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:50:08Z" - latency: 1.176956ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:49:08Z" - latency: 836.225µs message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:48:08Z" - latency: 1.006096ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:47:08Z" - latency: 819.712µs message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:46:08Z" - latency: 866.478µs message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:45:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T03:19:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-194-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-194.ec2.internal uid: 9f3db8f4-de31-4f0d-b351-ad35cfc59fee resourceVersion: "46323" uid: c41029e2-81ea-4630-acbd-a3d93a37489e spec: sourcePod: network-check-source-6947749cfc-5tw5w targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-14T03:25:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 854.672µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:49:08Z" - latency: 1.826776ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T03:49:08Z" - latency: 925.378µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:48:08Z" - latency: 1.893384ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T03:48:08Z" - latency: 1.080973ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:47:08Z" - latency: 1.711978ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T03:47:08Z" - latency: 913.273µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:46:08Z" - latency: 2.490771ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T03:46:08Z" - latency: 968.476µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T03:45:08Z" - latency: 1.757206ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T03:45:08Z" kind: List metadata: resourceVersion: ""