-
Notifications
You must be signed in to change notification settings - Fork 111
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
[Feature] Display status of application changes even when they are not done in velaux #827
Comments
When use VelaUX to create app, the source of truth is VelaUX datastore. Now we have a syncer component in VelaUX to sync apps that not created by VelaUX into VelaUX. But they are read-only. |
How can I make use of the syncer component to view status of apps not made by velaux? Even if its read only that could be good enough for my teams use cases. |
I think for now it wouldn't work in your case. When app is first created in VelaUX, then deployed to cluster via clicking |
Applications don't show up on vela ux even of they are created by vela CLI. If they did that could be good enough. Is it a bug that they don't show up? Or do I need to add some sort of annotation or label for vela ux to start syncing it? |
That maybe related your version. That machenism works on a relative newer version. |
I'm using the latest version of velaux, v1.8.1 |
I'll try to create an application again to test, maybe I had a project filter or something on the last time I tried |
Will the application be displayed under a project based on the namespace it is deployed to? or will it only show up in the main applications page? |
Synced app will be in Default project. And it's environment is like `syc- if no corresponding env exist. |
Is your feature request related to a problem? Please describe.
If I use fluxcd or kubectl to update an application that was initially created in velaux, the status of that update or application is not displayed in velaux.
Describe the solution you'd like
VelaUX should sync changes made to application manifests on the cluster regardless of whether they are made within velaux or not.
Describe alternatives you've considered
We could have developers solely use velaux to change their application, but we are hoping to use a gitops approach where application manifests are stored in application repos and fluxcd watches for changes and updates them.
Additional context
The text was updated successfully, but these errors were encountered: