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

Testing CA Certificate #169

Closed
3 tasks
shaneutt opened this issue Dec 1, 2021 · 1 comment
Closed
3 tasks

Testing CA Certificate #169

shaneutt opened this issue Dec 1, 2021 · 1 comment
Labels
area/feature New feature or request good first issue Good for newcomers priority/low

Comments

@shaneutt
Copy link
Contributor

shaneutt commented Dec 1, 2021

Problem Statement

The cert-manager addon presently provides a default Issuer that provides "self-signed" certificates. Using self-signed certificates presents many challenges and is in general "hacky".

Proposed Solution

Generate an upfront CA Certificate that is used for the duration of a test cluster's lifecycle, and installed as the default issuer.

Acceptance Criteria

  • kind and GKE cluster implementations both install the KTF CA on nodes during cluster deployment for container runtime trust
  • the cert-manager addon is configured to use the KTF CA as the default Issuer
  • the registry addon switches to using a cert signed by the KTF CA to avoid cluster-specific installation of the currently present self-signed cert
@mflendrich
Copy link
Contributor

Closing "won't fix" because of insufficient demand at this moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/feature New feature or request good first issue Good for newcomers priority/low
Projects
None yet
Development

No branches or pull requests

2 participants