Kubernetes Ingress API 版本
networking.k8s.io/v1* `spec.backend` -> `spec.defaultBackend`
* `serviceName` -> `service.name`
* `servicePort` -> `service.port.name` (for string values)
* `servicePort` -> `service.port.number` (for numeric values)
* `pathType` no longer has a default value in v1; "Exact", "Prefix", or "ImplementationSpecific" must be specified
将所有入口 yaml 文件从extensions/v1beta1 转换为networking.k8s.io/v1 的最简单方法是什么。
看起来 kubectl Convert 在 v1.19 中已被弃用。
Kubernetes 版本：
kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.0", GitCommit:"e19964183377d0ec2052d1f1fa930c4d7575bd50", GitTreeState:"clean", BuildDate:"2020-08-26T14:30:33Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.0", GitCommit:"e19964183377d0ec2052d1f1fa930c4d7575bd50", GitTreeState:"clean", BuildDate:"2020-08-26T14:23:04Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}
使用 kubectl Convert 时出错：
kubectl convert -f ingress_4_10_1.yaml --output-version networking.k8s.io/v1
kubectl convert is DEPRECATED and will be removed in a future version.
In order to convert, kubectl apply the object to the cluster, then kubectl get at the desired version.
error: networking.Ingress is not suitable for converting to "networking.k8s.io/v1" in scheme "k8s.io/kubernetes/pkg/api/legacyscheme/scheme.go:30"
我的入口 yaml：
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: frontend
annotations:
kubernetes.io/ingress.class: "ing-class1"
spec:
rules:
- host: frontend.com
http:
paths:
- path: /web-frontend/frontend.php
backend:
serviceName: frontend
servicePort: 80
手工重写并不是那么困难，例如：
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: frontend
annotations:
kubernetes.io/ingress.class: "ing-class1"
spec:
rules:
- host: frontend.com
http:
paths:
- backend:
service:
name: frontend
port:
number: 80
path: /web-frontend/frontend.php
pathType: Exact
在 https://cloud.google.com/kubernetes-engine/docs/deprecations/apis-1-22#ingress-v122
中找到了所需更改的精彩摘要| 田野 | 改变 |
|---|---|
| 规格后端 | 重命名为spec.defaultBackend。 |
| 后端服务名称 | 重命名为service.name。 |
| 服务端口 | 数字后端 servicePort 字段重命名为 service.port.number。字符串后端 servicePort 字段重命名为 service.port.name。 |
| 路径类型 | 现在每个指定路径都需要。该值可以是：Prefix、Exact 或 ImplementSpecific。要匹配未定义的 v1beta1 行为，请使用 ImplementSpecific。 |
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ingress-srv
annotations:
kubernetes.io/ingress.class: "nginx"
spec:
rules:
- host: addtest.com
http:
paths:
- path: /add
pathType: Prefix
backend:
service:
name: add-srv
port:
number: 4000
这个 GIST 来为我做这项工作。下载它并根据口味进行调整。它非常简单，并且会根据 PyYAML 的默认设置进行一些意外的重新格式化，但至少在这里它完成了工作。
kubectl convert -f app-ingress.yaml --output-version networking.k8s.io/v1 > app-ingress-new.yaml
k8s-ingress-convert.ps1（Powershell）
Push-Location .
# Without this variable I was seeing
# Select-String would have file lock (read lock)
# and rename to -old.yaml would fail.
$ingress_v1beta_list = @(
Get-ChildItem -Recurse *.yml,*.yaml |
Where-Object name -NotLike *-old* |
Select-String Ingress -List |
ForEach-Object { Select-String -LP $_.Path v1beta } |
ForEach-Object { $_.path } );
$ingress_v1beta_list
foreach ($ki in $ingress_v1beta_list) {
Set-Location $ki/.. -Verbose
$kold=$ki.Replace('.yaml','-old.yaml').Replace('.yml','-old.yml');
Move-Item $ki $kold -Verbose;
Write-Warning "k8s converting $ki";
kubectl convert -f $kold --output-version networking.k8s.io/v1 > $ki
}
Pop-Location
正斜杠 /
路径在 Powershell 中的 Win10/Win11 上运行良好。尚未测试过，但可能也适用于 Linux 和 Mac b/c 使用正斜杠。与 git 和
.gitignore 配合使用效果最佳
*-old.yaml
*-old.yml
import yaml
def transform_yaml(file_name):
with open(file_name, "r") as f:
data = yaml.safe_load(f)
for item in data["items"]:
if item["kind"] == "Ingress" and item["apiVersion"] == "extensions/v1beta1":
item["apiVersion"] = "networking.k8s.io/v1"
for rule in item["spec"]["rules"]:
for path in rule["http"]["paths"]:
path["pathType"] = "ImplementationSpecific"
backend_data = path.pop("backend")
new_backend_data = {
"service": {
"name": backend_data["serviceName"],
"port": {"number": backend_data["servicePort"]},
}
}
path["backend"] = new_backend_data
with open("transformed_" + file_name, "w") as f:
yaml.dump(data, f)
convert
包含不适当的依赖项。
convert必然依赖于
internal类型（以便转换），但
kubectl不应依赖于这些类型。事实上，API 服务器之外的任何软件都不应该依赖于内部类型。 弃用计划是将
convert创建为插件或单独的二进制文件。所以该功能仍然存在；只是不在
kubectl。可能的选择：
kubectl convert