在 https://editor.csdn.net/md/?articleId=106170316中跟着github中的说明进行了初体验。但是发现并不是每个模块都会用到.

github说明

后端service准备

两个version的myapp备用，并配好对应的service

ame:              myappsvc
Namespace:         default
Labels:            <none>
Annotations:       Selector:  app=myapp
Type:              ClusterIP
IP:                10.96.66.66
Port:              <unset>  80/TCP
TargetPort:        80/TCP
Endpoints:         10.244.2.215:80,10.244.2.216:80,10.244.2.217:80 + 2 more...
Session Affinity:  None
Events:            <none>Name:              myappsvc2
Namespace:         default
Labels:            <none>
Annotations:       Selector:  app=myappsec
Type:              ClusterIP
IP:                10.96.55.55
Port:              <unset>  80/TCP
TargetPort:        80/TCP
Endpoints:         10.244.2.225:80,10.244.2.226:80,10.244.2.227:80 + 2 more...
Session Affinity:  None

部署ingress.yaml

ingress.yaml 配置

[root@test ~]# cat ingress.yaml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:name: ingressmyappnamespace: ingress-nginx
spec:rules:- host: pphqq.vicp.nethttp:paths:- path: /v1backend:serviceName: myappsvcservicePort: 80- path: /v2backend:serviceName: mappsvc2servicePort: 80

apply 以后发现有报错

[root@test ~]# kubectl apply -f ingress.yaml
Error from server (InternalError): error when creating "ingress.yaml": Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": Post https://ingress-nginx-controller-admission.ingress-nginx.svc:443/extensions/v1beta1/ingresses?timeout=30s: context deadline exceeded

TS 参考1 ：https://blog.51cto.com/juestnow/2493608

文中提到**# kubelet 参数node-ip 为ipv6 模式记得修改 service ipFamily: IPv6
模式不然新版本webhook 会报错**

没想到什么：看到了 ipFamily: IPv6
https://github.com/kubernetes/ingress-nginx/blob/master/docs/deploy/index.md
提到 !!! danger The admission webhook require conectivity between Kubernetes API server and the ingress controller.
又是一个官方文档 https://kubernetes.io/zh/docs/reference/access-authn-authz/extensible-admission-controllers/
文中提到**对于使用 admissionregistration.k8s.io/v1beta1 创建的 webhook 而言，其默认超时是 30 秒。**这个跟报错中timeout=30s比较像。
自己跑的安装命令：
kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-0.32.0/deploy/static/provider/cloud/deploy.yaml
修改这个文件，在service下加了 ipFamily: IPv6 ，apply ingress.yaml 一样有报错。

TS 参考2 https://stackoverflow.com/questions/61365202/nginx-ingress-service-ingress-nginx-controller-admission-not-found

看起来还没解

TS 参考3 https://github.com/kubernetes/ingress-nginx/issues/5583

Orz 这个老哥重装了k8s ，我还能说啥。那研究参考1吧。
先看自己的log

[root@test ~]# kubectl logs pod/ingress-nginx-controller-866488c6d4-2sz9s -n ingress-nginx
-------------------------------------------------------------------------------
NGINX Ingress controllerRelease:       0.32.0Build:         git-446845114Repository:    https://github.com/kubernetes/ingress-nginxnginx version: nginx/1.17.10-------------------------------------------------------------------------------I0519 14:42:23.085872       6 flags.go:204] Watching for Ingress class: nginx
W0519 14:42:23.086188       6 flags.go:249] SSL certificate chain completion is disabled (--enable-ssl-chain-completion=false)
W0519 14:42:23.086222       6 client_config.go:543] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0519 14:42:23.086362       6 main.go:220] Creating API client for https://10.96.0.1:443
I0519 14:42:23.094174       6 main.go:264] Running in Kubernetes cluster version v1.18 (v1.18.2) - git (clean) commit 52c56ce7a8272c798dbc29846288d7cd9fbae032 - platform linux/amd64
I0519 14:42:23.210843       6 main.go:105] SSL fake certificate created /etc/ingress-controller/ssl/default-fake-certificate.pem
I0519 14:42:23.213364       6 main.go:113] Enabling new Ingress features available since Kubernetes v1.18
W0519 14:42:23.215404       6 main.go:125] No IngressClass resource with name nginx found. Only annotation will be used.
I0519 14:42:23.229793       6 ssl.go:528] loading tls certificate from certificate path /usr/local/certificates/cert and key path /usr/local/certificates/key
I0519 14:42:23.260220       6 nginx.go:263] Starting NGINX Ingress controller
I0519 14:42:23.276062       6 event.go:278] Event(v1.ObjectReference{Kind:"ConfigMap", Namespace:"ingress-nginx", Name:"ingress-nginx-controller", UID:"a0dec818-3429-4aec-a88a-97adba153201", APIVersion:"v1", ResourceVersion:"4033352", FieldPath:""}): type: 'Normal' reason: 'CREATE' ConfigMap ingress-nginx/ingress-nginx-controller
I0519 14:42:24.460640       6 nginx.go:307] Starting NGINX process
I0519 14:42:24.463065       6 nginx.go:327] Starting validation webhook on :8443 with keys /usr/local/certificates/cert /usr/local/certificates/key
I0519 14:42:24.463137       6 leaderelection.go:242] attempting to acquire leader lease  ingress-nginx/ingress-controller-leader-nginx...
I0519 14:42:24.463627       6 controller.go:139] Configuration changes detected, backend reload required.
I0519 14:42:24.485110       6 leaderelection.go:252] successfully acquired lease ingress-nginx/ingress-controller-leader-nginx
I0519 14:42:24.485316       6 status.go:86] new leader elected: ingress-nginx-controller-866488c6d4-2sz9s
I0519 14:42:24.537679       6 controller.go:155] Backend successfully reloaded.
I0519 14:42:24.537711       6 controller.go:164] Initial sync, sleeping for 1 second.
E0520 12:28:00.939762       6 leaderelection.go:320] error retrieving resource lock ingress-nginx/ingress-controller-leader-nginx: context deadline exceeded
I0520 12:28:00.939793       6 leaderelection.go:277] failed to renew lease ingress-nginx/ingress-controller-leader-nginx: timed out waiting for the condition
I0520 12:28:00.942992       6 leaderelection.go:242] attempting to acquire leader lease  ingress-nginx/ingress-controller-leader-nginx...
I0520 12:28:00.971606       6 leaderelection.go:252] successfully acquired lease ingress-nginx/ingress-controller-leader-nginx

[root@test ~]# kubectl describe svc ingress-nginx-controller-admission -n  ingress-nginx
Name:              ingress-nginx-controller-admission
Namespace:         ingress-nginx
Labels:            app.kubernetes.io/component=controllerapp.kubernetes.io/instance=ingress-nginxapp.kubernetes.io/managed-by=Helmapp.kubernetes.io/name=ingress-nginxapp.kubernetes.io/version=0.32.0helm.sh/chart=ingress-nginx-2.0.3
Annotations:       Selector:  app.kubernetes.io/component=controller,app.kubernetes.io/instance=ingress-nginx,app.kubernetes.io/name=ingress-nginx
Type:              ClusterIP
IP:                10.101.177.77
Port:              https-webhook  443/TCP
TargetPort:        webhook/TCP
Endpoints:         10.244.2.201:8443
Session Affinity:  None
Events:            <none>

[root@test ~]# curl https://ingress-nginx-controller-admission.ingress-nginx.svc:443
curl: (6) Could not resolve host: ingress-nginx-controller-admission.ingress-nginx.svc; Unknown error

无法解析？
检查 ingress-nginx-controller-admission.ingress-nginx.svc

