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

Explore Kubeapps distribution as Carvel package #4410

Closed
3 tasks done
ppbaena opened this issue Mar 10, 2022 · 2 comments
Closed
3 tasks done

Explore Kubeapps distribution as Carvel package #4410

ppbaena opened this issue Mar 10, 2022 · 2 comments
Assignees
Labels
component/project (To be removed) kind/feature An issue that reports a feature (approved) to be implemented

Comments

@ppbaena
Copy link
Collaborator

ppbaena commented Mar 10, 2022

Description:

As first step to add Kubeapps as a package of Tanzu Community Edition, it is necessary to revisit all requirements (here).

Once Kubeapps team will guarantee the compliance, a proposal will be sent to make Kubeapps available as a Tanzu package as part of Tanzu Community Edition.

Acceptance criteria

  • Revisit current status for distributing Kubeapps as a Carvel package
  • Revisit compliance with prerequisites
  • Create an issue to request to make Kubeapps available as a Tanzu package as part of Tanzu Community Edition.

Additional information

Interesting to take a look to the initial comments about Kubeapps in TCE (here)

@ppbaena ppbaena added kind/feature An issue that reports a feature (approved) to be implemented priority/high component/project (To be removed) labels Mar 10, 2022
@absoludity
Copy link
Contributor

I've been working on this as a background task (as it requires a few different communication points with carvel + bitnami teams).

@absoludity
Copy link
Contributor

I've created vmware-tanzu/community-edition#3732 with the details for the proposal, as well as the compliance with the prerequisites (ie. current feedback from slack is that we can use helm-template even though the TCE docs don't mention it). Also checked internally about current tooling for Kubeapps as carvel. Not yet sure how much we can re-use due to required input (public chart, not TAC chart) and output (git repo of source, rather than registry with package).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/project (To be removed) kind/feature An issue that reports a feature (approved) to be implemented
Projects
None yet
Development

No branches or pull requests

2 participants