Skip to content
This repository was archived by the owner on Jul 19, 2025. It is now read-only.
This repository was archived by the owner on Jul 19, 2025. It is now read-only.

Ksync init is failing due to connection problem #293

@alok87

Description

@alok87

We have a shared kubernetes cluster for all the developers. We are trying out ksync with every developer having a namespace wise access to kubernetes cluster. Every developers laptop is configured with kubectl having access to only the namespace the developer is working on.

On doing ksync init with the developer laptop it fails with the below connection error.
But if I use default admin user (the one with user and password) , ksync init gets past "Cluster Connection"

I even tried giving the dev-user the complete admin role, ksync init still fails with the same error. Even when kubectl works !

I also tried passing --context=k8sl.XXX.com same error.

$ ksync init --context=k8sl.XXX.com
==== Preflight checks ====
Cluster Config                              ✓
Cluster Connection                          ✘
↳	Unable to contact the cluster for context (k8sl.XXX.com). Does 'kubectl --context=k8sl.practodev.com cluster-info' work?
FATA[0000] Fix errors and try again.

Dev user in kube config looks like below (which is not working)

users:
- name: alok.singh@practo.com
  user:
    auth-provider:
      config:
        client-id: XXX
        client-secret: XXX
        id-token: XXX
        refresh-token: 

Default admin user in kubeconfig which works

users:
- name: k8sl.XXX.com-basic-auth
  user:
    password: XXXX
    username: admin
  • What exactly is run to check the connection?
  • What is the access required by the kubernetes user for ksync to work locally from a developer laptop?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions