我在本地物理Ubuntu20-04服务器上安装了Microk8s (没有GUI):
microk8s status --wait-ready
microk8s is running
high-availability: no
datastore master nodes: 127.0.0.1:19001
datastore standby nodes: none
addons:
enabled:
ha-cluster # Configure high availability on the current node
helm
尝试在Linux计算机上安装snap microk8s 1.19/stable时,出现以下错误: error: cannot perform the following tasks:
- Run configure hook of "microk8s" snap if present (run hook "configure": 或 - Mount snap "microk8s" (1769) ([stop snap-microk8s-1769.mount] failed with exit status -1: *** stack smas
我想要读取使用K8s的状态,但我不想有修改任何东西的权利。如何做到这一点?
以下内容将使我有充分的机会:
microk8s.kubectl Insufficient permissions to access MicroK8s. You can either try again with sudo or add the user digital to the 'microk8s' group:
sudo usermod -a -G microk8s digital sudo chown -f -R digital ~/.kube
The new group w
使用microk8s和skaffold,我在UNbuntu20.04安装中碰到了这个错误。
container server is waiting to start: aliwatters/dkc-multi-server:7b9b7d87ab81483cdb9b1227780d68dec815fe271aea2f9fe3a0e65090d90909 can't be pulled
我登录到码头了。
全错误为
exiting dev mode because first deploy failed: 1/1 deployment(s) failed
ali@stinky:~/git/d
我在启动群集仪表板时遇到超时问题
microk8s dashboard-proxy
这个问题在我的kubernate集群中一次又一次地发生。我真的不知道是什么原因。
error: timed out waiting for the condition on deployments/kubernetes-dashboard
Traceback (most recent call last):
File "/snap/microk8s/1609/scripts/wrappers/dashboard-proxy.py", line 50, in <mod
我已经安装了microk8s版本1.21,然后尝试创建一个“集群域声明”,我得到了这个错误消息"no matches for kind Cluster Domain Claim in version Networking.nnative.dev/v1alpha1“。我在CRD中搜索,但我不知道如何识别在哪个CRD中搜索。 有人能帮我吗? 这是我的YAML文件: apiVersion: networking.internal.knative.dev/v1alpha1
kind: ClusterDomainClaim
metadata:
nam
我已经在两台机器上安装了microk8s(1.24/稳定)。这两台机器的ip是:172.29.99.187,172.29.99.188。我在172.29.99.187:microk8s add-node上操作这个命令
输出:
From the node you wish to join to this cluster, run the following:
microk8s join 172.29.99.187:25000/57a191d07ce8fe360e13f4f1e9026ce8/5be428d4e916
Use the '--worker' flag to join
我在一台ubuntu笔记本电脑上有一个microk8s集群。我想从azure管道上应用一个部署yaml文件。
我已经在我的信徒中成功地定义了一个Kubernetes服务连接,并通过了验证。不过,当我尝试应用yaml文件时,我会得到以下行
/usr/bin/kubectl apply -f /home/vsts/work/1/s/devops/deploymen.yaml -o json
##[error]Unable to connect to the server: x509: certificate is valid for 127.0.0.1, 10.152.183.1, 192.1
我正在尝试使用MySQL Kubernetes来设置Microk8s HA数据库。
目标是让MySQL在所有三个节点上运行,在它们之间有一个浮动IP,如果其中任何一个节点在火焰中爆炸,数据库将继续工作。
我在https://microk8s.io/high-availability之后安装了3个节点,我将它们分组在一起,如果我运行microk8s kubectl get no,就会得到
NAME STATUS ROLES AGE VERSION
node3 Ready <none> 4m28s v1.19.3-34+a56971609ff3
我有死节点,我可能使用kubectl而不是microk8s命令删除它。问题是microk8s status仍然在数据存储备用节点中显示它。如何将其从集群中删除?
microk8s remove-node 192.168.1.3 --force
Error from server (NotFound): nodes "192.168.1.3" not found
Node 192.168.1.3 does not exist in Kubernetes.
从/var/snap/microk8s/current/var/kubernetes/backend/cluster.yaml
在重新启动VM之后,microk8s停止运行。
Executing this command outputs the following:
microk8s status:
microk8s is not running. use microk8s inspect for a deeper inspection.
microk8s kubectl get pod:
The connection to the server 127.0.0.1 16443 was refused did you specify the right host or port?
我几乎所有的方法都试过了,但没有结果。
Ubuntu 18内置了一个插件,当我试图安装它时,我得到了以下错误:
$ sudo snap install microk8s
error: snap "microk8s" requires classic confinement which is only available on
classic systems
在单个节点上安装MicroK8s时,在获取microk8s状态时出现以下错误:
The command could not be located because '/snap/bin' is not included in the PATH environment variable.
microk8s.status: command not found
我做过出口PATH=$PATH:/usr/bin
sudo nano /etc/environment
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/s
我在LXD容器中安装了microk8s。
snap install microk8s --classic
当我检查实例时,它会显示出快照.microk8s.daemon-proxy没有运行
root@mk8s1:~# microk8s inspect
Inspecting Certificates
Inspecting services
Service snap.microk8s.daemon-cluster-agent is running
Service snap.microk8s.daemon-containerd is running
Service snap.microk