【K8S】Timeout: request did not complete within requested timeout - context deadline exceeded

1.创建服务提示超时 

[root@K8S1 work]# kubectl apply -f web01-svc.yaml
Error from server (Timeout): error when creating "web01-svc.yaml": 
Timeout: request did not complete within requested timeout - context deadline exceeded

2.原因 

登陆上下文过期,需要重新设置上下文。
KUBE_APISERVER="https://192.168.1.60:8443"
kubectl config set-cluster kubernetes \
--certificate-authority=/etc/kubernetes/cert/ca.pem \
--embed-certs=true \
--server=${KUBE_APISERVER} \
--kubeconfig=admin.kubeconfig

KUBE_APISERVER="https://192.168.1.60:8443"

--设置客户端认证参数。
kubectl config set-credentials kubernetes-admin \
--client-certificate=apiserver-admin.pem \
--client-key=apiserver-admin-key.pem \
--embed-certs=true \
--kubeconfig=admin.kubeconfig

--设置上下文参数。
kubectl config set-context kubernetes-admin@kubernetes \
--cluster=kubernetes \
--user=kubernetes-admin \
--kubeconfig=admin.kubeconfig

--设置默认上下文 
kubectl config use-context kubernetes-admin@kubernetes --kubeconfig=admin.kubeconfig

3.再次创建成功。

[root@K8S1 work]# kubectl apply -f  web01-svc.yaml
service "web01" created

  • 1
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
ORA-12514 is an error that occurs when the Oracle listener is not able to find the requested service in the connect descriptor provided. This error typically indicates that the service name or SID specified in the connection string is incorrect or not known by the listener. To resolve this issue, you can try the following steps: 1. Verify the service name or SID: Double-check the service name or SID specified in the connect descriptor. Make sure it matches the service name or SID defined in the Oracle database. 2. Check listener status: Ensure that the Oracle listener is running and listening for incoming connections. You can use the following command to check the listener status: ``` lsnrctl status ``` If the listener is not running, start it using the following command: ``` lsnrctl start ``` 3. Register the service: If the service name or SID is correct, but still not known by the listener, you can try registering the service manually with the following command: ``` lsnrctl services ``` This command will reload the listener configuration and make it aware of any new services. 4. Check network connectivity: Ensure that there is no network issue between the client and the Oracle server. Check if you can ping the server from the client machine and vice versa. If none of these steps resolve the ORA-12514 error, it might be helpful to provide more information about your specific setup, such as the version of Oracle Database, operating system, and how you are connecting to the database.
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值