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

Added support for additional tls certs to custom services #2642

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

andreas-kupries
Copy link
Contributor

fix #2555

Similar to the support for certs by export to OCI registries.
Difference:

  • cert data is in the main secret holding repo credentials
  • export has the data in a separate secret referenced by name from the cred secret

might be better to adjust code here to use a separate secret as well, allow for sharing with export, and between services

@andreas-kupries andreas-kupries added the kind/enhancement New feature or request label Oct 11, 2023
@andreas-kupries andreas-kupries added this to the v1.11.0 milestone Oct 11, 2023
@andreas-kupries andreas-kupries self-assigned this Oct 11, 2023
@codecov
Copy link

codecov bot commented Oct 11, 2023

Codecov Report

Attention: 62 lines in your changes are missing coverage. Please review.

Files Coverage Δ
pkg/api/core/v1/models/service.go 100.00% <ø> (ø)
internal/services/catalog.go 58.25% <10.52%> (-14.69%) ⬇️
internal/helm/helm.go 69.90% <39.18%> (-3.96%) ⬇️

... and 28 files with indirect coverage changes

📢 Thoughts on this report? Let us know!.

@andreas-kupries andreas-kupries marked this pull request as ready for review October 11, 2023 13:02
@andreas-kupries andreas-kupries requested a review from a team as a code owner October 11, 2023 13:02
@andreas-kupries
Copy link
Contributor Author

andreas-kupries commented Oct 11, 2023

Testing:

  • The helmrepo field of service specs names a kube secret A.
  • The keys username and password of A are used to hold the credentials for accessing the helm repo in question.
  • This is how Added support for private Helm repositories and registries #2530 has made it.
  • This PR extends this:
    • The secret A gains a new optional key certs.
    • When certs is set, it holds the name of a kube secret C.
    • The key tls.crt of C is used to hold the PEM-encoded data of the additional certs.
    • This means that C has the same format as the cert secrets used by the export to OCI registries.
    • Like these secrets the certs held by C are provided as CAFile to the repo setup/login functions.
  • Of note, we have two different code paths for setting the cert info, i.e. OCI registry, and regular http(s) helm repo.
    Both require testing.

@andreas-kupries
Copy link
Contributor Author

See PR mittwald/go-helm-client#182 for a possible fix in the mittwald client to expose the necessary information to change by the caller.

The upstream PR is approved and waiting for merging since Aug 30, i.e. 1.5 months as of the time of writing this here.

Decision: Suspending work on this PR and associated ticket until the upstream PR is merged and usable.

@andreas-kupries andreas-kupries added status/later Excluded from release notes. Long-term goal we might target later status/suspended work here suspended due to other work taking priority labels Oct 13, 2023
@enrichman enrichman modified the milestones: v1.11.0, v1.12.0 Oct 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request status/later Excluded from release notes. Long-term goal we might target later status/suspended work here suspended due to other work taking priority
Projects
Status: Icebox
Development

Successfully merging this pull request may close these issues.

Add support for external helm repo for services with self-signed certificate
2 participants