-
Notifications
You must be signed in to change notification settings - Fork 251
Open
pulumi/pulumi-hugo
#3521Labels
area/docsImprovements or additions to documentationImprovements or additions to documentationgrooming-q2y25impact/first-48This bug is likely to be hit during a user's first 48 hours of product evaluationThis bug is likely to be hit during a user's first 48 hours of product evaluationneeds-triageNeeds attention from the triage teamNeeds attention from the triage teamsize/SEstimated effort to complete (1-2 days).Estimated effort to complete (1-2 days).
Milestone
Description
The Pulumi & Kubernetes guide can be updated to remove the conditional service logic for minikube. I got through the example using minikube with isMinikube
set to false
.
Steps to reproduce:
-
In a separate terminal, run
minikube tunnel
(required forLoadBalancer
to obtain IP127.0.0.1
) -
Follow all instructions with
isMinikube
set tofalse
-
Modify
frontend
service external port to 8080:-- "ports": [{ "port": 80, "target_port": 80, "protocol": "TCP" }], ++ "ports": [{ "port": 8080, "target_port": 80, "protocol": "TCP" }],
-
Run
pulumi up
Type Name Status + pulumi:pulumi:Stack pulumi-test-local created (13s) + ├─ kubernetes:apps/v1:Deployment nginx created (2s) + └─ kubernetes:core/v1:Service nginx created (10s) Outputs: ip: "127.0.0.1" Resources: + 3 created
-
Use
curl
to validate setup:❯ curl -I 127.0.0.1:8080 HTTP/1.1 200 OK Server: nginx/1.25.2 ...
Notes:
- Used port 8080 instead of 80 as the latter will prompt for admin password input in
minikube tunnel
minikube tunnel
must be running, otherwise service creation will stall waiting for IP assignment
Env details
❯ uname -orm
Darwin 23.0.0 arm64
❯ minikube version
minikube version: v1.31.2
commit: fd7ecd9c4599bef9f04c0986c4a0187f98a4396e
❯ pulumi version
v3.88.0
Metadata
Metadata
Assignees
Labels
area/docsImprovements or additions to documentationImprovements or additions to documentationgrooming-q2y25impact/first-48This bug is likely to be hit during a user's first 48 hours of product evaluationThis bug is likely to be hit during a user's first 48 hours of product evaluationneeds-triageNeeds attention from the triage teamNeeds attention from the triage teamsize/SEstimated effort to complete (1-2 days).Estimated effort to complete (1-2 days).