【原】关于使用openshift-V3无法自定义DNS解析

前段时间,参加2016红帽北京论坛,进一步了解了openshift相关内容,发现正符合我长久以来的需求,于是当天晚上便开始着手测试,测试过程中一切OK,唯独创建DNS解析的时候,V3的openshift好像不像是V2那样,直接提供测试链接。(至少我翻了半天没找到)

于是查手册查资料,最后在官方文档这里找到相关解释。(传送门:点我

e21c6def-cbdd-45c4-a202-630b6d1202e9

看到这行,终于找到DNSPOD的显性/隐性URL应该是啥了。

当然,<route-name>比较方便的就找到了(点击”Applications->Routes”,”Name”列即是。假设是”BBBBB”);可是, <namespace>又是在哪呢?我第一次开始搞的时候,没有留意这个namespace,于是采取了一个繁琐的方法,如下:

点击”Applications->Pods”,进入Pods列表界面,右上角有个”Actions”,点击,选择”Edit YAML”,在弹出的modal层中会看到”namespace: AAAAAA”。

综上,就可以组装成DNS的显性/隐性URL记录了,比如:

BBBBB-AAAAAA.44fs.preview.openshiftapps.com

最后进入DNSPOD解析页面,添加显性/隐性URL记录即可。

附官方教学视频(除DNS相关有不同外,其他可参考):Creating your first application with OpenShift Enterprise 3.0

《【原】关于使用openshift-V3无法自定义DNS解析》上有4条评论

  1. 我也是这个设置,但用绑定的顶级域名访问,显示 如下:

    Application is not available

    The application is currently not serving requests at this endpoint. It may not have been started or is still starting.

  2. 打开页面提示,博主你有解决方案吗

    Application is not available

    The application is currently not serving requests at this endpoint. It may not have been started or is still starting.

    Possible reasons you are seeing this page:

    The host doesn’t exist. Make sure the hostname was typed correctly and that a route matching this hostname exists.
    The host exists, but doesn’t have a matching path. Check if the URL path was typed correctly and that the route was created using the desired path.
    Route and path matches, but all pods are down. Make sure that the resources exposed by this route (pods, services, deployment configs, etc) have at least one pod running.

发表评论

电子邮件地址不会被公开。 必填项已用*标注