Skip to content

v0.0.9

Choose a tag to compare

View all tags
@github-actions github-actions released this 17 Jun 09:21
v0.0.9
aa9f3ff
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Bugfix release — makes cluster registration idempotent so a transient status-write conflict during a successful registration no longer pins the Cluster to Error. Surfaced during Rancher real-cluster validation.

Container image: docker.io/vworkspace/vworkspace-operator:v0.0.9

Install

Helm (operator + CRDs + RBAC):

helm upgrade --install vworkspace-operator \
  https://github.com/vworkspace-io/vworkspace-operator/releases/download/v0.0.9/vworkspace-operator-0.0.9.tgz \
  --version 0.0.9 \
  -n vworkspace-system \
  --create-namespace

kubectl (no Helm — apply CRDs first):

kubectl apply -f https://github.com/vworkspace-io/vworkspace-operator/releases/download/v0.0.9/crds.yaml
kubectl apply -f https://github.com/vworkspace-io/vworkspace-operator/releases/download/v0.0.9/operator.yaml
kubectl -n vworkspace-system wait --for=condition=Available \
  deployment/vworkspace-operator --timeout=300s

Install guide: docs/install/helm.md

Release assets

File Purpose
vworkspace-operator-0.0.9.tgz Helm chart (operator, CRDs, RBAC)
crds.yaml CRDs only — for kubectl or GitOps bootstrap
operator.yaml Namespace + operator Deployment (CRDs excluded)
SHA256SUMS Checksums for the files above

What's changed

Fixed

  • Cluster registration is now idempotent against existing bootstrap credentials. The reconciler treats a present, valid vworkspace-agent-credentials Secret as proof of registration and no longer re-exchanges the spent one-time token, and the post-registration status write retries on optimistic-concurrency conflicts. Previously a transient the object has been modified conflict during a successful registration left status.phase unset, so the next reconcile re-exchanged the consumed token and pinned the Cluster to Error (RegistrationTokenInvalid) until a new token was issued. A 401 with credentials already present is now treated as benign. Surfaced during Rancher real-cluster validation; tracked under hub golden-path task P4-T001.
  • CI: suppress the SA1019 staticcheck deprecation warning on the cluster-controller event recorder so golangci-lint passes on main (#75).

Full changelog: CHANGELOG.md

Assets 6
Loading