-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add granular control of query service components #3485
Conversation
f96ad92
to
5b62bf1
Compare
1f31d6b
to
535cdf0
Compare
I see the following error when testing this branch with Is it that weaveworks/weave-gitops#2305 Will try it on the clean cluster again now. |
The same error. Can check main in an hour. |
Yeah, the UI works fine for me in the main branch, but in the current one I see the same error. |
@@ -213,16 +213,18 @@ cluster-controller: | |||
tag: v1.5.2 | |||
|
|||
#### Explorer | |||
# Turns on explorer to true | |||
enableExplorer: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change looks good!.. I think quite a few clusters (demoX, maybe some customers) etc will be using this old value.
We could complicate the code w/ a bunch of
{{- if or (.Values.explorer.enabled .Values.explorerEnabled) }}
But also users will notice the explorer has been disabled, check the release notes which will call this out, and turn it back on, no biggie I think? cc @enekofb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There will be a corresponding docs change: https://github.com/weaveworks/weave-gitops/pull/4088/files
If we think backwards compatibility is important here, I can add that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we are fine with having it:
- announced as a breaking change in the release notes and
- how users could adapt the configuration.
We have it marked as alpha https://docs.gitops.weave.works/docs/explorer/intro/ to given users the right expectations of: yes it improves the situation but is not yet proven to reach a level of maturity to be proven useful for range of scenario.
i definitely think after this change is in we shoudl engage with Steve F. and Darryl to get more feedback though in particular on the explorer-based UIs
@opudrovs Can you try rebasing, then doing a |
@jpellizzari yes, just a moment. |
46a94ed
to
5bf1d33
Compare
5bf1d33
to
17d720d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested with
explorer:
enabled: true
enabledFor:
- applications
- sources
- gitopssets
- templates
with these args
I could see Explorer enabled
but i dont see the other ones
looking at
To test locally, turn off the NATIVE_BUILD flag with unset NATIVE_BUILD, then the Helm chart values changes should work.
@@ -53,6 +53,10 @@ spec: | |||
{{ if .Values.explorer.cleaner.disabled }} | |||
- --explorer-cleaner-disabled=true | |||
{{- end }} | |||
|
|||
# {{- if .Values.explorer.enabledFor }} | |||
- --explorer-enabled-for=applications,sources |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what is the background of adding it as flag over adding it to the configmap https://github.com/weaveworks/weave-gitops-enterprise/blob/17d720df8a2c3fa36547537da6f17d6c1934e698/charts/mccp/templates/clusters-service/configmap.yaml#L58
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was a leftover debug line that has been fixed. We now iterate through the items in the Values.EnabledFor
field. This was also causing the issue you reported with gitopssets
not using Explorer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry, i mean passing configuration as runtime flags like this vs just adding them to the config map ?
it feels that having all configuration values in the configmap simplifies config management
@@ -213,16 +213,18 @@ cluster-controller: | |||
tag: v1.5.2 | |||
|
|||
#### Explorer | |||
# Turns on explorer to true | |||
enableExplorer: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we are fine with having it:
- announced as a breaking change in the release notes and
- how users could adapt the configuration.
We have it marked as alpha https://docs.gitops.weave.works/docs/explorer/intro/ to given users the right expectations of: yes it improves the situation but is not yet proven to reach a level of maturity to be proven useful for range of scenario.
i definitely think after this change is in we shoudl engage with Steve F. and Darryl to get more feedback though in particular on the explorer-based UIs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@enekofb My leftover debug efforts were causing issues where we didn't loop over the items in the |
191a08c
to
cfdbfc7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Super! Ive verified worked with all values selected and some selected 🚀
Limitation: my frontend review not of much value (as usual)
Doubts:
- asked some question on passing the configuration as command arguments vs configmap
- also let please add info on how we are going to communicate the breaking change: for example i recently have one with label added and the notes (add internal monitoring server for metrics and profiling #3500)
fe84c79
to
1bed81e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just small comment below
@@ -60,7 +59,7 @@ const WGApplicationsDashboard: FC = ({ className }: any) => { | |||
<OpenedPullRequest /> | |||
</Flex> | |||
<div className={className}> | |||
{useQueryServiceBackend ? ( | |||
{isQueryServiceEnabled ? ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we might want use isExplorerEnabled as we have other uis https://github.com/weaveworks/weave-gitops-enterprise/pull/3485/files#diff-b9da4e2b2d5014f5b181f3a2c849a4cfbe3f3ac4b537b618c0ecb24e650ba267R44
or the other way around isQueryServiceEnabled
... explorer seems clearer to me though
1bed81e
to
11acba5
Compare
We want to be able to enable and disable the Explorer and query service backend for different parts of the UI. Before this, it was a global on-off switch handled via feature flags. This commit adds a dedicated enpoint for us to hit to enable or disable components via the helm values file.
Consolidates all of the explorer related configuration options underneath the `enabled` yaml key for consistency.
11acba5
to
f08c34f
Compare
Closes #3424
Allow for granular controls of when
Explorer
replaces the current table UI/backend.To test locally, turn off the
NATIVE_BUILD
flag withunset NATIVE_BUILD
, then the Helm chart values changes should work.Breaking Change release note copy:
We have changed the way the
explorer
feature is enabled. It is now possible to enable or disableexplorer
on different parts of the application. Previously, there was a global toggle set in the Helm Chart values calledenableExplorer
. This flag has been replaced by two keys:explorer.enabled
andexplorer.enabledFor
:Adding or removing items from this list will control which parts of the UI utilize the explorer backend.
The current values that are supported for this key:
See this section of the docs for more info: https://docs.gitops.weave.works/docs/explorer/getting-started/