• 安装部署

  • 关于如何删除Porter中已分配地址的问题

已经顺利完成在kubesphere上部署porter组件，并成功配置了基于Layer2的 LB，感谢各类教程。

现在问题是一旦使用过eip-pool的地址后，该地址就一直处于usage状态了，除非删除services。请各位大神帮忙看下，如何删除已经分配的eip地址

1 个月 后

这个需要你先删除对应的使用eip的service

3 个月 后
3 个月 后

k8s 1.20
ks 3.1.0
porter 0.4.1
如何删除EIP 地址?
其他使用到LB的服务都已经删除，无法删除eip 地址，重新部署porter后svc EXTERNAL-IP 一直处于pending状态
[root@namenodemaster porter]# k get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP 10.1.0.1 <none> 443/TCP 116d
porter-layer2-svc LoadBalancer 10.1.92.108 <pending> 80:26520/TCP 3s
[root@namenodemaster porter]# k get eip # 地址还是显示使用中
NAME CIDR USAGE TOTAL
porter-layer2-eip 172.31.2.200-172.31.2.210 3 11

[root@namenodemaster porter]# k delete -f porter-layer2-eip.yaml
eip.network.kubesphere.io “porter-layer2-eip” deleted
C

    jyhgit
    在ks console 重新部署porter 后进行的以下操作

    [root@namenodemaster porter]# k apply -f porter-layer2-eip.yaml 
Warning: Detected changes to resource porter-layer2-eip which is currently being deleted.
eip.network.kubesphere.io/porter-layer2-eip unchanged
[root@namenodemaster porter]# k apply -f porter-layer2.yaml 
deployment.apps/porter-layer2 created
[root@namenodemaster porter]# k apply -f porter-layer2-svc.yaml 
service/porter-layer2-svc created
[root@namenodemaster porter]# k get svc
NAME                TYPE           CLUSTER-IP    EXTERNAL-IP   PORT(S)          AGE
kubernetes          ClusterIP      10.1.0.1      <none>        443/TCP          116d
nginx-svc           NodePort       10.1.217.27   <none>        8080:32044/TCP   111d
porter-layer2-svc   LoadBalancer   10.1.196.40   <pending>     80:57437/TCP     49s
[root@namenodemaster porter]# k get svc
NAME                TYPE           CLUSTER-IP    EXTERNAL-IP   PORT(S)          AGE
kubernetes          ClusterIP      10.1.0.1      <none>        443/TCP          116d
nginx-svc           NodePort       10.1.217.27   <none>        8080:32044/TCP   111d
porter-layer2-svc   LoadBalancer   10.1.196.40   <pending>     80:57437/TCP     52s
[root@namenodemaster porter]# k get svc
NAME                TYPE           CLUSTER-IP    EXTERNAL-IP   PORT(S)          AGE
kubernetes          ClusterIP      10.1.0.1      <none>        443/TCP          116d
nginx-svc           NodePort       10.1.217.27   <none>        8080:32044/TCP   111d
porter-layer2-svc   LoadBalancer   10.1.196.40   <pending>     80:57437/TCP     53s
[root@namenodemaster porter]# k get ep
NAME                ENDPOINTS                                              AGE
kubernetes          172.31.0.231:6443,172.31.0.232:6443,172.31.1.37:6443   116d
nginx-svc           <none>                                                 111d
porter-layer2-svc   10.244.1.86:8080,10.244.3.238:8080                     60s
storage.pri-nfs     <none>                                                 111d
[root@namenodemaster porter]# k get svc    #pending
NAME                TYPE           CLUSTER-IP    EXTERNAL-IP   PORT(S)          AGE
kubernetes          ClusterIP      10.1.0.1      <none>        443/TCP          116d
nginx-svc           NodePort       10.1.217.27   <none>        8080:32044/TCP   111d
porter-layer2-svc   LoadBalancer   10.1.196.40   <pending>     80:57437/TCP     69s
[root@namenodemaster porter]# curl -I 10.244.1.86:8080
HTTP/1.1 200 OK
Date: Thu, 20 May 2021 01:41:03 GMT
Connection: keep-alive

[root@namenodemaster porter]# curl  10.244.1.86:8080  
You've hit porter-layer2-6fd5d96d5b-8fzv8

        jyhgit
        I0521 08:34:57.300307 1 clientconn.go:948] ClientConn switching balancer to “pick_first”
        E0521 08:35:17.816694 1 crd_finalizer.go:156] Operation cannot be fulfilled on customresourcedefinitions.apiextensions.k8s.io “eips.network.kubesphere.io”: the object has been modified; please apply your changes to the latest version and try again
        E0521 08:35:17.816719 1 crd_finalizer.go:299] eips.network.kubesphere.io failed with: timed out waiting for the condition
        I0521 08:35:33.123103 1 client.go:360] parsed scheme: “passthrough”