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

Update chart to support TLS for pinniped-proxy #4959

Merged
merged 4 commits into from
Jun 28, 2022
Merged

Conversation

absoludity
Copy link
Contributor

Description of the change

Following on from #4958, this PR updates the kubeapps chart to:

  • supply the pinniped-proxy service with the tls cert and key, when the secret is specified
  • supply the clients of pinniped-proxy (kubeappsapis, and currently still kubeops) with the related CA cert.

Benefits

The pinniped-proxy service can run as a TLS web service, when configured so.

Possible drawbacks

Applicable issues

Additional information

Copy link
Collaborator

@castelblanque castelblanque left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@antgamdia antgamdia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@@ -1581,6 +1581,14 @@ pinnipedProxy:
## @param pinnipedProxy.defaultPinnipedAPISuffix Specify the (default) API suffix
##
defaultPinnipedAPISuffix: pinniped.dev
## @param pinnipedProxy.TLSSecret Specify an optional TLS secret with which to proxy requests
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess we have to run the readmenator to add those params to the chart docs.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah - I'll do that. It does now get run automatically upstream, but no need to wait.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, fortunately, there's no need anymore, but it's nice to have our chart up to date, especially if we, want to give a try to the brand new TLS config. Thanks!

@absoludity absoludity force-pushed the 2268-pinniped-tls-3 branch 2 times, most recently from 0729ef2 to b0a4c4a Compare June 28, 2022 00:14
Base automatically changed from 2268-pinniped-tls-2 to main June 28, 2022 22:48
Signed-off-by: Michael Nelson <minelson@vmware.com>
Signed-off-by: Michael Nelson <minelson@vmware.com>
Signed-off-by: Michael Nelson <minelson@vmware.com>
Signed-off-by: Michael Nelson <minelson@vmware.com>
@netlify
Copy link

netlify bot commented Jun 28, 2022

Deploy Preview for kubeapps-dev ready!

Name Link
🔨 Latest commit 3581d13
🔍 Latest deploy log https://app.netlify.com/sites/kubeapps-dev/deploys/62bb85e051b3ea0009f1e8cb
😎 Deploy Preview https://deploy-preview-4959--kubeapps-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@absoludity absoludity merged commit 09d7648 into main Jun 28, 2022
@absoludity absoludity deleted the 2268-pinniped-tls-3 branch June 28, 2022 23:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants