concourse / concourse/concourse-chart
Ways to force HTTPS?
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 160
- Forks
- 189
- PR merge metrics
- No merged PRs in 30d
Description
Hi, Would it be possible to extend the chart with a way to force HTTPS for requests to concourse web UI? Not sure if it's possible without ingress. For those using ingress controller with support for IngressRoute, it could do if the chart would come with (optional) IngressRoute manifest. Not sure how the support for IngressRoute in Kubernetes will develop over time.
Other options maybe?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the chart's existing ingress configuration and manifests. Determine how HTTPS could be forced for Concourse web UI requests, including whether an optional IngressRoute should be supported; done means the chosen approach is documented and works for the relevant ingress setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100