Replies: 1 comment
|
在检查 istio 代码之后,我发现在 istio 1.27 里,first_party_jwt 这种认证方式已经被彻底禁用了。你可以改为安装 Higress 2.1.x 系列中的最高版本 2.1.11 来在不支持 third_party_jwt 的低版本 K8s 集群中使用 Higress。但这个版本后续不会迭代了。 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
环境:
k8s版本:v1.20.9
docker版本:19.03.15
Higress版本:2.2.3
Helm版本:v3.10.3
背景:
1、Linux龙蜥7.9服务器版本,离线环境安装,纯k8s无istio。
2、kubectl describe pod 查看使用的JWT_POLICY是first-party-jwt
部署方式:
1、在外网能联网环境下载helm-charts文件和higress镜像文件(console.tar、gateway.tar、higress.tar、pilot.tar、higress-plugin-server.tar)。
2、通过第一步下载的helm-charts文件,使用helm install higress -n higress-system ./higress --create-namespace安装。
安装成功后,higress-gateway status是Running,READY是0/1
错误日志:
1、gateway日志:
failed to sign CSR: create certificate: rpc error: code = Unauthenticated desc = request authenticate failure
resource default failed to sign: create certificate: rc error: code = Unauthenticated desc = request authenticate failure
failed to warm certificate: failed to generate workload certificate: create certificate: rpc error: code = Unauthenticated desc = request authenticate failure
failed to fetch token from file: open /var/run/secrets/tokens/istio-token: no such file or directory
2、controller日志:
Failed to authenticate client from 10.244.2.2:59550: Authenticator ClientCertAuthenticator: no verified chain is found; Authenticator KubeJWTAuthenticator: target JWT extraction error: no HTTP authorization header exists
All reactions