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

[FluxCD Addon]Cannot see Resource Graph in Kustomization #487

Closed
chengleqi opened this issue Oct 3, 2022 · 5 comments · Fixed by kubevela/kubevela#4849
Closed

[FluxCD Addon]Cannot see Resource Graph in Kustomization #487

chengleqi opened this issue Oct 3, 2022 · 5 comments · Fixed by kubevela/kubevela#4849

Comments

@chengleqi
Copy link
Member

I have a Deployment resource and a Service resource in my Kustomization App But VelaUX didn't show these resource.

image

Expect
show all the resources like HelmRelease in the Resource Graph like below:
image

@wangyikewxgm
Copy link
Collaborator

The reason is there is a built-in topology-rule of helmRelease and it's sub-resources. Are you interested in contributing to solve this issue by adding a topology-rule for kutomize. Here are some related docs: https://kubevela.net/docs/platform-engineers/addon/addon-cue#auxiliary-resources , https://kubevela.net/docs/reference/topology-rule.

@chengleqi
Copy link
Member Author

Thanks. I'd like to tackle this one.
/assign

@chengleqi
Copy link
Member Author

I see. The HelmRelease type resource are built-in velaql .
I'd better put the kustomize rule in configmap and let vela merge it.

@chengleqi
Copy link
Member Author

chengleqi commented Oct 11, 2022

Hi guys. I found this can only be implemented by built-in velaql way like HelmRelease.

velaql can list all the resource the HelmRelease has because of the helmRelease2AnyListOption func but we cannot pass function or pass dynamic relevant labels through configmap. And a Deployment doesn't have OwnerReferences with its Kustomization so it also cannot be listed through GetOwnerReferences when the ListOption func is missed.

This time we can just add Kustomization type beside the HelmRelease but I think we should find a better way to improve the extendability of configmap way.

@wangyikewxgm @wonderflow @FogDong

@wonderflow
Copy link
Collaborator

pass dynamic relevant labels through configmap

This could be potential solution for extensibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants