如何解决Kubernetes Helm Artifactory 端口无法访问
我正在尝试使用 Minikube 和 Helm 3 安装 Artifactory
我正在遵循此处的说明以及我在此处和此处找到的其他一些内容: https://artifacthub.io/packages/helm/jfrog/artifactory-oss
我想我可能遗漏了一些关于暴露端口的明显内容。
据我所知,您需要启用“入口”?
所以:
minikube addons enable ingress
运行安装后,
$ cat namespace-artifactory.json
{
"apiVersion": "v1","kind": "Namespace","metadata": {
"name": "artifactory-oss","labels": {
"name": "artifactory-oss"
}
}
}
$ kubectl create -f namespace-artifactory.json
$ helm upgrade --install artifactory-oss --set artifactory.postgresql.postgresqlPassword=postgres_password --namespace artifactory-oss jfrog/artifactory-oss
Release "artifactory-oss" does not exist. Installing it now.
NAME: artifactory-oss
LAST DEPLOYED: Mon Apr 12 16:20:53 2021
NAMESPACE: artifactory-oss
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Congratulations. You have just deployed JFrog Artifactory OSS!
$ kubectl get namespace
NAME STATUS AGE
artifactory-oss Active 99s
default Active 6d
kube-node-lease Active 6d
kube-public Active 6d
kube-system Active 6d
kubernetes-dashboard Active 4d22h
$ kubectl get svc --namespace artifactory-oss
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
artifactory-oss-artifactory ClusterIP 10.98.138.1 <none> 8082/TCP,8081/TCP 100s
artifactory-oss-artifactory-nginx LoadBalancer 10.104.240.114 <pending> 80:32112/TCP,443:30681/TCP 100s
artifactory-oss-postgresql ClusterIP 10.100.119.202 <none> 5432/TCP 100s
artifactory-oss-postgresql-headless ClusterIP None <none> 5432/TCP 100s
$ kubectl --namespace artifactory-oss get pods
NAME READY STATUS RESTARTS AGE
artifactory-oss-artifactory-0 1/1 Running 0 2m23s
artifactory-oss-artifactory-nginx-75b745c955-ffgql 1/1 Running 0 2m23s
artifactory-oss-postgresql-0 1/1 Running 0 2m23s
$ kubectl logs --namespace artifactory-oss artifactory-oss-artifactory-0
... Server configuration reloaded on localhost:8046
... Server configuration reloaded on localhost:8049
... Server configuration reloaded on :8082
... frontend (jffe) service initialization completed in 40.24 seconds. Listening on port: port 8070
所以现在看起来它起作用了,也许,除了我无法访问任何端口。
- 集群 IP 不同。看起来很奇怪。
- 没有外部 IP。看起来很奇怪。
我使用 firewalld 打开了 8000-9000 范围内的端口:
public (active)
target: default
icmp-block-inversion: no
interfaces: ens192
sources:
services: dhcpv6-client ssh
ports: 8000-9000/tcp
protocols:
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules:
但是 80** 端口都没有遇到任何问题。
任何熟悉这个安装的人,或者知道我做错了什么?
谢谢
------------编辑 1:
kubectl --namespace artifactory-oss describe service artifactory-oss-artifactory-nginx
Name: artifactory-oss-artifactory-nginx
Namespace: artifactory-oss
Labels: app=artifactory
app.kubernetes.io/managed-by=Helm
chart=artifactory-11.13.0
component=nginx
heritage=Helm
release=artifactory-oss
Annotations: meta.helm.sh/release-name: artifactory-oss
meta.helm.sh/release-namespace: artifactory-oss
Selector: app=artifactory,component=nginx,release=artifactory-oss
Type: LoadBalancer
IP Families: <none>
IP: 10.104.240.114
IPs: 10.104.240.114
Port: http 80/TCP
TargetPort: 80/TCP
NodePort: http 32112/TCP
Endpoints: 172.17.0.2:80
Port: https 443/TCP
TargetPort: 443/TCP
NodePort: https 30681/TCP
Endpoints: 172.17.0.2:443
Session Affinity: None
External Traffic Policy: Cluster
Events: <none>
--------编辑 2:
minikube tunnel
Status:
machine: minikube
pid: 1380280
route: 10.96.0.0/12 -> 192.168.49.2
minikube: Running
services: [artifactory-oss-artifactory-nginx]
errors:
minikube: no errors
router: no errors
loadbalancer emulator: no errors
解决方法
查看为什么您的 nginx 入口是 <pending>
。
kubectl --namespace artifactory-oss describe service artifactory-oss-artifactory-nginx
我们在生产中使用它,它需要安装一个 nginx 入口引擎。 minikube 中可能需要的不仅仅是入口插件
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。