text:
Mimic 2.5 UI Warning for Node Problems in 2.6

Detailed Description
In Rancher 2.5, when viewing clusters (/clusters), a UI warning was present if a node in a cluster was having problems.
In Rancher 2.6, when viewing clusters (Cluster Management), there are no UI warnings if a cluster is having problems. You are required to click 'into' the cluster, to see that there are node problems.
Having the ability to glance at all of your clusters and see any problems is a great feature that should be brought back.
Rancher 2.5:

Rancher 2.6:

Duplicates https://github.com/rancher/dashboard/issues/5346

@neillsom This is a dup and will be fixed by the work you are doing for 5346

Observed warning for nodes with issues.

authors: HoustonDad floatingman nwmac


text:
UI fixes for list pages

[x] In list page for namespace, can we make the word "Project" in a different color so that the word is less prominent:

[x] In list page for any k8s resource, add Namespace: to the folder name so that it's clear that it's grouped by namespace. The name will be Namespace: <namespace_name>, which is similar to the Project: <project_name>. It's not obvious to new users that these groupings are namespace.

[ ] On the Namespace list page, the content inside the project grouping in the table is aligned better than the spacing for any other resources. In the resource list, the checkbox is too close to the left edge.

Namespace List View

Resource List View

The last item is still open. The spacing on other resources for where the checkbox is not the same as on the namespace page.

@vincent99 is looking at this becuase the check for column widths isn't working as expected.

https://github.com/rancher/dashboard/pull/751/commits/d41bb1f4f3ce8a370187507cf259dbd186885e24

source: gharchive/issue

authors: deniseschannon lvuch vincent99

repo: rancher/dashboard

license_type: permissive

license_source: github-api


text:
Unable to add git repo with basic auth secret failed to look up helmSecretName: secrets "fleet-default/<secret>" not found

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
I'm unable to deploy a repository using fleet with basic auth required (for either git or helm authentication)
Expected Behavior
users should be able to deploy a repo that requires authentication
Steps To Reproduce

deploy a git repo that requires some basic auth
wait for the deployment to get to an active state
repo fails with error Failed to look up helmSecretName, error: secrets "fleet-default/<secret>" not found
checking the fleet-default/secret in the local cluster, you can see that the secret was indeed created.

Environment
- Architecture: amd64
- Fleet Version: 0.6.0-rc5
- Cluster:
  - Provider: aws
  - Options: 3 nodes
  - Kubernetes Version: 1.25.6, rke1

