Kubernetes Helm Artifactory 端口无法访问

如何解决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 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 &lt;select id=&quot;xxx&quot;&gt; SELECT di.id, di.name, di.work_type, di.updated... &lt;where&gt; &lt;if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 &lt;property name=&quot;dynamic.classpath&quot; value=&quot;tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-