( ardi | 2023. 01. 24., k – 12:40 )

Copy /etc/rancher/k3s/k3s.yaml on your machine located outside the cluster as ~/.kube/config ==> OK

$ kubectl get nodes
Unable to connect to the server: dial tcp 127.0.0.1:6443: connectex: No connection could be made because the target mach
ine actively refused it.

UPDATE: Atirva a configban a localhost IP-t a szerver cimre:

$ kubectl get nodes
NAME    STATUS   ROLES                  AGE    VERSION
server   Ready    control-plane,master   4d5h   v1.25.5+k3s2

UPDATE2:

A config file igy nez ki (kulcsok xxx-re irva)

apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: xxx
    server: https://server_IP:6443
  name: default
contexts:
- context:
    cluster: default
    user: default
  name: default
current-context: default
kind: Config
preferences: {}
users:
- name: default
  user:
    client-certificate-data: xxx
    client-key-data: xxx

 

$ kubectl get ns
NAME               STATUS   AGE
default            Active   4d5h
kube-system        Active   4d5h
kube-public        Active   4d5h
kube-node-lease    Active   4d5h
development-dept   Active   23h

$ kubectl get role
NAME        CREATED AT
developer   2023-01-23T12:34:33Z

$ kubectl get rolebinding
NAME                       ROLE             AGE
developer-binding-myuser   Role/developer   23h

Nos, az a kerdesem, hogyan tudom e configot boviteni myuser-rel es kulcsaival, hogy csak a development-dept namespace-ben tudjon mukodni?

Ardi