[iakmc]

Summary

Front-proxy's kubeconfig client cert only had system:masters in its Subject Organizations. That's not enough to reach kcp's Admin Workspace (/services/admin), which front-proxy needs for shard discovery (NewPeersConfig in pkg/proxy/peers.go). The Admin Workspace authorizer checks for group membership in system:kcp:admin specifically, not system:masters, so front-proxy was getting denied there.

What Type of PR Is This?

/kind bug

Related Issue(s)

Part from this PR

Release Notes

front-proxy's kubeconfig client certificate now includes the `system:kcp:admin` group, fixing access to kcp's Admin Workspace used for shard discovery.

[kcp-ci-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign xmudrii for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[iakmc]

/test pull-kcp-operator-test-e2e-canary

[kcp-ci-bot]

@iakmc: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kcp-operator-test-e2e-canary	33ba0bb	link	false	/test pull-kcp-operator-test-e2e-canary

Full PR test history

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[mjudeikis]

I dont think we need this anymore?