spinnaker.clouddriver.operations

Cloud provider operations

Dimensions:None

Technical Annotations (15)

Configuration Parameters (3)

terminationGracePeriodSecondsrecommended: sufficient for operation completion

Kubernetes pod spec to allow Clouddriver to finish work

redis.poll.timeoutSecondsrecommended: increase from 300

Timeout before rescheduling agents that haven't completed (default 5 minutes)

redis.poll.intervalSecondsrecommended: 30

Default 30-second interval between caching agent runs; tune based on freshness vs quota needs

Error Signatures (1)

No atomic operation converter found for description 'deployManifest' and cloud provider 'kubernetes' at version 'v1'exception

CLI Commands (3)

curl <clouddriver>:7002/credentials/<account>diagnostic

curl <clouddriver>:7002/credentialsdiagnostic

watch -g "curl -s spin-clouddriver.spinnaker:7002/credentials | jq '.[] | select(.type==\"kubernetes\") | select(.providerVersion==\"v1\") | \"\(.name) \(.providerVersion)\"' | sort"

monitoring

Technical References (8)

clouddrivercomponentproviderVersionconceptdeployManifestconcepttomcatcomponentSIGTERMconceptClouddrivercomponentcaching agentsconcept~/.hal/$DEPLOYMENT/profiles/clouddriver-local.ymlfile path

Related Insights (4)

Provider version mismatch causes deployManifest failures in Kubernetes v2 pipelinescritical

▸

Clouddriver requires graceful shutdown window for Kubernetes operationswarning

▸

Premature caching agent rescheduling due to timeoutwarning

▸

Caching interval tradeoff between UI freshness and API quotainfo

▸