Skip to content

Cloudseed v0.2.1

Choose a tag to compare

@github-actions github-actions released this 27 Sep 02:22
· 3 commits to main since this release
fb546c1

Cloudseed v0.2.1 fixes first-time public-IP detection, Cloudseed installation on bastions and private-cluster tunnel setup. It also adds explicit host-kubeconfig administration and clearer security scan evidence across the CLI, MCP, agents and web console.

Bastion and cluster access

Standalone releases now include portable Python source and the launcher needed to install the same Cloudseed version on Linux bastions, including from a macOS controller. Normal provisioning installs and verifies both cloudseed and cs, makes them available in login/SSH shells, and leaves unrelated existing commands untouched. Kubernetes-enabled bastions receive checksum-verified kubectl, Helm and k9s when tool provisioning is enabled, including VMware. Repair an older bastion from the original controller with:

cs provision CLOUD --env NAME --host bastion

Replace CLOUD and NAME with the existing environment. Installation does not copy the controller's environment records, Terraform state, private SSH keys, kubeconfig or cloud credentials. Keep infrastructure lifecycle and managed platform workflows on the original controller; installing the CLI does not grant cloud or cluster permissions.

After explicitly configuring an authorized kubeconfig on the bastion, use cs kubectl --local-context get nodes, cs helm --local-context list -A, or terminal cs k9s --local-context. This mode validates the selected context and an HTTPS endpoint with TLS verification, and rejects Cloudseed cloud/environment selectors. kubectl/Helm also offer local_context=true through MCP and an explicit host-kubeconfig option in the console; those paths and built-in agent execution require target confirmation even for reads. The target is the machine running that interface. The mode does not fetch credentials, open a Cloudseed tunnel, import infrastructure state or create Cloudseed Undo entries.

On the original controller, first use of a private-cluster tunnel now prepares kubectl before updating the environment's kubeconfig, including commands launched through Helm or k9s. A failed kubeconfig update stops the command with recovery guidance instead of reporting the tunnel ready. TLS verification against the original API name stays enabled.

Fixed

  • Bundled trusted CA roots for verified HTTPS during AWS/GCP/Azure public-IP discovery and downloads. Explicit certificate overrides remain supported; TLS verification stays enabled.
  • Cloud scans retain every failed/manual observation, including lower severities, actual explanations, check IDs, affected resources, remediation and account/project/subscription scope.
  • CIS/STIG, Kubernetes posture, image, host and FIPS scans preserve evidence and report empty, partial, malformed or unverified results as incomplete. Kubernetes-disabled architecture assessments no longer demand cluster diagnostics.
  • Informational and explicitly excluded/inapplicable checks do not create artificial incomplete results. Unknown findings explain the specific evidence gap and how to resolve it.
  • Detailed web report cards, evidence and remediation, explicit preview limits, full JSON/Markdown views and narrow-screen wrapping.
  • macOS packaging uses Apple Developer ID signing for Nimesh Pandeya, team QPF2VF2885, and verifies the expected publisher, hardened runtime and secure timestamp before testing and attesting the signed bytes. Signing is separate from Apple notarization, which this workflow does not perform.
  • Release provenance verification no longer combines mutually exclusive GitHub CLI flags.

Result policy

FAIL exits 1; INCOMPLETE exits 3; PASS and N/A exit 0. A failed result takes precedence over incomplete evidence. Cloud/CIS/host scans fail on any failed check. Kubernetes posture retains its High/Critical failure threshold; image scans retain their Critical threshold. Lower-severity findings remain visible, and every report explains the applicable policy and coverage limits.

scan architecture --max-age-days 30 accepts saved evidence up to 30 days old. Run scan cloud first, then architecture to consume that evidence. Neither a saved configuration check nor a benchmark pass establishes complete framework compliance. Existing reports are preserved; rerun scans to obtain the expanded report format.

Documentation

Downloads and verification

Choose the executable for your OS and CPU: Linux/macOS, amd64/arm64. Each executable has checksums, a manifest and a complete SPDX software inventory. GitHub release-workflow attestations authenticate the build and artifact bytes.

The container image is ghcr.io/nimeshbuilds/cloudseed:v0.2.1, with amd64 and arm64 variants. Use the versioned tag; this release does not publish a latest tag.

After replacing a local binary, restart the Cloudseed console/MCP service so it loads the updated code and web assets. See the release verification scenario before running downloaded artifacts.

Validation

The release is built from fb546c119fd5be75e4461c7e084a2cc41723db55. All 17 merged-main checks and all 10 release jobs passed. The source suite ran 3,840 tests in each of six Linux/macOS and Python-version combinations. All 19 offline scenarios passed with 712 checks; 61 live or credential-dependent steps were explicitly skipped. Each of the four published binary platforms passed 23 packaged tests, and both container architectures passed 21 packaged tests, plus their release scenario checks.

Post-publication verification passed for all 22 downloaded release assets, all 16 file provenance subjects, both image attestations and the multi-architecture container index. Both downloaded Mac binaries passed strict Developer ID signature verification. The downloaded Mac ARM64 executable passed real HTTPS public-IP discovery for AWS/GCP/Azure, nine isolated native kubectl context/TLS checks, and Cloudseed's own checksum-and-attestation verifier.

These checks did not create, destroy or reprovision cloud resources. Automated tests and installation smoke checks do not establish live deployment acceptance across all clouds; live AWS/GCP/Azure/VMware deployment, workload and recovery validation still requires authorized environments and identities.