Skip to content

Bug: worker/controller failed setup to on topology configuration on gke autopilot clusters #102

@sanjay7178

Description

@sanjay7178

📜 Description

Bug

I tried setting up kubeslice demo on cloud clusters on my two gke clusters in us-east1 and us-central1 , but though I couldn't able to make initial setup in my clusters via kubeslice-cli --config=topology2.yml install , also I tried the kind minimal-demo didn't worked out mentioned by #83 , It seems gke autopilot cluster doesn't have any worker node by default and kubeslice-cli needs atleast a minimum of 1 node to each cluster

👟 Reproduction steps

  • Create 3 GKE Autopilot clusters on same or different regions
  • Manage to have a topology file of cluster and workers with its kubeconfig
  • Finally run the installation using kubeslice-cli

👍 Expected behavior

Not working

👎 Actual Behavior

Its needs to actually work on GKE Autopilot clusters

🐚 Relevant log output

Image

Version

None

🖥️ What operating system are you seeing the problem on?

No response

✅ Proposed Solution

No response

👀 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find any similar issue

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions