Closed voor closed 2 years ago
Something that can let us change those values, even if it's temporarily:
i'm game for short term solution descirbed above => adding 2 annotations (i tweaked names a little bit):
ext.packaging.carvel.dev/helm-template-name: bob
ext.packaging.carvel.dev/helm-template-namespace: alice
Describe the problem/challenge you have We use AppCR currently and install packages from a privileged namespace (one that has more permissive roles) into another namespace(s) as a typical practice.
In particular, it's very common for us to have the following in our App CR:
Of note is the helm template including steps explicitly for name and namespace.
We are currently able to translate this to a
Package
that looks like this:And fit the values in properly with a PackageInstall that looks like this:
Note the inclusion of both the values and annotation of
external-dns-something
-- we're fine with this, it works, it's not great, but we have a way forward that's a workaround.We do not have a workaround for the parts marked
# THIS
-- the name and namespace that is passed into helm template. There is currently nothing in the Packaging API that would allow us to override this.For singletons, like metrics-server, or Harbor, or something that generally has "one of" we are not blocked, because the Package we make can hard-code this. However, for things that we like to deploy a lot of (databases, messaging, caching, etc.) we are stuck.
Describe the solution you'd like Something that can let us change those values, even if it's temporarily:
While you come up with a better UX and long-term fix.
Anything else you would like to add: We are happy with something short-term that unblocks us and eager to see a longer term plan around this level of customization.
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible" 👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.