Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Init containers are not visible in the Cluster Explorer UI #4840

Closed
leodotcloud opened this issue Feb 10, 2021 · 6 comments
Closed

Init containers are not visible in the Cluster Explorer UI #4840

leodotcloud opened this issue Feb 10, 2021 · 6 comments
Assignees
Milestone

Comments

@leodotcloud
Copy link

What kind of request is this (question/bug/enhancement/feature request):
bug

Steps to reproduce (least amount of steps as possible):

  • Create a pod using an init container.
  • Or use one of the existing canal pods in the System project/kube-system namespace

Result:

  • One can see/access the logs of the install-cni init container in the Cluster Manager UI.
  • The same container is missing in the Cluster Explorer UI.

Environment information

  • Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.5.5
  • Installation option (single install/HA): Both

gz#14633

gz#17564

@leodotcloud leodotcloud changed the title Init containers are visible in the Cluster Explorer UI Init containers are not visible in the Cluster Explorer UI Jul 22, 2021
@fvogl
Copy link

fvogl commented Oct 7, 2021

+1

@tompatib
Copy link

tompatib commented Oct 7, 2021

As with 2.6 version the "old" UI is not available anymore, this would be very nice to fix, please.

@gaktive gaktive transferred this issue from rancher/rancher Dec 30, 2021
@gaktive gaktive added this to the v2.6.4 milestone Dec 30, 2021
@gaktive
Copy link
Member

gaktive commented Dec 30, 2021

Internal reference: SURE-2741, SURE-3021

@vincent99
Copy link
Contributor

These are already in 2.6[.1+].

@richard-cox
Copy link
Member

richard-cox commented Jan 4, 2022

In the latest 2.6.4-bound code the logs for init containers are available as per other containers in the log window containers drop down.

image

@brudnak
Copy link
Member

brudnak commented Feb 7, 2022

My checks PASSED

Reproduction Environment

Not required.

These are already in 2.6[.1+].


Validation Environment

Component Version / Type
Rancher version v2.6-948355cc596b8466a77aec5276640425a5935852-head
Rancher cluster type Docker
Docker version 20.10.7, build 20.10.7-0ubuntu5~20.04.2
Helm version v2.16.8-rancher1
Downstream cluster type RKE1 Linode
Downstream K8s version v1.22.6-rancher1-1
Browser type Firefox
Browser version 96.0.3

Validation steps

  1. Starting from the default Rancher homepage /dashboard/home
  2. Click hamburger menu -> Cluster Management -> Explore (next to downstream RKE1 cluster)
  3. Click Workload -> Pods -> Only System Namespaces -> right click on canal pod in kube-system -> click View Logs -> Containers drop down list available

Logs for init containers are available as per other containers in the log window containers drop down.

@brudnak brudnak closed this as completed Feb 7, 2022
@zube zube bot removed the [zube]: Done label May 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants