apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:53:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-108-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-108.ec2.internal uid: f143c5a7-4719-40b0-ae46-602ed7bd8a03 resourceVersion: "53172" uid: f441aef9-5507-4e17-a540-a4abc74f5482 spec: sourcePod: network-check-source-685456655f-r87s8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-08T17:00:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.310881ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:21:57Z" - latency: 986.51µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:20:57Z" - latency: 928.999µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:19:57Z" - latency: 1.161701ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:18:57Z" - latency: 1.116224ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:17:57Z" - latency: 1.140306ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:16:57Z" - latency: 1.233032ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:15:57Z" - latency: 1.807055ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:14:57Z" - latency: 1.026354ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:13:57Z" - latency: 982.728µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:12:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:53:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-108-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-108.ec2.internal uid: f143c5a7-4719-40b0-ae46-602ed7bd8a03 resourceVersion: "54670" uid: 69a3818c-9a3d-42e8-a8de-8fc6f4698e0f spec: sourcePod: network-check-source-685456655f-r87s8 targetEndpoint: a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T16:59:57Z" message: 'load-balancer-api-external: tcp connection to a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.899038ms message: 'load-balancer-api-external: tcp connection to a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:23:57Z" - latency: 7.454512ms message: 'load-balancer-api-external: resolved host name a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T17:23:57Z" - latency: 3.663635ms message: 'load-balancer-api-external: tcp connection to a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:22:57Z" - latency: 9.577665ms message: 'load-balancer-api-external: resolved host name a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T17:22:57Z" - latency: 5.167554ms message: 'load-balancer-api-external: tcp connection to a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:21:57Z" - latency: 12.688606ms message: 'load-balancer-api-external: resolved host name a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T17:21:57Z" - latency: 4.581928ms message: 'load-balancer-api-external: tcp connection to a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:20:57Z" - latency: 7.647977ms message: 'load-balancer-api-external: resolved host name a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T17:20:57Z" - latency: 4.847319ms message: 'load-balancer-api-external: tcp connection to a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:19:57Z" - latency: 8.747519ms message: 'load-balancer-api-external: resolved host name a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T17:19:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:53:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-108-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-108.ec2.internal uid: f143c5a7-4719-40b0-ae46-602ed7bd8a03 resourceVersion: "54671" uid: ceee0f24-ca4c-49ee-a07e-21dd5ba4e38e spec: sourcePod: network-check-source-685456655f-r87s8 targetEndpoint: a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-08T16:59:57Z" message: 'load-balancer-api-internal: tcp connection to a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.867921ms message: 'load-balancer-api-internal: tcp connection to a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:23:57Z" - latency: 7.298554ms message: 'load-balancer-api-internal: resolved host name a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T17:23:57Z" - latency: 3.695377ms message: 'load-balancer-api-internal: tcp connection to a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:22:57Z" - latency: 9.540522ms message: 'load-balancer-api-internal: resolved host name a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T17:22:57Z" - latency: 5.1672ms message: 'load-balancer-api-internal: tcp connection to a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:21:57Z" - latency: 12.710405ms message: 'load-balancer-api-internal: resolved host name a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T17:21:57Z" - latency: 5.126351ms message: 'load-balancer-api-internal: tcp connection to a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:20:57Z" - latency: 7.695702ms message: 'load-balancer-api-internal: resolved host name a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T17:20:57Z" - latency: 4.811811ms message: 'load-balancer-api-internal: tcp connection to a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:19:57Z" - latency: 8.86087ms message: 'load-balancer-api-internal: resolved host name a3069d991e0e44e2693feb69d4e6c818-9c6966bee8458985.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-08T17:19:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:53:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-108-to-network-check-target-ip-10-0-132-198 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-108.ec2.internal uid: f143c5a7-4719-40b0-ae46-602ed7bd8a03 resourceVersion: "53170" uid: 832a16ef-e467-40a2-845b-188fdae71995 spec: sourcePod: network-check-source-685456655f-r87s8 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-08T17:00:57Z" message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.754028ms message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:21:57Z" - latency: 2.449216ms message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:20:57Z" - latency: 3.081553ms message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:19:57Z" - latency: 2.486176ms message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:18:57Z" - latency: 2.191625ms message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:17:57Z" - latency: 2.478931ms message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:16:57Z" - latency: 2.444155ms message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:15:57Z" - latency: 2.494066ms message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:14:57Z" - latency: 2.722385ms message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:13:57Z" - latency: 2.050079ms message: 'network-check-target-ip-10-0-132-198: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:12:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:53:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-108-to-network-check-target-ip-10-0-133-106 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-108.ec2.internal uid: f143c5a7-4719-40b0-ae46-602ed7bd8a03 resourceVersion: "53171" uid: 344c0569-1cbd-4d98-aaea-2bcd8ae4db42 spec: sourcePod: network-check-source-685456655f-r87s8 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-08T17:00:57Z" message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.94148ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:21:57Z" - latency: 1.989338ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:20:57Z" - latency: 2.410011ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:19:57Z" - latency: 2.465074ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:18:57Z" - latency: 2.52933ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:17:57Z" - latency: 2.610401ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:16:57Z" - latency: 2.82754ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:15:57Z" - latency: 2.301488ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:14:57Z" - latency: 2.51908ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:13:57Z" - latency: 2.39581ms message: 'network-check-target-ip-10-0-133-106: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:12:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:53:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-108-to-network-check-target-ip-10-0-137-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-108.ec2.internal uid: f143c5a7-4719-40b0-ae46-602ed7bd8a03 resourceVersion: "53169" uid: 26d8f191-f7bc-4213-bccc-a88925e0f4d3 spec: sourcePod: network-check-source-685456655f-r87s8 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-08T17:00:57Z" message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.406561ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:21:57Z" - latency: 1.118119ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:20:57Z" - latency: 1.079706ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:19:57Z" - latency: 1.017954ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:18:57Z" - latency: 1.527993ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:17:57Z" - latency: 992.369µs message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:16:57Z" - latency: 1.205404ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:15:57Z" - latency: 954.643µs message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:14:57Z" - latency: 1.077662ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:13:57Z" - latency: 1.00961ms message: 'network-check-target-ip-10-0-137-108: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:12:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-08T16:53:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-108-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-108.ec2.internal uid: f143c5a7-4719-40b0-ae46-602ed7bd8a03 resourceVersion: "54669" uid: 4800804e-5c7d-4a6f-8e4f-c0afd197268a spec: sourcePod: network-check-source-685456655f-r87s8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-08T16:59:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.013387ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:23:57Z" - latency: 2.169534ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T17:23:57Z" - latency: 1.291945ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:22:57Z" - latency: 1.881895ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T17:22:57Z" - latency: 1.235384ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:21:57Z" - latency: 1.914059ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T17:21:57Z" - latency: 1.008718ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:20:57Z" - latency: 1.849751ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T17:20:57Z" - latency: 858.663µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-08T17:19:57Z" - latency: 1.860777ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-08T17:19:57Z" kind: List metadata: resourceVersion: ""