search

portainer / kubernetes-beta

Feedback for the BETA version of Portainer with Kubernetes support
19 stars 1 forks source link

[TOPIC] - Amazon EKS #5

Open deviantony opened 4 years ago

deviantony commented 4 years ago

We have not tested the deployment of the Portainer for Kubernetes BETA version in EKS.

Have any feedback about deploying and using the Portainer for Kubernetes BETA version in EKS?

Discuss it here.

ncresswell commented 4 years ago

Had one user report that the BETA successfully deploys and works fine on EKS with Kubernetes 1.14.8

tomasz-zylka-fluke commented 4 years ago

Hi team! Great job. I absolutely love using portainer and therefore I'm very interested in playing with beta on EKS. I deployed the BETA without any problems on EKS (kubernetes v1.14.8), using helm chart. Connected to local endpoint. So far so good - I have good feelings about it in general. The app is intuitive and simple. Spent like 1h on it and observed four issues:

  1. (bug) Most of Volumes are marked as 'Unused' - I'm sure they are not as I checked that via kubectl
  2. (feature request) [Applications view] I would love to have the possibility to select a given 'resource pool' to show only apps that belong to selected resource pool. Ahh maybe it's not that crucial as I can do it in 'Resource pool' view
  3. (feature request) I cannot find pods that do NOT belongs to any application. E.g. my jenkins instance running on kubernetes creates pods when needs to scale and execute jobs on those pods. I cannot find them in BETA.
  4. (usability bug) [Applications view / Port mappings] When 'Publishing mode' column has very long value, then I am not able to see 'Exposed port' and 'Container port' columns without scrolling the view (which is very inconvenient)

EDIT: added fourth issue

tomasz-zylka-fluke commented 4 years ago

Issues/comments no. 2, 3 and 4 actually belong to different topics than EKS.

deviantony commented 4 years ago

@tomasz-zylka-fluke thanks for the feedback !

To answer your questions:

  1. Volumes are only marked as used if they are used by Applications. At the moment, Applications are leveraging the following Kubernetes resources: Deployments, StatefulSets and DaemonSets. If your volumes are used by something else (likely isolated pods) then it will not be considered used by Portainer.

We'll investigate this.

  1. Yes, you can have a look at the applications running inside a specific resource pool by inspecting a resource pool although we can look at adding filters to the applications view.

  2. See my 1st answer and cross referenced here https://github.com/portainer/kubernetes-beta/issues/11#issuecomment-606467576

  3. The 4th one is referenced here https://github.com/portainer/kubernetes-beta/issues/11#issuecomment-606457643