devcontainers / devcontainers/features

kubectl-helm-minikube port-forward 443

Open
#976 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
1.5k
Forks
621
Avg merge
6d 53m
Merged PRs (30d)
9

Description

When I run

`kubectl port-forward -n ingress-nginx services/ingress-nginx-controller 80:80`

the forwarded address is `127.0.0.1:80`, but when I run

`kubectl port-forward -n ingress-nginx services/ingress-nginx-controller 443:443`

the forwarded address is `https://CODESPACENAME-443.app.github.dev/`

I would like to be able to use `https://localhost` to access my app from the host machine (e.g. a browser) with a secure connection, but because of the observed behavior of the codespace this is not possible.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the two kubectl port-forward commands from the issue in a Codespace with the ingress-nginx service. Compare how ports 80 and 443 are exposed and investigate the relevant Dev Container Features configuration or entry point. Done means the HTTPS endpoint is reachable as https://localhost from the host machine with a secure connection.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops, networking
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.