apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T19:20:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-26-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-26.ec2.internal uid: e52c54b1-d2e7-4f25-9b8f-53b114a2f1e7 resourceVersion: "54818" uid: b3c574b3-22fc-4d14-9db0-abf80238c2b9 spec: sourcePod: network-check-source-685456655f-8lvlx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-10T19:27:06Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.414808ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:48:06Z" - latency: 1.543453ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:47:06Z" - latency: 1.1671ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:46:06Z" - latency: 1.202407ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:45:06Z" - latency: 1.256679ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:44:06Z" - latency: 1.208871ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:43:06Z" - latency: 1.079432ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:42:06Z" - latency: 1.249383ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:41:06Z" - latency: 982.279µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:40:06Z" - latency: 1.130882ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T19:20:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-26-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-26.ec2.internal uid: e52c54b1-d2e7-4f25-9b8f-53b114a2f1e7 resourceVersion: "56384" uid: 50477c04-e3be-4c95-83e8-bbc59fde0461 spec: sourcePod: network-check-source-685456655f-8lvlx targetEndpoint: a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T19:26:06Z" message: 'load-balancer-api-external: tcp connection to a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.092379ms message: 'load-balancer-api-external: tcp connection to a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:50:06Z" - latency: 8.431279ms message: 'load-balancer-api-external: resolved host name a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T19:50:06Z" - latency: 6.168046ms message: 'load-balancer-api-external: tcp connection to a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:49:06Z" - latency: 8.418848ms message: 'load-balancer-api-external: resolved host name a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T19:49:06Z" - latency: 6.266886ms message: 'load-balancer-api-external: tcp connection to a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:48:06Z" - latency: 9.108197ms message: 'load-balancer-api-external: resolved host name a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T19:48:06Z" - latency: 6.034064ms message: 'load-balancer-api-external: tcp connection to a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:47:06Z" - latency: 9.309927ms message: 'load-balancer-api-external: resolved host name a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T19:47:06Z" - latency: 5.696843ms message: 'load-balancer-api-external: tcp connection to a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:46:06Z" - latency: 10.413318ms message: 'load-balancer-api-external: resolved host name a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T19:46:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T19:20:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-26-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-26.ec2.internal uid: e52c54b1-d2e7-4f25-9b8f-53b114a2f1e7 resourceVersion: "56385" uid: e1e83569-b9ea-48c9-8c7a-965498eeb47c spec: sourcePod: network-check-source-685456655f-8lvlx targetEndpoint: a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-10T19:26:06Z" message: 'load-balancer-api-internal: tcp connection to a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.167893ms message: 'load-balancer-api-internal: tcp connection to a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:50:06Z" - latency: 8.339268ms message: 'load-balancer-api-internal: resolved host name a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T19:50:06Z" - latency: 3.358157ms message: 'load-balancer-api-internal: tcp connection to a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:49:06Z" - latency: 8.326938ms message: 'load-balancer-api-internal: resolved host name a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T19:49:06Z" - latency: 6.302589ms message: 'load-balancer-api-internal: tcp connection to a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:48:06Z" - latency: 9.007161ms message: 'load-balancer-api-internal: resolved host name a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T19:48:06Z" - latency: 5.972125ms message: 'load-balancer-api-internal: tcp connection to a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:47:06Z" - latency: 9.203475ms message: 'load-balancer-api-internal: resolved host name a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T19:47:06Z" - latency: 5.739114ms message: 'load-balancer-api-internal: tcp connection to a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:46:06Z" - latency: 10.326346ms message: 'load-balancer-api-internal: resolved host name a981a2895ea5f4c37bcfc3c98971dcf6-c45a0604d3e89718.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-10T19:46:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T19:20:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-26-to-network-check-target-ip-10-0-129-230 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-26.ec2.internal uid: e52c54b1-d2e7-4f25-9b8f-53b114a2f1e7 resourceVersion: "54815" uid: f3635763-dde4-4db4-9f66-b7c5e3ea0a99 spec: sourcePod: network-check-source-685456655f-8lvlx targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-10T19:27:06Z" message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.230772ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:48:06Z" - latency: 2.895628ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:47:06Z" - latency: 2.576489ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:46:06Z" - latency: 2.348053ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:45:06Z" - latency: 2.338434ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:44:06Z" - latency: 1.731467ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:43:06Z" - latency: 2.475935ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:42:06Z" - latency: 2.723288ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:41:06Z" - latency: 1.939147ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:40:06Z" - latency: 2.785442ms message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T19:20:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-26-to-network-check-target-ip-10-0-130-178 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-26.ec2.internal uid: e52c54b1-d2e7-4f25-9b8f-53b114a2f1e7 resourceVersion: "54816" uid: 4fca124b-1c6b-45a9-8531-77a4d0bbecce spec: sourcePod: network-check-source-685456655f-8lvlx targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-10T19:27:06Z" message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.303582ms message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:48:06Z" - latency: 2.4465ms message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:47:06Z" - latency: 2.409509ms message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:46:06Z" - latency: 2.393003ms message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:45:06Z" - latency: 2.366335ms message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:44:06Z" - latency: 2.091281ms message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:43:06Z" - latency: 2.274061ms message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:42:06Z" - latency: 2.450513ms message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:41:06Z" - latency: 1.925457ms message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:40:06Z" - latency: 2.452513ms message: 'network-check-target-ip-10-0-130-178: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T19:20:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-26-to-network-check-target-ip-10-0-134-26 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-26.ec2.internal uid: e52c54b1-d2e7-4f25-9b8f-53b114a2f1e7 resourceVersion: "54814" uid: c4570966-a908-4a41-9b69-75a0976eafea spec: sourcePod: network-check-source-685456655f-8lvlx targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-09-10T19:27:06Z" message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 991.613µs message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:48:06Z" - latency: 912.519µs message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:47:06Z" - latency: 1.000742ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:46:06Z" - latency: 1.106859ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:45:06Z" - latency: 1.28953ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:44:06Z" - latency: 1.035707ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:43:06Z" - latency: 993.95µs message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:42:06Z" - latency: 1.423403ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:41:06Z" - latency: 1.201582ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:40:06Z" - latency: 1.792339ms message: 'network-check-target-ip-10-0-134-26: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:39:06Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-10T19:20:05Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-26-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-26.ec2.internal uid: e52c54b1-d2e7-4f25-9b8f-53b114a2f1e7 resourceVersion: "56383" uid: 8a91e46b-0aab-4f1f-be3c-9a4f3d8d41dc spec: sourcePod: network-check-source-685456655f-8lvlx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-10T19:26:06Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.002856ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:50:06Z" - latency: 1.811313ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T19:50:06Z" - latency: 882.596µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:49:06Z" - latency: 2.204678ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T19:49:06Z" - latency: 911.79µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:48:06Z" - latency: 1.91397ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T19:48:06Z" - latency: 999.632µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:47:06Z" - latency: 1.623502ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T19:47:06Z" - latency: 962.186µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-10T19:46:06Z" - latency: 1.868778ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-10T19:46:06Z" kind: List metadata: resourceVersion: ""