You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have e2e tests for Shard and RootShard objects, but right now we don't run a whole end-to-end scenario for FrontProxy installations. We should deploy a kcp setup (with a RootShard, a Shard and a FrontProxy) and test that:
1.) A Kubeconfig to the FrontProxy gives us access to the installation (we might/should pre-create RBAC for the user we encode into the kubeconfig), lets us list workspaces, etc.
2.) Creating new Workspaces works and that scheduling to the secondary shard also works.
3.) Probably more. Think about it a bit and add test steps you would find useful to make sure that everything is working.
We have e2e tests for
Shard
andRootShard
objects, but right now we don't run a whole end-to-end scenario forFrontProxy
installations. We should deploy a kcp setup (with aRootShard
, aShard
and aFrontProxy
) and test that:1.) A
Kubeconfig
to theFrontProxy
gives us access to the installation (we might/should pre-create RBAC for the user we encode into the kubeconfig), lets us list workspaces, etc.2.) Creating new
Workspaces
works and that scheduling to the secondary shard also works.3.) Probably more. Think about it a bit and add test steps you would find useful to make sure that everything is working.
The existing e2e tests can be found under https://github.com/kcp-dev/kcp-operator/tree/main/test/e2e.
The text was updated successfully, but these errors were encountered: