- 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>

Disables the vue-i18n eslint rules for files
that are not able to be autofixed, this will
stop these offences causing pipeline failures
but they will need manual fixing.

Our current version of Cert-Manager does not uninstall
cleanly, and we must manually remove custom resource
definitions.

Only display the details of the cluster page when the cluster
exists. If it is in "creating" state, show a message and a spinner

Also creates specs

Only allow Helm to be uninstalled if it's the only app

- Remove Tiller leftovers after reser command
- Fixes specs and offenses

Adds changelog file

Fix reset_command specs

- After uninstalling the knative helm chart it's necessary to also
remove some leftover resources to allow the cluster to be clean
and knative to be reinstalleable.
- Adds knative uninstall disclaimer
- Uninstall ksvc before uninstalling knative

Make list of Knative and Ingres resources explicit

- To avoid deleting unwanted resources we are listing exact
which resources will be deleted rather than simply deleting any
resource that contains istio or knative words.

i18n linting for .vue files under the
app/assets/javascripts/clusters/ directory

João Cunha authored 5 years ago and Mayra Cabrera committed 5 years ago

- enabled uninstallation
- give it a specific uninstall message
- ajust specs

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.

This commit is the result of running `yarn eslint --fix` after enabling
the `no-implicit-coercion` ESLint rule.  This rule has been added to
our ESLint config here:

https://gitlab.com/gitlab-org/gitlab-eslint-config/merge_requests/14

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

- Vue confirmation modal implementation
- CSS tweaks for modal default height

- Separate cluster application UI state from server-side app status
- Use a state machine to determine cluster application next state
- Instead of using two variables to keep track of when an app
is installing or updating, just use the app status property and control
server-side and user events using the FSM service.

Implemented the toast component for success messages

- Create empty uninstall_button component.
- Add uninstallable property to application_row component.
- Display Uninstall button if app is uninstallable and it
is installed.

- Create installed property for cluster apps
- Pass installed property to the application_row component

Move cluster applications manager tests from karma to jest. Fixes
some migration issues related with timeouts, and HTTP request
expectations.

if there isn’t an ingress IP assigned for the cluster yet

A runner installed on a cluster will now use the
cluster's `cluster_type` as its `runner_type`.

When ingress application is installed, the cluster domain help text
is updated to indicate that ingress external ip can be used as the
cluster domain

Show a loading spinner while Ingress/Knative IP is being assigned

Uses a new factory method to DRY instantiation.

Added the functionality to edit the Knative domain

This reverts merge request !24485