Expected Behavior
All dev and prod HTTPS endpoints should be reachable and return valid responses:
HTTP-to-HTTPS redirect (301) should work for all endpoints.
Actual Behavior
HTTPS redirect (301) works because it's handled by Cloudflare, not the origin.
Dev environment root cause:
Prod environment root cause:
Additional observations:
- Dev cluster has a single node named
hcloud-prod-cx23-fsn1- the "prod" prefix is misleading for a dev cluster3
- Dev cluster has no HelmReleases, no Gateways, no nothing beyond Flux and CiliumHTTPRoutes
- Only namespaces present in dev:
default, flux-system, kube-system, kube-node-lease, kube-public, cilium-secrets
Steps to Replicate
530
530
error code: 1033
MANIFEST_UNKNOWN: manifest unknown
Only flux-system and kube-system pods
Expected Behavior
All dev and prod HTTPS endpoints should be reachable and return valid responses:
HTTP-to-HTTPS redirect (301) should work for all endpoints.
Actual Behavior
HTTPS redirect (301) works because it's handled by Cloudflare, not the origin.
Dev environment root cause:
tag: devbutworkload pushpushes the artifact with taglatestMANIFEST_ Flux cannot pull the manifestsUNKNOWNworkload pushand Flux OCIRepository configured bycluster create/updateksail#3927Prod environment root cause:
workload reconcilestep with:wait for oci repository ready: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadlineGITHUB_TOKENenv var (see [bug]: CD and CI workflows missing GITHUB_TOKEN in workload reconcile step #1343)Additional observations:
hcloud-prod-cx23-fsn1- the "prod" prefix is misleading for a dev cluster3default,flux-system,kube-system,kube-node-lease,kube-public,cilium-secretsSteps to Replicate
530
530
error code: 1033MANIFEST_UNKNOWN: manifest unknownOnly flux-system and kube-system pods