Skip to content

add: ClusterConfig for managing cluster-wide settings and enhance cluster creation logic - #1182

Merged
Hamdy-khader merged 3 commits into
mainfrom
main-sfam-2790
Jul 23, 2026
Merged

add: ClusterConfig for managing cluster-wide settings and enhance cluster creation logic#1182
Hamdy-khader merged 3 commits into
mainfrom
main-sfam-2790

Conversation

@Hamdy-khader

Copy link
Copy Markdown
Collaborator

Fixes sfam-2790

Comment thread simplyblock_core/cluster_ops.py Outdated
Co-authored-by: Copilot Autofix powered by AI <223894421+github-code-quality[bot]@users.noreply.github.com>
@Hamdy-khader
Hamdy-khader merged commit 3447e9e into main Jul 23, 2026
8 of 10 checks passed
@Hamdy-khader
Hamdy-khader deleted the main-sfam-2790 branch July 23, 2026 16:38
wmousa added a commit that referenced this pull request Jul 24, 2026
… k8s

  PR #1182 replaced add_cluster()'s inline "first cluster on kubernetes"
  setup (FDB connection string, grafana settings, mgmt-node registration)
  with an unconditional read of DeployConfig, but nothing writes that
  record for kubernetes deployments � only the docker-swarm
  create_cluster() path does. Every fresh k8s deployment's first cluster
  create therefore failed with KeyError: No deploy config found.

  Restore the bootstrap: when no clusters exist yet, derive mode/db
  connection/grafana settings, register the mgmt node, and persist the
  result as the DeployConfig subsequent add_cluster() calls read.

  Update tests/integration/test_cluster_duplicate_name.py, which seeded
  clusters without a DeployConfig (broken by #1182 independent of this
  fix), and add coverage for the restored bootstrap path.
wmousa added a commit that referenced this pull request Jul 24, 2026
… k8s

  PR #1182 replaced add_cluster()'s inline "first cluster on kubernetes"
  setup (FDB connection string, grafana settings, mgmt-node registration)
  with an unconditional read of DeployConfig, but nothing writes that
  record for kubernetes deployments � only the docker-swarm
  create_cluster() path does. Every fresh k8s deployment's first cluster
  create therefore failed with KeyError: No deploy config found.

  Restore the bootstrap: when no clusters exist yet, derive mode/db
  connection/grafana settings, register the mgmt node, and persist the
  result as the DeployConfig subsequent add_cluster() calls read.

  Update tests/integration/test_cluster_duplicate_name.py, which seeded
  clusters without a DeployConfig (broken by #1182 independent of this
  fix), and add coverage for the restored bootstrap path.
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.

1 participant