apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-219-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-219.ec2.internal uid: 439ff56d-788f-4ad5-889a-490885985db2 resourceVersion: "18028" uid: a37aa1fb-d080-4234-b46f-597afadcdfc1 spec: sourcePod: network-check-source-8894fc9bd-2hr4w targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T21:26:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.004153ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:33:21Z" - latency: 1.249089ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:32:21Z" - latency: 955.618µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:31:21Z" - latency: 887.696µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:30:21Z" - latency: 1.085107ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:29:21Z" - latency: 1.057536ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:28:21Z" - latency: 838.305µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:27:21Z" - latency: 947.543µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:26:21Z" - latency: 1.06802ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:25:21Z" - latency: 1.019458ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:24:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-219-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-219.ec2.internal uid: 439ff56d-788f-4ad5-889a-490885985db2 resourceVersion: "20073" uid: 4bbe0c95-239a-4713-9af4-4b6a5c1939ed spec: sourcePod: network-check-source-8894fc9bd-2hr4w targetEndpoint: a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:25:21Z" message: 'load-balancer-api-external: tcp connection to a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.148002ms message: 'load-balancer-api-external: tcp connection to a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:37:21Z" - latency: 7.801765ms message: 'load-balancer-api-external: resolved host name a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:37:21Z" - latency: 4.043297ms message: 'load-balancer-api-external: tcp connection to a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:36:21Z" - latency: 8.422907ms message: 'load-balancer-api-external: resolved host name a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:36:21Z" - latency: 4.506247ms message: 'load-balancer-api-external: tcp connection to a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:35:21Z" - latency: 7.878776ms message: 'load-balancer-api-external: resolved host name a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:35:21Z" - latency: 4.593102ms message: 'load-balancer-api-external: tcp connection to a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:34:21Z" - latency: 8.864896ms message: 'load-balancer-api-external: resolved host name a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:34:21Z" - latency: 4.88247ms message: 'load-balancer-api-external: tcp connection to a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:33:21Z" - latency: 7.540155ms message: 'load-balancer-api-external: resolved host name a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:33:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-219-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-219.ec2.internal uid: 439ff56d-788f-4ad5-889a-490885985db2 resourceVersion: "20074" uid: 9c3e31b4-e425-4890-b866-e96672b4fa65 spec: sourcePod: network-check-source-8894fc9bd-2hr4w targetEndpoint: a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T21:25:21Z" message: 'load-balancer-api-internal: tcp connection to a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.134851ms message: 'load-balancer-api-internal: tcp connection to a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:37:21Z" - latency: 7.884399ms message: 'load-balancer-api-internal: resolved host name a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:37:21Z" - latency: 4.469033ms message: 'load-balancer-api-internal: tcp connection to a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:36:21Z" - latency: 8.499306ms message: 'load-balancer-api-internal: resolved host name a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:36:21Z" - latency: 4.469249ms message: 'load-balancer-api-internal: tcp connection to a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:35:21Z" - latency: 7.97431ms message: 'load-balancer-api-internal: resolved host name a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:35:21Z" - latency: 5.765084ms message: 'load-balancer-api-internal: tcp connection to a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:34:21Z" - latency: 8.920475ms message: 'load-balancer-api-internal: resolved host name a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:34:21Z" - latency: 5.263875ms message: 'load-balancer-api-internal: tcp connection to a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:33:21Z" - latency: 7.598563ms message: 'load-balancer-api-internal: resolved host name a9edc5ed6f21045c5b500f3661509988-d89bdb02de5104dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T21:33:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-219-to-network-check-target-ip-10-0-132-118 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-219.ec2.internal uid: 439ff56d-788f-4ad5-889a-490885985db2 resourceVersion: "18026" uid: 19e9eb35-ce29-4bd3-980c-e2301afd5595 spec: sourcePod: network-check-source-8894fc9bd-2hr4w targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:26:21Z" message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.127978ms message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:33:21Z" - latency: 2.273169ms message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:32:21Z" - latency: 1.91054ms message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:31:21Z" - latency: 2.143047ms message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:30:21Z" - latency: 1.946337ms message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:29:21Z" - latency: 2.1065ms message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:28:21Z" - latency: 1.990401ms message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:27:21Z" - latency: 2.075313ms message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:26:21Z" - latency: 2.045501ms message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:25:21Z" - latency: 2.32673ms message: 'network-check-target-ip-10-0-132-118: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:24:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-219-to-network-check-target-ip-10-0-132-219 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-219.ec2.internal uid: 439ff56d-788f-4ad5-889a-490885985db2 resourceVersion: "18025" uid: b8092a9d-5091-45aa-9de6-86a527c3ed47 spec: sourcePod: network-check-source-8894fc9bd-2hr4w targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:26:21Z" message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 881.675µs message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:33:21Z" - latency: 805.567µs message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:32:21Z" - latency: 1.191012ms message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:31:21Z" - latency: 904.058µs message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:30:21Z" - latency: 1.165657ms message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:29:21Z" - latency: 855.127µs message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:28:21Z" - latency: 1.186833ms message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:27:21Z" - latency: 859.407µs message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:26:21Z" - latency: 937.132µs message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:25:21Z" - latency: 1.105706ms message: 'network-check-target-ip-10-0-132-219: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:24:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-219-to-network-check-target-ip-10-0-141-46 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-219.ec2.internal uid: 439ff56d-788f-4ad5-889a-490885985db2 resourceVersion: "18027" uid: 37abeb82-20dd-4554-bda4-e7e2998c7d95 spec: sourcePod: network-check-source-8894fc9bd-2hr4w targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T21:26:21Z" message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.109974ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:33:21Z" - latency: 2.456296ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:32:21Z" - latency: 2.023445ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:31:21Z" - latency: 2.470208ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:30:21Z" - latency: 2.043644ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:29:21Z" - latency: 2.132088ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:28:21Z" - latency: 2.178161ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:27:21Z" - latency: 2.049529ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:26:21Z" - latency: 2.82277ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:25:21Z" - latency: 2.097021ms message: 'network-check-target-ip-10-0-141-46: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:24:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T21:19:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-219-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-219.ec2.internal uid: 439ff56d-788f-4ad5-889a-490885985db2 resourceVersion: "20072" uid: 0744584b-c108-46ff-99ca-c93c2d5c7dfe spec: sourcePod: network-check-source-8894fc9bd-2hr4w targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T21:25:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 961.825µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:37:21Z" - latency: 1.75295ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:37:21Z" - latency: 966.286µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:36:21Z" - latency: 1.757227ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:36:21Z" - latency: 807.218µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:35:21Z" - latency: 1.701333ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:35:21Z" - latency: 1.013173ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:34:21Z" - latency: 1.918256ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:34:21Z" - latency: 1.020712ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T21:33:21Z" - latency: 1.59254ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T21:33:21Z" kind: List metadata: resourceVersion: ""