0
[feature]: Self managed TLS support
Source: makeplane/plane#5783 · opened by @greenaar
Is there an existing issue for this?
• I have searched the existing issues
Summary
Self managed TLS support. For cases where an automatically generated certificate is not desired, and a certificate already exists.
Example, I have a wildcard certificate. It's already configured on my K8S cluster. I should be able to specify 'self managed', the certificate name as stored in K8S, and expect that to enable TLS support without any further configuration.
Why should this be worked on?
On demand certificate provisioning is not always desired (or possible to use). Running over http is not desirable in most cases.
The configuration changes to enable the above self_managed: true and certificate_name logic would be relatively small chart modifications, with a lot of upside (in my case at least).
• I have searched the existing issues
Summary
Self managed TLS support. For cases where an automatically generated certificate is not desired, and a certificate already exists.
Example, I have a wildcard certificate. It's already configured on my K8S cluster. I should be able to specify 'self managed', the certificate name as stored in K8S, and expect that to enable TLS support without any further configuration.
Why should this be worked on?
On demand certificate provisioning is not always desired (or possible to use). Running over http is not desirable in most cases.
The configuration changes to enable the above self_managed: true and certificate_name logic would be relatively small chart modifications, with a lot of upside (in my case at least).
No pledges yet. Be the first to back this.
Comments
Similar requests
[feature]: Support Google Object Storage gs://
0 votes · 0 comments
[feature]: Allow inline creation of dropdown options in custom properties
0 votes · 0 comments
[feature]: issue-relation support in API
0 votes · 0 comments
[feature]: MCP search/list for wiki pages
1 vote · 0 comments
[feature]: [Self-Hosted] Provide an option to authenticate to S3 with IRSA instead of AWS Access Key and Secret Access Key
0 votes · 0 comments
No comments yet.