apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T18:48:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-88-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-88.ec2.internal uid: 2ab747c7-71a1-4ee5-ae50-99f3a7eb7975 resourceVersion: "54607" uid: 7970a577-964f-4c73-adc1-843f7cb72e4c spec: sourcePod: network-check-source-989f8b8dc-s22ql targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T18:55:30Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.10452ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:23:30Z" - latency: 1.294857ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:22:30Z" - latency: 1.606038ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:21:30Z" - latency: 1.108071ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:20:30Z" - latency: 1.861016ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:19:30Z" - latency: 3.729196ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:18:30Z" - latency: 1.156225ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:17:30Z" - latency: 1.668106ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:16:30Z" - latency: 1.50527ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:15:30Z" - latency: 878.637µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:14:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T18:48:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-88-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-88.ec2.internal uid: 2ab747c7-71a1-4ee5-ae50-99f3a7eb7975 resourceVersion: "55669" uid: 5c2e0f7b-706f-4463-8fd4-8e7cdc605958 spec: sourcePod: network-check-source-989f8b8dc-s22ql targetEndpoint: a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T18:54:30Z" message: 'load-balancer-api-external: tcp connection to a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.963675ms message: 'load-balancer-api-external: tcp connection to a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:24:30Z" - latency: 8.259601ms message: 'load-balancer-api-external: resolved host name a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:24:30Z" - latency: 5.242875ms message: 'load-balancer-api-external: tcp connection to a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:23:30Z" - latency: 7.160535ms message: 'load-balancer-api-external: resolved host name a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:23:30Z" - latency: 3.946372ms message: 'load-balancer-api-external: tcp connection to a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:22:30Z" - latency: 8.865501ms message: 'load-balancer-api-external: resolved host name a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:22:30Z" - latency: 5.790246ms message: 'load-balancer-api-external: tcp connection to a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:21:30Z" - latency: 7.05903ms message: 'load-balancer-api-external: resolved host name a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:21:30Z" - latency: 3.383398ms message: 'load-balancer-api-external: tcp connection to a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:20:30Z" - latency: 7.902705ms message: 'load-balancer-api-external: resolved host name a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:20:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T18:48:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-88-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-88.ec2.internal uid: 2ab747c7-71a1-4ee5-ae50-99f3a7eb7975 resourceVersion: "55670" uid: 470ab003-b005-45fa-a220-a67ba2de784e spec: sourcePod: network-check-source-989f8b8dc-s22ql targetEndpoint: a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T18:54:30Z" message: 'load-balancer-api-internal: tcp connection to a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.870245ms message: 'load-balancer-api-internal: tcp connection to a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:24:30Z" - latency: 8.317ms message: 'load-balancer-api-internal: resolved host name a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:24:30Z" - latency: 5.142952ms message: 'load-balancer-api-internal: tcp connection to a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:23:30Z" - latency: 7.180015ms message: 'load-balancer-api-internal: resolved host name a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:23:30Z" - latency: 5.463987ms message: 'load-balancer-api-internal: tcp connection to a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:22:30Z" - latency: 8.846658ms message: 'load-balancer-api-internal: resolved host name a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:22:30Z" - latency: 8.638899ms message: 'load-balancer-api-internal: tcp connection to a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:21:30Z" - latency: 6.975903ms message: 'load-balancer-api-internal: resolved host name a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:21:30Z" - latency: 3.339078ms message: 'load-balancer-api-internal: tcp connection to a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:20:30Z" - latency: 7.824807ms message: 'load-balancer-api-internal: resolved host name a0d790b6a66814cfaa1c9c5f7354c30a-ece3b7c4eca159ff.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T19:20:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T18:48:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-88-to-network-check-target-ip-10-0-135-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-88.ec2.internal uid: 2ab747c7-71a1-4ee5-ae50-99f3a7eb7975 resourceVersion: "54602" uid: 504a2cca-51d4-4179-9ba4-6db627db90e6 spec: sourcePod: network-check-source-989f8b8dc-s22ql targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T18:55:30Z" 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.446279ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:23:30Z" - latency: 2.242271ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:22:30Z" - latency: 2.791833ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:21:30Z" - latency: 2.181916ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:20:30Z" - latency: 2.460345ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:19:30Z" - latency: 5.93752ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:18:30Z" - latency: 2.346523ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:17:30Z" - latency: 2.376903ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:16:30Z" - latency: 2.386986ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:15:30Z" - latency: 2.034542ms message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:14:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T18:48:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-88-to-network-check-target-ip-10-0-141-163 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-88.ec2.internal uid: 2ab747c7-71a1-4ee5-ae50-99f3a7eb7975 resourceVersion: "54603" uid: abae4abc-ef8c-4492-a52e-39433ecfd60e spec: sourcePod: network-check-source-989f8b8dc-s22ql targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T18:55:30Z" message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.393191ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:23:30Z" - latency: 1.998652ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:22:30Z" - latency: 2.393636ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:21:30Z" - latency: 2.123211ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:20:30Z" - latency: 2.011385ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:19:30Z" - latency: 4.231806ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:18:30Z" - latency: 2.075731ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:17:30Z" - latency: 2.048624ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:16:30Z" - latency: 2.260917ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:15:30Z" - latency: 1.88272ms message: 'network-check-target-ip-10-0-141-163: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:14:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T18:48:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-88-to-network-check-target-ip-10-0-141-88 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-88.ec2.internal uid: 2ab747c7-71a1-4ee5-ae50-99f3a7eb7975 resourceVersion: "54604" uid: 6d2c3787-ee3d-430f-a4bc-f475ae2a6323 spec: sourcePod: network-check-source-989f8b8dc-s22ql targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T18:55:30Z" message: 'network-check-target-ip-10-0-141-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.99497ms message: 'network-check-target-ip-10-0-141-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:23:30Z" - latency: 1.506859ms message: 'network-check-target-ip-10-0-141-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:22:30Z" - latency: 1.598399ms message: 'network-check-target-ip-10-0-141-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:21:30Z" - latency: 1.474894ms message: 'network-check-target-ip-10-0-141-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:20:30Z" - latency: 996.942µs message: 'network-check-target-ip-10-0-141-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:19:30Z" - latency: 5.628254ms message: 'network-check-target-ip-10-0-141-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:18:30Z" - latency: 907.507µs message: 'network-check-target-ip-10-0-141-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:17:30Z" - latency: 1.514726ms message: 'network-check-target-ip-10-0-141-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:16:30Z" - latency: 1.017399ms message: 'network-check-target-ip-10-0-141-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:15:30Z" - latency: 957.648µs message: 'network-check-target-ip-10-0-141-88: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:14:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T18:48:29Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-88-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-88.ec2.internal uid: 2ab747c7-71a1-4ee5-ae50-99f3a7eb7975 resourceVersion: "55668" uid: 0c93ff18-038c-4cd2-b7bd-c1d78ae4a6a4 spec: sourcePod: network-check-source-989f8b8dc-s22ql targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T18:54:30Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.014717ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:24:30Z" - latency: 2.357362ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:24:30Z" - latency: 1.112121ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:23:30Z" - latency: 1.880839ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:23:30Z" - latency: 977.309µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:22:30Z" - latency: 2.059018ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:22:30Z" - latency: 939.886µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:21:30Z" - latency: 2.474955ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:21:30Z" - latency: 844.973µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T19:20:30Z" - latency: 2.265572ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T19:20:30Z" kind: List metadata: resourceVersion: ""