Logs
{"conditions":[{"lastUpdateTime":"2023-03-30T18:03:36Z","message":"failed to look up helmSecretName, error: secrets \"fleet-default/auth-9qgqg\" not found","reason":"Error","status":"False","type":"Accepted"},{"lastUpdateTime":"2023-03-30T18:03:36Z","status":"True","type":"ImageSynced"}],"desiredReadyClusters":0,"display":{"readyBundleDeployments":"0/0"},"lastSyncedImageScanTime":null,"observedGeneration":0,"readyClusters":0,"resourceCounts":{"desiredReady":0,"missing":0,"modified":0,"notReady":0,"orphaned":0,"ready":0,"unknown":0,"waitApplied":0},"summary":{"desiredReady":0,"ready":0}} {"conditions":[{"lastUpdateTime":"2023-03-30T17:51:50Z","message":"failed to look up helmSecretName, error: secrets \"fleet-default/auth-mqt8j\" not found","reason":"Error","status":"False","type":"Accepted"},{"lastUpdateTime":"2023-03-30T17:51:50Z","status":"True","type":"ImageSynced"}],"desiredReadyClusters":0,"display":{"readyBundleDeployments":"0/0"},"lastSyncedImageScanTime":null,"observedGeneration":0,"readyClusters":0,"resourceCounts":{"desiredReady":0,"missing":0,"modified":0,"notReady":0,"orphaned":0,"ready":0,"unknown":0,"waitApplied":0},"summary":{"desiredReady":0,"ready":0}} {"commit":"3d38dd4054a62f355d051a9d5c34746f2f78aeca","conditions":[{"lastUpdateTime":"2023-03-30T18:12:52Z","status":"True","type":"Ready"},{"lastUpdateTime":"2023-03-30T18:17:11Z","status":"True","type":"Accepted"},{"lastUpdateTime":"2023-03-30T18:11:54Z","status":"True","type":"ImageSynced"},{"lastUpdateTime":"2023-03-30T18:11:54Z","status":"False","type":"Reconciling"},{"lastUpdateTime":"2023-03-30T18:11:54Z","status":"False","type":"Stalled"},{"lastUpdateTime":"2023-03-30T18:17:11Z","status":"True","type":"Synced"}],"desiredReadyClusters":2,"display":{"readyBundleDeployments":"2/2"},"gitJobStatus":"Current","lastSyncedImageScanTime":null,"observedGeneration":1,"readyClusters":2,"resourceCounts":{"desiredReady":6,"missing":0,"modified":0,"notReady":0,"orphaned":0,"ready":6,"unknown":0,"waitApplied":0},"resources":[{"apiVersion":"apps/v1","id":"fleet-mc-helm-example/frontend","kind":"Deployment","name":"frontend","namespace":"fleet-mc-helm-example","state":"Ready","type":"apps.deployment"},{"apiVersion":"apps/v1","id":"fleet-mc-helm-example/redis-master","kind":"Deployment","name":"redis-master","namespace":"fleet-mc-helm-example","state":"Ready","type":"apps.deployment"},{"apiVersion":"apps/v1","id":"fleet-mc-helm-example/redis-slave","kind":"Deployment","name":"redis-slave","namespace":"fleet-mc-helm-example","state":"Ready","type":"apps.deployment"},{"apiVersion":"v1","id":"fleet-mc-helm-example/frontend","kind":"Service","name":"frontend","namespace":"fleet-mc-helm-example","state":"Ready","type":"service"},{"apiVersion":"v1","id":"fleet-mc-helm-example/redis-master","kind":"Service","name":"redis-master","namespace":"fleet-mc-helm-example","state":"Ready","type":"service"},{"apiVersion":"v1","id":"fleet-mc-helm-example/redis-slave","kind":"Service","name":"redis-slave","namespace":"fleet-mc-helm-example","state":"Ready","type":"service"}],"summary":{"desiredReady":2,"ready":2}} {"commit":"3d38dd4054a62f355d051a9d5c34746f2f78aeca","conditions":[{"lastUpdateTime":"2023-03-30T17:44:22Z","status":"True","type":"Ready"},{"lastUpdateTime":"2023-03-30T17:44:23Z","status":"True","type":"Accepted"},{"lastUpdateTime":"2023-03-30T17:44:22Z","status":"True","type":"ImageSynced"},{"lastUpdateTime":"2023-03-30T17:44:23Z","status":"False","type":"Reconciling"},{"lastUpdateTime":"2023-03-30T17:44:23Z","status":"False","type":"Stalled"},{"lastUpdateTime":"2023-03-30T17:44:23Z","message":"secrets \"fleet-default/auth-bkjvv\" not found","reason":"Error","status":"False","type":"Synced"}],"desiredReadyClusters":0,"display":{"readyBundleDeployments":"0/0","state":"GitUpdating"},"lastSyncedImageScanTime":null,"observedGeneration":1,"readyClusters":0,"resourceCounts":{"desiredReady":0,"missing":0,"modified":0,"notReady":0,"orphaned":0,"ready":0,"unknown":0,"waitApplied":0},"summary":{"desiredReady":0,"ready":0}}>

Anything else?

/backport v2.7.2

authors: mantis-toboggan-md slickwarren


text:
[FIX] Fixed some issues with driver pages

Summary
Fixes #11046
Fixes #10718

Fixed deactivate driver bulk action, fixed displaying driver id instead of name for drivers that do not have translation.
Occurred changes and/or fixed issues

Additionally, changed bulk activation action to follow pattern similar to other models.
When provisioning a cluster, driver name is used instead of the id.
Technical notes summary

N/A
Areas or cases that should be tested

[] Test that driver name is shown instead of id for non-builtin driver
[] Test that driver can be activated on its own
[] Test that drivers can be activated in bulk
[] Test that driver can be deactivated on its own
[] Test that drivers can be deactivated in bulk
Areas which could experience regressions

Driver name is displayed instead of id inside of the cluster creation wizard.

Screenshot/Video

Checklist

[x] The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
[x] The PR has a Milestone
[x] The PR template has been filled out
[x] The PR has been self reviewed
[x] The PR has a reviewer assigned
[x] The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
[x] The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes

@aalves08 @richard-cox Adding you as reviewers, in case you have time to help review this and get this in.

If there are no overnight objections to my tweak, will merge tomorrow AM UK time

@richard-cox I think Eva is out, right? If it's approved can it be merged?

Yep, just been tickling gates after rebase.

source: gharchive/pull-request

authors: aalves08 eva-vashkevich nwmac richard-cox


text:
Add async/await tag to the RKE2 PSP check function

Summary
Fixes #8300

Occurred changes and/or fixed issues
Prevent blocking the editing in case of clusters RKE2 with version < 1.25.x without PSPs and status provisioning or updating.
Technical notes summary
Added missing async/await tag to the function.
Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

when checking psps with !!this.psps?.count;, if the cluster has psp's enabled but just doesn't contain any we'll return false. is that intended?  /**
   * Check presence of PSPs as template or CLI creation
   */
  hasPsps() {
    return !!this.psps?.count;
  },

Yes, it's intended to inform people of PSPs deletion/invalidation, so it would make no sense if there's none.


text:
Automate docs team notification for release notes

This is a clean version of #9767

Summary
This solely pertains to the Github repo and internal processes.  It adds a Github action that automatically emails the docs team about release notes.

We use the release-note label to indicate issues that should be added to the release notes. However, unless an engineer or manager alerts the docs team, the docs team receives no notice that the issue needs to be added. Docs writers need to manually check the repo frequently to make sure they don't miss any issues during the release cycle. This can be especially hectic and failure-prone towards the end of a release.
This PR adds a brief (10-14 second) Github action that automatically adds a comment to issues labeled with release-note. The comment pings the docs team recipients listed in the .yml, which triggers an email notification that alerts them that an issue needs a release note.
See https://github.com/jenschelkopf/issue-label-notification-action for details on the Github action.

@richard-cox new PR with clean commit history, as promised

@martyav The workflow fails with
[Error: .github#L1]
jenschelkopf/issue-label-notification-action@1.3 is not allowed to be used in rancher/dashboard. Actions in this workflow must be: within a repository owned by rancher or matching the following: actions/checkout@*, actions/download-artifact@*, actions/setup-node@*, actions/upload-artifact@*, codecov/codecov-action@*, peaceiris/actions-gh-pages@v3, tj-actions/changed-files@*, github/issue-labeler@v2.5.

https://github.com/rancher/dashboard/actions/runs/6352953763
I can take a look on Monday, if not please do prod me

authors: martyav richard-cox


text:
Bump yip

The result of:

go get github.com/mudler/yip@v1.4.6
go mod tidy
go vendor

Fixes #1849

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (1a1b942) 75.96% compared to head (ba9583b) 75.96%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1872   +/-   ##
=======================================
  Coverage   75.96%   75.96%
=======================================
  Files          66       66
  Lines        6912     6912
=======================================
  Hits         5251     5251
  Misses       1290     1290
  Partials      371      371

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter davidcassany

repo: rancher/elemental-toolkit