kcp
kcp copied to clipboard
kcp-dev
bug: Wire in dev certificate for mounts in `kcp start`
Describe the bug
This is to track https://github.com/kcp-dev/kcp/pull/3057/files#diff-8788f7c7e1c9b5d5b7df0e3a320164e8cc298040cebea5acaeb4ccd9f85ee854R157
As follow-up:
When running kcp start we generate a development certificate for api-server. It is being reused for all rest/API trust in the local kcp instance. We need to reuse the same certificate when running virtual workspaces in dev.
When making calls we should use the same CA as our dev certificate. Its callers responsibility to use this certificate when developing virtual-workspaces. Need to document this use case in developers docs too.,
Steps To Reproduce
See PR
Expected Behaviour
Use TLS
Additional Context
No response
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kcp-ci-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
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/test-infra repository.
@mjudeikis: Reopened this issue.
In response to this:
/reopen /remove-lifecycle rotten
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/test-infra repository.
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale