Skip to content

fix: substitute CLOUDSCALE_API_TOKEN when deploying CAPCS manually - #65

Open
alakae wants to merge 2 commits into
mainfrom
fix-make-deploy-credentials
Open

fix: substitute CLOUDSCALE_API_TOKEN when deploying CAPCS manually#65
alakae wants to merge 2 commits into
mainfrom
fix-make-deploy-credentials

Conversation

@alakae

@alakae alakae commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Documents a plain-kind deploy path in docs/development.md. This was handier for me than bringing up Tilt for a quick manual check of a local image.

`make deploy` applied config/manager/credentials.yaml verbatim, so without
clusterctl init's or Tilt's separate substitution mechanisms the manager's
own credentials Secret got the literal `${CLOUDSCALE_API_TOKEN}` placeholder
as its token, causing a CrashLoopBackOff with an "Invalid token" error from
the cloudscale API.

Pipe the built manifest through `envsubst` scoped to just that one variable
(not a bare envsubst, to avoid touching any other `$identifier`-shaped
content in the generated CRDs).
@alakae
alakae requested a review from mweibel July 29, 2026 06:21
Set up specific Makefile targets (and documentation) to support quick
local checks without the need of tilt. Removes existing
deploy/install/etc. targets which come with kubebuilder boilerplate but
we never use.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants