apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T10:09:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-215-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-215.ec2.internal uid: 3cfa64f3-9b75-4281-93f0-853fd587bdca resourceVersion: "26798" uid: 0d06aa41-a436-45a0-9057-3dec6e4f727a spec: sourcePod: network-check-source-7b678d77c7-5qr2r targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T10:16:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.305172ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:51:05Z" - latency: 1.20021ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:50:05Z" - latency: 1.239593ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:49:05Z" - latency: 1.320692ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:48:05Z" - latency: 1.213658ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:47:05Z" - latency: 1.054473ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:46:05Z" - latency: 992.744µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:45:05Z" - latency: 1.120818ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:44:05Z" - latency: 1.040985ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:43:05Z" - latency: 975.203µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:42:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T10:09:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-215-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-215.ec2.internal uid: 3cfa64f3-9b75-4281-93f0-853fd587bdca resourceVersion: "26799" uid: e1665be8-c808-4edf-9c36-7f2898e0920b spec: sourcePod: network-check-source-7b678d77c7-5qr2r targetEndpoint: ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T10:15:05Z" message: 'load-balancer-api-external: tcp connection to ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.975086ms message: 'load-balancer-api-external: tcp connection to ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:51:05Z" - latency: 7.17452ms message: 'load-balancer-api-external: resolved host name ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T10:51:05Z" - latency: 3.391969ms message: 'load-balancer-api-external: tcp connection to ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:50:05Z" - latency: 7.226931ms message: 'load-balancer-api-external: resolved host name ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T10:50:05Z" - latency: 4.927523ms message: 'load-balancer-api-external: tcp connection to ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:49:05Z" - latency: 10.391129ms message: 'load-balancer-api-external: resolved host name ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T10:49:05Z" - latency: 5.002075ms message: 'load-balancer-api-external: tcp connection to ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:48:05Z" - latency: 8.07431ms message: 'load-balancer-api-external: resolved host name ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T10:48:05Z" - latency: 5.040568ms message: 'load-balancer-api-external: tcp connection to ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:47:05Z" - latency: 7.618178ms message: 'load-balancer-api-external: resolved host name ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T10:47:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T10:09:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-215-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-215.ec2.internal uid: 3cfa64f3-9b75-4281-93f0-853fd587bdca resourceVersion: "26800" uid: bc9b0c76-79e8-4ce6-9655-0387183a7f47 spec: sourcePod: network-check-source-7b678d77c7-5qr2r targetEndpoint: ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T10:15:05Z" message: 'load-balancer-api-internal: tcp connection to ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.962763ms message: 'load-balancer-api-internal: tcp connection to ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:51:05Z" - latency: 7.292109ms message: 'load-balancer-api-internal: resolved host name ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T10:51:05Z" - latency: 3.86253ms message: 'load-balancer-api-internal: tcp connection to ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:50:05Z" - latency: 7.272898ms message: 'load-balancer-api-internal: resolved host name ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T10:50:05Z" - latency: 4.913729ms message: 'load-balancer-api-internal: tcp connection to ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:49:05Z" - latency: 10.504809ms message: 'load-balancer-api-internal: resolved host name ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T10:49:05Z" - latency: 4.709584ms message: 'load-balancer-api-internal: tcp connection to ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:48:05Z" - latency: 8.23475ms message: 'load-balancer-api-internal: resolved host name ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T10:48:05Z" - latency: 5.100064ms message: 'load-balancer-api-internal: tcp connection to ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:47:05Z" - latency: 7.679742ms message: 'load-balancer-api-internal: resolved host name ab66903232a55480b98970b0494efe24-0ff8e5ff5bbe9742.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T10:47:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T10:09:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-215-to-network-check-target-ip-10-0-135-1 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-215.ec2.internal uid: 3cfa64f3-9b75-4281-93f0-853fd587bdca resourceVersion: "26796" uid: 5045483f-4d45-438d-b61a-6ad76430510f spec: sourcePod: network-check-source-7b678d77c7-5qr2r targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T10:16:05Z" message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.083527ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:51:05Z" - latency: 2.677016ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:50:05Z" - latency: 1.851185ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:49:05Z" - latency: 2.210652ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:48:05Z" - latency: 1.806528ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:47:05Z" - latency: 1.910092ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:46:05Z" - latency: 1.858545ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:45:05Z" - latency: 1.857555ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:44:05Z" - latency: 1.914116ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:43:05Z" - latency: 1.960719ms message: 'network-check-target-ip-10-0-135-1: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:42:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T10:09:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-215-to-network-check-target-ip-10-0-135-215 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-215.ec2.internal uid: 3cfa64f3-9b75-4281-93f0-853fd587bdca resourceVersion: "26794" uid: b1202769-3138-42c2-9a9e-468df20c4395 spec: sourcePod: network-check-source-7b678d77c7-5qr2r targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T10:16:05Z" message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 799.632µs message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:51:05Z" - latency: 1.031543ms message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:50:05Z" - latency: 619.043µs message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:49:05Z" - latency: 1.063085ms message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:48:05Z" - latency: 959.497µs message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:47:05Z" - latency: 1.457834ms message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:46:05Z" - latency: 856.838µs message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:45:05Z" - latency: 779.582µs message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:44:05Z" - latency: 1.36322ms message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:43:05Z" - latency: 936.874µs message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:42:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T10:09:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-215-to-network-check-target-ip-10-0-143-196 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-215.ec2.internal uid: 3cfa64f3-9b75-4281-93f0-853fd587bdca resourceVersion: "26795" uid: 6fa26df3-a93a-4870-af12-1aa30100e35d spec: sourcePod: network-check-source-7b678d77c7-5qr2r targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T10:16:05Z" message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.056749ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:51:05Z" - latency: 1.964011ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:50:05Z" - latency: 1.902772ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:49:05Z" - latency: 2.27076ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:48:05Z" - latency: 2.01891ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:47:05Z" - latency: 2.153095ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:46:05Z" - latency: 1.937551ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:45:05Z" - latency: 2.060549ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:44:05Z" - latency: 2.207137ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:43:05Z" - latency: 2.128529ms message: 'network-check-target-ip-10-0-143-196: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:42:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T10:09:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-215-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-215.ec2.internal uid: 3cfa64f3-9b75-4281-93f0-853fd587bdca resourceVersion: "26797" uid: c941c657-4107-4c58-8464-08588d1b7de2 spec: sourcePod: network-check-source-7b678d77c7-5qr2r targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T10:15:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.190828ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:51:05Z" - latency: 1.829334ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T10:51:05Z" - latency: 1.001092ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:50:05Z" - latency: 1.931572ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T10:50:05Z" - latency: 1.017761ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:49:05Z" - latency: 1.800172ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T10:49:05Z" - latency: 863.418µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:48:05Z" - latency: 1.963907ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T10:48:05Z" - latency: 1.002793ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T10:47:05Z" - latency: 1.73164ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T10:47:05Z" kind: List metadata: resourceVersion: ""