-
This card is about tracking the status of the upgrade group somewhere within the UI, which basically results in keep some sort of status of it in ManagedOSImage or any other related resource.
See h…
-
hi!
I was looking through this repo as an example Holochain project to help me understand good structuring / practices. it has been helpful in that way - thanks 🙂
when I follow the steps in the …
-
This issue is about porting the image building functionality from the current [elemental-operator](https://github.com/rancher/elemental-operator).
Due to the absence of the Rancher API, this will sli…
-
Upgrading rancher 2.7.1 to 2.7.2 shouldn't allow the usage of Elemental 1.0.0.
I think we should consider replacing the Elemental dashboard with a disclaimer saying that the user should update thei…
-
Hi Elemental-UI members,
Do you have a plan to improve the performance of the components?
I'm trying to rebuild my company's UI system based on elemental-ui. However, to be used in a big product, th…
-
**Setup**
- Rancher version: 2.6.8
- Rancher-dashboard branch: elemental-dev
**Describe the bug**
**Context:** Test upgrade in the UI
When you upgrade a node, there is no easy way to follow…
juadk updated
2 years ago
-
As discussed yesterday with @aalves08, I was able to install elemental-ui extension 1.1.0 in rancher 2.7.1:
```
helm upgrade --install rancher rancher-latest/rancher --namespace cattle-system --cr…
-
When building installation media, it's also possible to select the target platform of the built image/iso.
Right now it could be a hardcoded list with `linux/x86_64` and `linux/arm64` and default t…
-
It's possible for the sort order to not be update-able after an element is moved.
There is some funkiness in the way the base elemental UI tells the backend what sort value to use.
In this example…
-
I believe it would be beneficial to enhance the logs by incorporating `container.id` alongside `ElasticApmTransactionID` and `ElasticApmTraceId` when using the log correlation feature. Currently, the …