apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T18:50:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-108-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-108.ec2.internal uid: 0895bd68-50d7-4b5d-8041-a3a52d202775 resourceVersion: "43367" uid: 0be030a0-a0bf-4e9f-ae57-68f5c9718378 spec: sourcePod: network-check-source-7f44b6dd87-h9hw4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T18:57:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.400914ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:18:24Z" - latency: 896.63µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:17:24Z" - latency: 1.40906ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:16:24Z" - latency: 817.856µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:15:24Z" - latency: 1.060659ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:14:24Z" - latency: 837.304µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:13:24Z" - latency: 1.310201ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:12:24Z" - latency: 735.815µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:11:24Z" - latency: 1.134369ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:10:24Z" - latency: 919.233µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:09:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T18:50:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-108-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-108.ec2.internal uid: 0895bd68-50d7-4b5d-8041-a3a52d202775 resourceVersion: "45893" uid: 8da6e843-9388-46e8-9c6a-86ca7ed29371 spec: sourcePod: network-check-source-7f44b6dd87-h9hw4 targetEndpoint: adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T18:56:24Z" message: 'load-balancer-api-external: tcp connection to adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.771211ms message: 'load-balancer-api-external: tcp connection to adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:20:24Z" - latency: 7.13972ms message: 'load-balancer-api-external: resolved host name adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T19:20:24Z" - latency: 4.010838ms message: 'load-balancer-api-external: tcp connection to adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:19:24Z" - latency: 11.74649ms message: 'load-balancer-api-external: resolved host name adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T19:19:24Z" - latency: 3.980973ms message: 'load-balancer-api-external: tcp connection to adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:18:24Z" - latency: 10.112531ms message: 'load-balancer-api-external: resolved host name adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T19:18:24Z" - latency: 4.003404ms message: 'load-balancer-api-external: tcp connection to adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:17:24Z" - latency: 8.826191ms message: 'load-balancer-api-external: resolved host name adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T19:17:24Z" - latency: 4.899984ms message: 'load-balancer-api-external: tcp connection to adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:16:24Z" - latency: 8.128935ms message: 'load-balancer-api-external: resolved host name adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T19:16:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T18:50:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-108-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-108.ec2.internal uid: 0895bd68-50d7-4b5d-8041-a3a52d202775 resourceVersion: "45892" uid: 95879462-42af-4316-adf9-f96af0e4cb39 spec: sourcePod: network-check-source-7f44b6dd87-h9hw4 targetEndpoint: adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T18:56:24Z" message: 'load-balancer-api-internal: tcp connection to adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.7966ms message: 'load-balancer-api-internal: tcp connection to adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:20:24Z" - latency: 7.204018ms message: 'load-balancer-api-internal: resolved host name adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T19:20:24Z" - latency: 3.096957ms message: 'load-balancer-api-internal: tcp connection to adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:19:24Z" - latency: 11.839394ms message: 'load-balancer-api-internal: resolved host name adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T19:19:24Z" - latency: 3.935771ms message: 'load-balancer-api-internal: tcp connection to adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:18:24Z" - latency: 10.137749ms message: 'load-balancer-api-internal: resolved host name adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T19:18:24Z" - latency: 5.240785ms message: 'load-balancer-api-internal: tcp connection to adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:17:24Z" - latency: 8.893939ms message: 'load-balancer-api-internal: resolved host name adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T19:17:24Z" - latency: 4.878553ms message: 'load-balancer-api-internal: tcp connection to adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:16:24Z" - latency: 8.157955ms message: 'load-balancer-api-internal: resolved host name adc064ed5607d4a80804f8be313e9b1a-bbbe26ebb6c71881.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T19:16:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T18:50:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-108-to-network-check-target-ip-10-0-134-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-108.ec2.internal uid: 0895bd68-50d7-4b5d-8041-a3a52d202775 resourceVersion: "43364" uid: 152efba6-e4cf-48cc-bb16-a0814e64df52 spec: sourcePod: network-check-source-7f44b6dd87-h9hw4 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T18:57:24Z" message: 'network-check-target-ip-10-0-134-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.26854ms message: 'network-check-target-ip-10-0-134-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:18:24Z" - latency: 847.379µs message: 'network-check-target-ip-10-0-134-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:17:24Z" - latency: 1.202196ms message: 'network-check-target-ip-10-0-134-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:16:24Z" - latency: 1.01047ms message: 'network-check-target-ip-10-0-134-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:15:24Z" - latency: 801.232µs message: 'network-check-target-ip-10-0-134-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:14:24Z" - latency: 1.166391ms message: 'network-check-target-ip-10-0-134-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:13:24Z" - latency: 862.054µs message: 'network-check-target-ip-10-0-134-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:12:24Z" - latency: 982.932µs message: 'network-check-target-ip-10-0-134-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:11:24Z" - latency: 1.239114ms message: 'network-check-target-ip-10-0-134-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:10:24Z" - latency: 818.176µs message: 'network-check-target-ip-10-0-134-108: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:09:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T18:50:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-108-to-network-check-target-ip-10-0-135-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-108.ec2.internal uid: 0895bd68-50d7-4b5d-8041-a3a52d202775 resourceVersion: "43365" uid: 2c8d6e05-5265-4db0-9614-78dfaee71dd9 spec: sourcePod: network-check-source-7f44b6dd87-h9hw4 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T18:57:24Z" message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.439809ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:18:24Z" - latency: 2.346086ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:17:24Z" - latency: 2.285082ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:16:24Z" - latency: 2.040773ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:15:24Z" - latency: 1.909525ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:14:24Z" - latency: 2.006004ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:13:24Z" - latency: 2.535397ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:12:24Z" - latency: 1.785354ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:11:24Z" - latency: 2.140754ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:10:24Z" - latency: 2.15054ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:09:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T18:50:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-108-to-network-check-target-ip-10-0-137-226 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-108.ec2.internal uid: 0895bd68-50d7-4b5d-8041-a3a52d202775 resourceVersion: "43366" uid: 02361c68-c015-4bc1-a45b-29549ccbea8d spec: sourcePod: network-check-source-7f44b6dd87-h9hw4 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T18:57:24Z" message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.374148ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:18:24Z" - latency: 2.007086ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:17:24Z" - latency: 1.973181ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:16:24Z" - latency: 1.955589ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:15:24Z" - latency: 1.841409ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:14:24Z" - latency: 1.90448ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:13:24Z" - latency: 1.871967ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:12:24Z" - latency: 1.937498ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:11:24Z" - latency: 1.930319ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:10:24Z" - latency: 1.509899ms message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:09:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T18:50:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-134-108-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-134-108.ec2.internal uid: 0895bd68-50d7-4b5d-8041-a3a52d202775 resourceVersion: "45891" uid: 81d5d612-e5c1-4833-8517-d092befb7fd0 spec: sourcePod: network-check-source-7f44b6dd87-h9hw4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T18:56:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 893.544µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:20:24Z" - latency: 1.698256ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T19:20:24Z" - latency: 1.120506ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:19:24Z" - latency: 1.660576ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T19:19:24Z" - latency: 845.179µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:18:24Z" - latency: 2.437238ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T19:18:24Z" - latency: 870.063µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:17:24Z" - latency: 1.648474ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T19:17:24Z" - latency: 1.267831ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T19:16:24Z" - latency: 1.809901ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T19:16:24Z" kind: List metadata: resourceVersion: ""