[root@test ~]# kubectl get svc -n ingress-nginx
NAME                                 TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
ingress-nginx-controller             LoadBalancer   10.107.164.64   <pending>     80:31145/TCP,443:30277/TCP   4d18h
ingress-nginx-controller-admission   ClusterIP      10.101.177.77   <none>        443/TCP                      4d18h[root@test ~]# kubectl describe svc/ingress-nginx-controller-admission -n ingress-nginx
Name:              ingress-nginx-controller-admission
Namespace:         ingress-nginx
Labels:            app.kubernetes.io/component=controllerapp.kubernetes.io/instance=ingress-nginxapp.kubernetes.io/managed-by=Helmapp.kubernetes.io/name=ingress-nginxapp.kubernetes.io/version=0.32.0helm.sh/chart=ingress-nginx-2.0.3
Annotations:       Selector:  app.kubernetes.io/component=controller,app.kubernetes.io/instance=ingress-nginx,app.kubernetes.io/name=ingress-nginx
Type:              ClusterIP
IP:                10.101.177.77
Port:              https-webhook  443/TCP
TargetPort:        webhook/TCP
Endpoints:         10.244.2.201:8443
Session Affinity:  None
Events:            <none>
[root@test ~]#

太艰难了 5/25，上班忙到炸。 ingress已经折磨我好久了，这篇已经磨了一礼拜。过生日前让我release这篇吧。TAT
dns有问题，看一眼服务吧

[root@test ~]# kubectl get svc -n kube-system
NAME       TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)                  AGE
kube-dns   ClusterIP   10.96.0.10   <none>        53/UDP,53/TCP,9153/TCP   26d
# 把dns改了
[root@test ~]# vim /etc/resolv.conf
[root@test ~]# nslookup baidu.com
Server:         10.96.0.10
Address:        10.96.0.10#53Non-authoritative answer:
Name:   baidu.com
Address: 39.156.69.79
Name:   baidu.com
Address: 220.181.38.148

还是没用
又看到一篇：https://blog.csdn.net/u012986012/article/details/105453459
还是提到了webhook的问题
回到官网 https://kubernetes.io/zh/docs/reference/access-authn-authz/extensible-admission-controllers/
其中提到了失败策略
failurePolicy 定义了如何处理 admission webhook 中无法识别的错误和超时错误。允许的值为 Ignore 或 Fail。

Ignore 表示调用 webhook 的错误将被忽略并且允许 API 请求继续。
Fail 表示调用 webhook 的错误导致准入失败并且 API 请求被拒绝。

试试ignore吧或者关掉webhook?

在本片最顶上的一张图有两个关于webhook的资源
一个是https_webhook, 另一个是validatingWebhookConfiguration

即时配置 admission webhook
您可以通过 ValidatingWebhookConfiguration 或者 MutatingWebhookConfiguration 动态配置哪些资源要被哪些 admission webhook 处理。

好像找对路子了。
0526 今天deadline
先关掉试试
用edit 删除这三行
- --validating-webhook=:8443
- --validating-webhook-certificate=/usr/local/certificates/cert
- --validating-webhook-key=/usr/local/certificates/key
没啥用，不懂要怎么关，各位大神麻烦评论告诉我
加ignore试试
也是用edit

