Skip to content

Redirect issues with Workspaces and standalone virtual-workspace server #1806

@ncdc

Description

@ncdc

When the partial metadata informer is trying to request /clusters/*/apis/tenancy.kcp.dev/v1beta1/workspaces from the kcp process, this gets redirected to the front proxy, and we see this error

W0819 11:41:35.676289       1 reflector.go:324] k8s.io/client-go@v0.0.0-20220803191238-b6a732dbd013/tools/cache/reflector.go:167: failed to list *unstructured.Unstructured: Get "https://<external url>/services/workspaces/%2A/apis/tenancy.kcp.dev/v1beta1/workspaces?limit=500&resourceVersion=0": x509: certificate is valid for [REDACTED], not apiserver-loopback-client

We need to figure out how to handle situations where the loopback client might get redirected to another URL where it can't validate the certificate.

Originally posted by @ncdc in #1654 (comment)

Metadata

Metadata

Assignees

Labels

area/operationarea/serverEverything around `kcp start`area/shardingIssues or PRs related to sharding changesarea/workspaceslifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions