Open zhangchunsheng opened 4 years ago
Issue-Label Bot is automatically applying the labels:
Label | Probability |
---|---|
kind/bug | 0.79 |
area/kfctl | 0.51 |
Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: app homepage, dashboard and code for this bot.
add flag in /etc/kubernetes/manifests/kube-apiserver.yaml
- --service-account-signing-key-file=/etc/kubernetes/pki/sa.key
- --service-account-issuer=kubernetes.default.svc
@zhangchunsheng which cloud are you running on ? AWS, GCP, on-prem ?
@zhangchunsheng which cloud are you running on ? AWS, GCP, on-prem ?
Aliyun
Issue-Label Bot is automatically applying the labels:
Label | Probability |
---|---|
platform/aws | 0.80 |
Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: app homepage, dashboard and code for this bot.
Add following flags/feature gates in you API Server. In the file /etc/kubernetes/manifests/kube-apiserver.yaml
- --feature-gates=TokenRequest=true
- --feature-gates=TokenRequestProjection=true
It should look something like this
spec:
containers:
- command:
- kube-apiserver
- --advertise-address=192.168.28.60
- --allow-privileged=true
- --feature-gates=TokenRequest=true
- --feature-gates=TokenRequestProjection=true
- --authorization-mode=Node,RBAC
- --client-ca-file=/etc/kubernetes/pki/ca.crt
Add following flags/feature gates in you API Server. In the file /etc/kubernetes/manifests/kube-apiserver.yaml
- --feature-gates=TokenRequest=true - --feature-gates=TokenRequestProjection=true
It should look something like this
spec: containers: - command: - kube-apiserver - --advertise-address=192.168.28.60 - --allow-privileged=true - --feature-gates=TokenRequest=true - --feature-gates=TokenRequestProjection=true - --authorization-mode=Node,RBAC - --client-ca-file=/etc/kubernetes/pki/ca.crt
@shantanuVerma7 You saved me.
wsl2 ubuntu + docker desktop + kfctl_istio_dex v1.2.0
works perfectly with below changes
- --service-account-signing-key-file=/run/config/pki/sa.key
- --service-account-issuer=kubernetes.default.svc
- --feature-gates=TokenRequest=true
- --feature-gates=TokenRequestProjection=true
@kim-sardine @shantanuVerma7 I need to thank you guys as well. I just installed 1.2 kf on Mac Docker-Desktop Kubernetes:
In case anyone tries to install kf 1.2 on docker-desktop 2.4.0 with kubernetes 1.18.8 I did the following:
# Edit kube-apiserver.yaml in docker-desktop
# docker run -it --privileged --pid=host debian nsenter -t 1 -m -u -n -i sh
# vi /var/lib/kubeadm/manifests/kube-apiserver.yaml
# ADD FOLLLOWING:
# - --service-account-signing-key-file=/run/config/pki/sa.key
# - --service-account-issuer=kubernetes.default.svc
# - --feature-gates=TokenRequest=true
# - --feature-gates=TokenRequestProjection=true
This caused the "kube-apiserver-docker-desktop" to restart in the docker kubernetes, and then kf installed (after some time) successfully
Note: also edited kfctl_k8s_istio.v1.2.0.yaml and added "clusterName: docker-desktop". This allowed both apply and delete to work properly
@kim-sardine @shantanuVerma7 I need to thank you guys as well. I just installed 1.2 kf on Mac Docker-Desktop Kubernetes:
In case anyone tries to install kf 1.2 on docker-desktop 2.4.0 with kubernetes 1.18.8 I did the following:
# Edit kube-apiserver.yaml in docker-desktop # docker run -it --privileged --pid=host debian nsenter -t 1 -m -u -n -i sh # vi /var/lib/kubeadm/manifests/kube-apiserver.yaml # ADD FOLLLOWING: # - --service-account-signing-key-file=/run/config/pki/sa.key # - --service-account-issuer=kubernetes.default.svc # - --feature-gates=TokenRequest=true # - --feature-gates=TokenRequestProjection=true
This caused the "kube-apiserver-docker-desktop" to restart in the docker kubernetes, and then kf installed (after some time) successfully
Note: also edited kfctl_k8s_istio.v1.2.0.yaml and added "clusterName: docker-desktop". This allowed both apply and delete to work properly
do as above steps, work properly, docker-desktop on Mac
kubeflow / cache-deployer-deployment log