[root@test ~]# kubectl get ValidatingWebhookConfiguration/ingress-nginx-admission -n ingress-nginx
NAME                      WEBHOOKS   AGE
ingress-nginx-admission   1          7d1h
[root@test ~]# kubectl edit ValidatingWebhookConfiguration/ingress-nginx-admission -n ingress-nginx
validatingwebhookconfiguration.admissionregistration.k8s.io/ingress-nginx-admission edited
######下面是edit界面中的某一段
webhooks:
- admissionReviewVersions:
- v1beta1
clientConfig:caBundle: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUJPRENCM3FBREFnRUNBaEJOUUROWnBJcXR3TTJzaDg3YVVrSlpNQW9HQ0NxR1NNNDlCQU1DTUFBd0lCY04KTWpBd05URTVNVEl3TlRJMVdoZ1BNakV5TURBME1qVXhNakExTWpWYU1BQXdXVEFUQmdjcWhrak9QUUlCQmdncQpoa2pPUFFNQkJ3TkNBQVRDcWRWOWdVTm5yelY0Umg5NlIxYkl6R3lzQjE3UHJzc21CNDBGQjRPYU5MR28yMGwzCjJHYVpaTHNtN1dzblJva2FRcWpMOSs3NlBUQVBRSm9KS3BrYW96Z3dOakFPQmdOVkhROEJBZjhFQkFNQ0FnUXcKRXdZRFZSMGxCQXd3Q2dZSUt3WUJCUVVIQXdFd0R3WURWUjBUQVFIL0JBVXdBd0VCL3pBS0JnZ3Foa2pPUFFRRApBZ05KQURCR0FpRUE4K1A1WGlyOFgzREJEK1IvN2lIVWxzNXg3TW1UdjVMN1VzQzBJM3N2WmM4Q0lRQ2JSMUNpCkVOdEJ6N21CNU9KWG50RmdDblJLRkxjUVkxeWJ6bDVwTnlyZkZnPT0KLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo=service:name: ingress-nginx-controller-admissionnamespace: ingress-nginxpath: /extensions/v1beta1/ingressesport: 443
failurePolicy: Fail             ##################改成Ignore
matchPolicy: Exact
name: validate.nginx.ingress.kubernetes.io
#########################然后重新部署ingress.yaml
[root@test ~]# kubectl apply -f ingress.yaml
ingress.extensions/ingressmyapp created   
[root@test ~]#

TAT 谢天谢地。
但是照理说Fail不该动的，先欠着吧，这篇只是初体验。XD

验证篇

[root@test ~]# kubectl get ingress -n ingress-nginx
NAME           CLASS    HOSTS            ADDRESS   PORTS   AGE
ingressmyapp   <none>   pphqq.vicp.net             80      11m
########在describe时发现了error ####################################
[root@test ~]# kubectl describe ingress/ingressmyapp -n ingress-nginx
Name:             ingressmyapp
Namespace:        ingress-nginx
Address:
Default backend:  default-http-backend:80 (<error: endpoints "default-http-backend" not found>)
###########################为什么会找不到？ 
Rules:
Host            Path  Backends
----            ----  --------
pphqq.vicp.net/v1   myappsvc:80 (<error: endpoints "myappsvc" not found>)   ##    **所以必须在一个ns里？ ** 改完一个以后这个变成   /v1   myappsvc:80 (<none>)/v2   mappsvc2:80 (<error: endpoints "mappsvc2" not found>)#    v2是写错服务名，重新改
Annotations:      Events:
Type            Reason  Age   From                      Message
----            ------  ----  ----                      -------
Normal          CREATE  12m   nginx-ingress-controller  Ingress ingress-nginx/ingressmyapp

改完再看describe，现在看起来都已经有了

[root@test ~]# kubectl describe ingress/ingressmyapp -n ingress-nginx
Name:             ingressmyapp
Namespace:        ingress-nginx
Address:
Default backend:  default-http-backend:80 (<error: endpoints "default-http-backend" not found>)

###########################为什么会找不到？
#官网 Note: Depending on the Ingress controller you are using, you may need to create a default-http-backend Service.
Default Backend
An Ingress with no rules sends all traffic to a single default backend. The default backend is typically a configuration option of the Ingress controller and is not specified in your Ingress resources.

If none of the hosts or paths match the HTTP request in the Ingress objects, the traffic is routed to your default backend.
所以应该不影响。只有再不匹配路径是会转到默认。

Rules:Host            Path  Backends----            ----  --------pphqq.vicp.net/v1   myappsvc:80 (10.244.2.232:80,10.244.2.235:80,10.244.2.239:80 + 2 more...)/v2   myappsvc2:80 (10.244.2.231:80,10.244.2.236:80,10.244.2.237:80 + 2 more...)
Annotations:      Events:Type            Reason  Age    From                      Message----            ------  ----   ----                      -------Normal          CREATE  41m    nginx-ingress-controller  Ingress ingress-nginx/ingressmyappNormal          CREATE  7m10s  nginx-ingress-controller  Ingress ingress-nginx/ingressmyappNormal          UPDATE  77s    nginx-ingress-controller  Ingress ingress-nginx/ingressmyapp

验证放在第二篇吧。

查看全文
如若内容造成侵权/违法违规/事实不符，请联系编程学习网邮箱：809451989@qq.com进行投诉反馈，一经查实，立即删除！

Ubuntu20.04安装cuda10.1
安装前准备CUDA的主要用途是深度学习，而目前主流的深度学习框架Tensorflow2最高支持CUDA 10.1，因此本文讲解在Ubuntu 20.04系统上安装CUDA 10.1的主要过程。首先要查看你的NVIDIA显卡驱动是否支持cuda10.1版本。在终端执行以下命令： nvidia-smi如果 CUDA Version: … 这里的…...
2024/3/13 22:25:36
stm32F1xx（一） GPIO工作原理（正点原子P11）
一 GPIO基本原理与寄存器配置 1 GPIO基本结构和工作方式参考资料：战舰/精英STM32F1开发板《STM32F1开发指南-库函数版本》-第六章跑马灯实验6.1小节 miniSTM32F1开发板《STM32不完全手册-库函数版本》-第六章跑马灯实验6.1小节 STM32F1xx官方资料《STM32中文参考手册V1…...
2024/4/16 18:47:42
数据结构与算法学习---数据结构篇（图a）（默然回首，夯实基础）
一、图的入门 1.1 图的实际应用：现实生活中，有许多应用场景会包含很多点以及点点之间的连接，而这些应用场景我们都可以用即将要学习的图这种数据结构去解决地图：我们生活中经常使用的地图，基本上是由城市以及连接城市的道路组成，如果我们把城市看做是一个一个的点，把…...
2024/4/7 5:58:12
LINUX日志常用命令
杀僵尸进程部分程序员，肯定喜欢下面命令：ps -ef | grep java (先查java进程ID) kill -9 PID(生产环境谨慎使用) kill、killall、pkill命令的区别 kill：通过pid来杀死进程 killall （killall [参数] [进程名]）：Linux系统中的killall命令用于杀死指定名字的进程（kill pro…...
2024/3/13 22:25:26
7-1 jmu-Java-02基本语法-08-ArrayList入门 (20分)
本习题主要用于练习如何使用ArrayList来替换数组。新建1个ArrayList strList用来存放字符串，然后进行如下操作。提示:查询Jdk文档中的ArrayList。注意:请使用System.out.println(strList)输出列表元素。输入格式输入n个字符串，放入strList。直到输入为!!end!!时，结束输…...
2024/4/16 18:47:48
python暴力破解仿射密码
#暴力破解仿射密码def decrypt():k1 = [1,3,5,7,9,11,15,17,19,21,23,25]n = 1ny = []for i in k1:while (i * n) % 26 != 1:n += 1ny.append(n)f = open(cipher08.txt)w = open(plain08.txt,w)cipher = f.read()p = []for k1 in ny:for k2 in range(1,27):p.append(\n 逆元=+s…...
2024/4/16 18:47:30
maven基础部分
一.概述1.层次以及所用技术和浏览器相关:视图层，表示层，表现层{{视图层（H5 CSS JSP）控制层(servlet/action(struct2)/Handler(spring mvc)）}业务逻辑层{ Spring IOC AOP}持久化层（和数据库交互）{ JDBC/DBUtils/Spring JDBCTemplate/Hibernate/Mybatis}数据库 { Oracl…...
2024/3/14 2:21:01
深入理解张正友相机标定法：数学理论详细推导
最近在项目中需要在激光雷达（Lidar）和相机（Camera）之间进行标定，即需要标定出相机内参和外参，使用的标定方法是张正友标定法，这里给出其数学理论推导过程。论文原文：《A Flexible New Technique for Camera Calibration》论文翻译：https://blog.csdn.net/humanking7/a…...
2024/3/30 17:51:52
lua调用C++函数崩溃时，查看lua的调用栈信息（特别适用于tolua++）
https://blog.csdn.net/mayao11/article/details/8267503...
2024/4/16 18:47:30
[R语言学习笔记] - R环境初始配置整合
本文涉及配置package目录重定向。下载镜像（Repository）重定向。配置整合 Rprofile.site 配置文件位于R内核的安装目录下。如果安装了多个版本的R内核，如原生3.6，原生4.0，微软Microsoft R Open，则根据自己的需求修改目标内核目录下的对应文件。例如我的路径为C:\Program …...
2024/4/16 18:47:30
小技巧：用 GitBook 组织 Markdown 文档
喜欢用 Markdown 写文档，那怎么把一个个 Markdown 文档组成在一起呢？这篇文章，分享了一个用 GitBook 来组织 Markdown 文档的办法。一起了解下吧。Markdown 是一种轻量级标记语言。只需人们纯文本编写文档，加上点标记符号，就能转成有格式的文档（如 HTML 富文本）。已广泛…...
2024/3/14 2:20:57
00012-layui 表格table刷新后，工具栏的按钮失效
工具栏按钮： <script type="text/html" id="taskListTable-toolbar"><div class="layui-btn-container"><button class="layui-btn layui-btn-sm" data-type="cancelTask">任务作废</button></…...
2024/4/16 18:47:12
MyCat实现——MySQL读写分离
环境配置参考：https://blog.csdn.net/u012948302/article/details/78902092一、安装jdk二、github下载解压mycat2.1、全部下下来，选择自己需要的版本2.2、拷贝到linux中，解压tar -zxvf jdk-8u151-linux-x64.tar.gz2.3、测试、启动mycat[root@localhost bin]# /usr/local/myc…...
2024/4/16 18:47:12
XGBoost实践
XGBoost实践...
2024/3/13 22:25:05
街景字符-字符识别模型
运行官网论坛给出的baseline代码：https://tianchi.aliyun.com/notebook-ai/detail?spm=5176.12586969.1002.3.2ce832bc6BfoeY&postId=108342思路：把每个图的结果对应为出5个数字之内的数字猜测。torch.utils.data.DataLoader函数：数据加载器，结合了数据集和取样器，并…...
2024/4/16 18:47:12
当fixed 遇见transform
今天有个同事请教问题： fixed布局失效，他给我说是根据父级定位，开发将近5年的我郁闷不已，主要是他还拿出了实例，后经作者一番搜索之后，发现 fixed遇见父级有 transform的会失效。。。。参考：张鑫旭大神效果如图：...
2024/4/16 18:48:12
python3 str.decode()报错
代码 child=os.path.join(%s/%s%(filepath,childDir)) print(child.decode(gbk))# .decode(gbk)是解决中文显示乱码问题报错提示 line 7, in readFile print(child.decode())# .decode(‘gbk’)是解决中文显示乱码问题 AttributeError: ‘str’ object has no attribute ‘deco…...
2024/4/16 18:48:36
从JVM开始聊GC
本次聊聊GC 书的搬运工一、JVM 1.组成a.JAVA栈b.本地方法栈c.JAVA堆d.--方法区即永久区1.7以后放于堆2.释义a.JAVA栈 :线程私有。由一系列帧组成，也称为帧栈。保存了局部变量表、操作数栈、常量池指针。b.本地方法栈。Native外部调用。c.JAVA堆：私有线程共享堆[全局共享]。应…...
2024/4/16 18:48:24
定时调用之setTimeout
setTimeout //语法规则：window.setTimeout(调用函数，延时时间)； //1 这个window在调用的时候可以省略 //2 这个延时时间单位是毫秒,但是可以省略，如果省略默认就是0 //3 这个调用函数可以直接写函数还可以直接写函数名还有一个写法 ‘函数名()’ //4 页面中可能会有多个定…...
2024/4/15 7:06:39
Unity单例模式实现跨场景通讯
单例模式是当只需要一个实例体的时候，比如游戏的管理、声音的管理等。相当于这个类只需要创建一个对象，不需要创建其他对象的时候，一般使用单例模式，属于一种设计模式。特点是调用一些属性时不需要获取到这个对象，通过类名来访问其中的一个静态变量。单例模式可以在不同场…...
2024/4/16 18:48:36

k8s_难产的ingress架构初体验（一）