Replies: 2 comments
|
Currently there isn't a better way to do this though we have thought about things like spinning up a deployment in a throw away cluster to detect the pods that come up - #1277 - that implementation will require more thought / time though |
0 replies
|
Not super sure if this should be a separate discussion, however it would be nice if we could add annotations or something to give Like with in a CRD, example Crossplane provider: apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
name: provider-keycloak
spec:
package: xpkg.upbound.io/crossplane-contrib/provider-keycloak:v0.6.0So annotation of annotations:
zarf.dev/hint: ".spec.package"In that example I just use a similar syntax of |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
As a zarf user, it would be wonderful to understand if there are other ways to find images in the helm charts besides rendering the chart. This is very important because I want to improve the current solution I have to find images in operators, where I basically define a dummy deployment file with 0 replicas to help zarf find the image.
If this is already documented somewhere, a link to the documentation can also help.
Thanks
All reactions