feat: add a button for Deployment/Statefulset logs

[doncicuto]

closes #257

📑 Description

This PR adds a button to show deployment and statefulset logs in the UI. Here are a couple of screenshots.

• Deployment logs

• Statefulset logs

✅ Checks

• I have updated the documentation as required
• I have performed a self-review of my code

Additional context

I've updated the handler.go to re-enable the endpoints required for this PR:

h.router.GET("/resources/deployments/:namespace/:deployment/:container/logs", modulesController.GetDeploymentLogs)
h.router.GET("/resources/statefulsets/:namespace/:name/:container/logs", modulesController.GetStatefulSetsLogs)

[petar-cvit]

Hey @doncicuto, sorry for the delay. Can we somehow move the Logs button so its not in a separate section? I'm thinking of moving it up alongside the Manifest button, but that manifest button is not defined by a resource component.

Could you maybe move the manifest button in each component so we can add Logs and Manifest in the same row?

[doncicuto]

Hi @petar-cvit I'll try to update the PR following your requirements. Thanks!

[doncicuto]

Hi @petar-cvit, I think the button issue is fixed:

[petar-cvit]

Thanks @doncicuto, looks good. I just left one comment on the component organization. Also, we merged one other PR so you will have to resolve some conflicts

[petar-cvit]

Can we move this button to specific resource components? The only reason why I would do it is so because we don't have one row implemented in different components

[doncicuto]

Hi @petar-cvit, no problem, so you want me to move the Manifest button to all components found in the k8s-resources folder?

[petar-cvit]

yeah, that way we can add/remove buttons depending on the kind. I suppose it's not going to be a lot of copy pasted code if we extract those buttons into separate components and reuse them in k8s resources components

[petar-cvit]

@doncicuto, any updates on the PR?

[doncicuto]

I'm deeply sorry Petar I've been pretty busy these months and I don't think I can resume my collaboration right now so to be honest it's better to unassign this issue to me. I like the project so I Will definitely help again on the future as soon as I get more free time.

[petar-cvit]

@doncicuto no worries, I will close this one then