Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Show Knative install button on group/instance cluster pages
- Allow Knative to be installed on group/instance clusters
- Add feature specs for installing applications on group/instance
clusters
- Add changelog entry
- Update docs to reflect that Knative can now be installed on
group-level and instance-level clusters
|
|
|
|
Added the ability to see project deployments using a group cluster
|
|
Signed-off-by: Balasankar "Balu" C <balasankar@gitlab.com>
|
|
Only display the details of the cluster page when the cluster
exists. If it is in "creating" state, show a message and a spinner
|
|
Contemplate the scenario where a K8 managed application becomes
not_installable after being installable.
|
|
Use update term instead of update in the clusters managed app
implementation in order to make the implementation and UI
language more consistent.
|
|
They are used to indicate when knative domain name
has changed
|
|
The new component also implements several improvements in the
knative domain editor workflow:
- Display a loading spinner when saving changes in the domain name
- Display success toast message indicating changes were saved
successfully.
- Display error message in the contraty occurs
|
|
Added a changelog entry for the feature
|
|
|
|
|