Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improvement for k8s.io/docs/setup/best-practices/certificates/ #23726

Closed
recentcoin opened this issue Sep 7, 2020 · 5 comments
Closed

Improvement for k8s.io/docs/setup/best-practices/certificates/ #23726

recentcoin opened this issue Sep 7, 2020 · 5 comments
Labels
language/en Issues or PRs related to English language lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@recentcoin
Copy link

Any hints on how to integrate this with an existing CA? For example, our AD domain currently has a CA cluster for authentication between machines. We'd like to expand that to handle the certs needed for kube containers so that its already trusted by our staff.

@sftim
Copy link
Contributor

sftim commented Oct 8, 2020

I think you're asking for something different from what https://k8s.io/docs/setup/best-practices/certificates/ is requesting - my guess is that what you have in mind is closer to #14725 (TLS for applications running in the cluster)

Have I got that right?
/language en
/triage needs-information

@k8s-ci-robot k8s-ci-robot added language/en Issues or PRs related to English language triage/needs-information Indicates an issue needs more information in order to work on it. labels Oct 8, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 6, 2021
@fejta-bot
Copy link

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.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 5, 2021
@sftim
Copy link
Contributor

sftim commented Feb 5, 2021

Will close this. Slightly relevant to issue #25833
/close

@k8s-ci-robot
Copy link
Contributor

@sftim: Closing this issue.

In response to this:

Will close this. Slightly relevant to issue #25833
/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
language/en Issues or PRs related to English language lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

4 participants