Specify existing secret names for Ingress HTTPS certs

Open Beginner friendly
#490 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
helm, kubernetes
Domain
infrastructure

Research direction

Start by inspecting the Helm chart's Ingress templates and TLS-related values. Trace how HTTPS certificates are currently configured, then make the existing secret name configurable for manually provisioned certificates; done means users can supply a secret, including a wildcard certificate, without relying on certificate manager or LoadBalancer TLS termination.

Written by the indexing model from the issue text.

Description

needs-triage type:feature
Description

This will allow users to provision certs manually (e.g. wildcards) when TLS not handled by certificate manager or LoadBalancer TLS termination.

Requested By
  • Customer name and/or link to HubSpot contact
Dominant language
Go Template
Stars
5
Forks
17
Avg merge
3d 13h
Merged PRs (30d)
25

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FlowFuse/helm

All issues in FlowFuse/helm

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.