- labelSelector has two primary applicators
- matching utils function
- this should normally NOT be cached and not receive updates over sockets
- this is done by stipulating transient = true
- findLabelSelector
- this should normally be cached and receive updates
- this is done by stipulating transient = false
- when applicable (workload and services detail page) we want live updates whilst we're on the page
- we don't when we leave, so unwatch
- fix and align these two and their usages
- ensure each input (transient) is correct for context
- ensure response is in the correct format and handled correctly
- improved typing
Additionally
- Improve labelling for network policy ingress/egress label selectors
- Replace empty table with 'no details' in cis report detail page's list's sub row
- On services page handle the very weird use case of no visibility on pods
- Fix issue where extension catalog was not showing when refreshing on extension catalog page list
- Fixed an issue where we would ALWAYS show false positive invalid field warning in console
- Bump up default page size from 10k to 100k
- this is for requests we make to the new vai cache outside of pages
- it matches the default they use when proxying requests to target kube cluster
* Test / Wire in new label filtering to limited places
- Wired in to
- Workload detail page - pods and services (broken due to reverse selector)
- Service Detail - Pods List
- Service create/edit - Pod selector tab
- Also
- Fix showPodRestarts in random location
- TODOs
- Lots of testing / validation required
- reverse deployment --> service selector (not services given deployment, but for each service contains pods from deployment)
- workload model usages of pods getter
- services model usages of pods getter
- many many more....
* wired in, NOT tested
* improvement
* sdfdsf
* ryrty
* werer
* The great test off begins
* testing and tidying
* testing and tidying
* First good run
* tests, fixes and improvements
* updates
* Tidying up
* Fixes (namespace orientated), tweaks, updates
* Fix unit test
* Fixes for vai off
* Re-write `matching`
- handle namespaces better (given if the resource is namespaced
- better align with legacy matching fn (given specific scenarios that should return none or all)
* Lots of fixes, but mainly vai off --> pods list --> deployment detail --> pods list updates correctly
* fix lint, unit test
* e2e fix
* Fix weird plugins build validation failure (TS error on expected param for JS method with a default)
* Fix workload services
* changes following mini code review
* Only show pods tab if workload type supports it, always show pod resource table if tab is shown
Revert changes to object merge behavior because the existing behavior is destructive when merging deeply nested user values. For example, a default object contains the value:
```js
a: {
b: true,
c: true,
d: {
e: true,
f: {
g: true,
e: { },
f: [ ],
},
},
}
```
and a user value modifies `g`, which is stored as:
```js
a: {
d: {
f: {
g: false,
},
},
}
```
When the object is merged, deeply nested values will only be taken from the user values, causing properties to be lost. Furthermore, default properties for `f` can also be dropped. This operation is too destructive, and it's better to merge user-supplied properties with defaults than to drastically alter YAML altogether.
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
* refactor AssignTo, MoveModal and feature flag modal as prompt modals + add unit tests + remove store mechanisms that were dedicated to these modals
* fix small issues with FeatureFlagListDialog and MoveNamespaceDialog
* fix merge conflicts + remove code comments
* address merge conflicts + remove text from template
- make ported `createHeaders` schema null safe
- ensure node detail page handles no pods permissions
- both are pre 2.11 issues (though some code has changed locations)
* hide grouping controls for machines and machine pools in prov cluster details view corresponding tab
* Fix rke1 pool list
---------
Co-authored-by: Richard Cox <ricox@suse.com>
- their resource table elements turned these off
- this misconfiguration was ignored until grouping was fixed in https://github.com/rancher/dashboard/pull/11663
- specifically the addition of the if in computedGroupBy
```
computedGroupBy() {
// If we're not showing grouping options we shouldn't have a group by property
if (!this.showGrouping) {
return null;
}
```
- Add UnitInput field to edit/display the pollingInterval
- Add unit tests
- Add warning banners to inform about polling interval low value risks
- Scroll page to show warning banners
Signed-off-by: Francesco Torchia <francesco.torchia@suse.com>
* Add hooks to support virtual clusters
* Fix lint issues
* Refinements
* Update for Vue 3 changes
* Fix import
* Minor tweaks
* Fix bug causing e2e tests to fail
* Fix lint issue
* Rename internal properties and ensure they don't break clone/save
* Ensure we generate types for the plugins package to give us access to mapDriver
* Simpler approach
* Fix lint issues and add type
* Remove unused code
* Revery unnecessary changes
* Bug fix for finding model extension
* Factor out string constant and add provider display method
* Add experimental to API
* Update typegen.sh to use SHELL_DIR var
* Move type def
* Fix lint issue
* Address PR feedback
* Update steve-class.js so we always get an array
* Fix type definition