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

Implement remaining parts for the Helm-direct plugin #3340

Closed
26 tasks done
antgamdia opened this issue Sep 1, 2021 · 3 comments
Closed
26 tasks done

Implement remaining parts for the Helm-direct plugin #3340

antgamdia opened this issue Sep 1, 2021 · 3 comments
Labels
component/apis-server Issue related to kubeapps api-server component/ui Issue related to kubeapps UI kind/feature An issue that reports a feature (approved) to be implemented

Comments

@antgamdia
Copy link
Contributor

antgamdia commented Sep 1, 2021

As #3085 and #3165 became really big issues (we tracked the status there), I'm opening this new one just to track the remaining or unfinished aspects preventing us from having a fully-working Helm-direct plugin.

Feel free to edit this issue to add something I might have missed.

Updated on September 30th

@antgamdia antgamdia added component/apis-server Issue related to kubeapps api-server component/ui Issue related to kubeapps UI kind/feature An issue that reports a feature (approved) to be implemented priority/high labels Sep 1, 2021
@absoludity
Copy link
Contributor

  * [ ]  Continue checking the issue in [Don't cache clients that are created (without auth) when app loads. #3338](https://github.com/kubeapps/kubeapps/pull/3338)
    
    * [ ]  Perhaps related to: `Response closed without grpc-status (Headers only)` in `GetInstaledPackageSummaries`

The problem that was addressed by #3338 was completely reproducible in a local environment when using token authentication, and is easy to demonstrate the fix in that PR fixing it. Not sure why you think that particular problem still needs investigating, or why it would be related to the Response closed without grpc-status issue?

Also, perhaps this issue could be merged with #3146.

@antgamdia
Copy link
Contributor Author

The problem that was addressed by #3338 was completely reproducible in a local environment when using token authentication, and is easy to demonstrate the fix in that PR fixing it. Not sure why you think that particular problem still needs investigating, or why it would be related to the Response closed without grpc-status issue?

Yes, not related at all. I just added that message during the release process, so that we don't forget about it. Edited now.

Also, perhaps this issue could be merged with #3146.

Yes... we have so many open ongoing issues that sometimes we just duplicate some content. Let's see if we can organize them better for the next iteration.

@antgamdia
Copy link
Contributor Author

Closing (FINALLY!!) as all the related PRs have already been merged 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/apis-server Issue related to kubeapps api-server component/ui Issue related to kubeapps UI kind/feature An issue that reports a feature (approved) to be implemented
Projects
None yet
Development

No branches or pull requests

3 participants