检查Pod的日志时,即使Pod已启动并正在运行,也不会出现Pod错误

问题描述

我通过引用kubernetes.io安装了kubernetes仪表板,一切都很好(我编辑了pod并用Nodeport替换了cluster-ip)

enter image description here

,但仪表板在登录一段时间后没有响应。再次,我必须使用不记名令牌登录,并且再次在一段时间后重复该循环。当我使用kubectl logs podname检查日志时,由于该名称未找到任何Pod,因此会引发错误,但是如果我通过kubectl get pod,它将显示为Pod正在运行,甚至我也可以访问它。

解决方法

您需要使用@startuml title Touchgram Content Store entity Artist { * Name * Bio UsualLicense } entity PhysicalGallery { * Name * Address * Contact Description } entity OnlineGallery { * Name * WebAddress Description } entity PhysicalProduct { * Name Description } entity DigitalSale { * Price * Timestamp } note bottom of DigitalSale : All digital sales\nare totally anonymous\nvia online credit entity DigitalProduct { * Name * DownloadFile * Price License } entity DigitalAvail { * Price * DateRange Comments } Artist }o..|| DigitalProduct DigitalProduct }o..|| DigitalSale DigitalProduct }o..|| DigitalAvail DigitalProduct }o..|{ PhysicalProduct DigitalProduct <|-- Image DigitalProduct <|-- Sound DigitalProduct <|-- VisualEffect DigitalProduct <|-- Template Template }o..o{ DigitalProduct : "Uses Other\nProduct" note bottom of Template : Template Touchgrams\n(eg: greeting cards or memes)\nCan use digital products\nfrom many artists\nso license & sales would\ncascade through note bottom of DigitalAvail : By default,available\nas soon as in store\nbut restrictions can be added Artist }o..o{ PhysicalGallery : Exhibits at Artist }o..o{ OnlineGallery : Advertises OnlineGallery }o..o{ PhysicalGallery : Advertises PhysicalProduct }o..o{ OnlineGallery : Sold through PhysicalProduct }o..o{ PhysicalGallery : Shown at note "Normally one digital version\nwould exist of a canvas\nbut often offer prints\n\nconversely,more rarely\nmight do several digital\nversions of a work\neg: with different filters\nor even crop portions\n\nWe **do not** handle\nphysical sales" as N1 N1 .. PhysicalProduct @enduml 命令的-n标志来具有名称空间名称。如果没有名称空间名称,它将在kubectl logs名称空间中查找容器,但是您的容器位于default名称空间中。

kubernetes-dashboard

相关问答

依赖报错 idea导入项目后依赖报错,解决方案:https://blog....
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下...
错误1:gradle项目控制台输出为乱码 # 解决方案:https://bl...
错误还原:在查询的过程中,传入的workType为0时,该条件不起...
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct...