| Age | Commit message (Collapse) | Author |
|---|
|
Our current version of Cert-Manager does not uninstall
cleanly, and we must manually remove custom resource
definitions.
|
|
|
|
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.
|
|
|
|
- Set as uninstallable app
- Update docs
- Adjust specs
|
|
- JupyterHub must not be available (installed or updated)
|
|
- enabled uninstallation
- give it a specific uninstall message
- ajust specs
|
|
|
|
|
|
|
|
'58941-use-gitlab-serverless-with-existing-knative-installation' into 'master'
Resolve "Use GitLab serverless with existing Knative installation"
Closes #58941
See merge request gitlab-org/gitlab-ce!27173
|
|
|
|
Remove Kn services cache from Clusters::Application::Knative
Knative function can exist even if user did not installed Knative via
GitLab managed apps.
-> Move responsibility of finding services into the Cluster
-> Responsability is inside Clusters::Cluster::KnativeServiceFinder
-> Projects::Serverless::FunctionsFinder now calls depends solely on a
cluster to find the Kn services.
-> Detect Knative by resource presence instead of service presence
-> Mock knative_installed response temporarily for frontend to develop
Display loader while `installed === 'checking'`
Added frontend work to determine if Knative is installed
Memoize with_reactive_cache(*args, &block) to avoid race conditions
When calling with_reactive_cache more than once, it's possible that the
second call will already have the value populated. Therefore, in cases
where we need the sequential calls to have consistent results, we'd fall
under a race condition.
Check knative installation via Knative resource presence
Only load pods if Knative is discovered
Always return a response in FunctionsController#index
- Always indicate if Knative is installed, not installed or checking
- Always indicate the partial response for functions. Final response is
guaranteed when knative_installed is either true | false.
Adds specs for Clusters::Cluster#knative_services_finder
Fix method name when calling on specs
Add an explicit check for functions
Added an explicit check to see if there are any functions available
Fix Serverless feature spec
- we don't find knative installation via database anymore,
rather via Knative resource
Display error message for request timeouts
Display an error message if the request times out
Adds feature specs for when functions exist
Remove a test purposed hardcoded flag
Add ability to partially load functions
Added the ability to partially load functions on the frontend
Add frontend unit tests
Added tests for the new frontend additions
Generate new translations
Generated new frontend translations
Address review comments
Cleaned up the frontend unit test.
Added computed prop for `isInstalled`.
Move string to constant
Simplify nil to array conversion
Put knative_installed states in a frozen hash for better read
Pluralize list of Knative states
Quey services and pods filtering name
This way we don't need to filter the namespace in memory.
Also, the data we get from the network is much smaller.
Simplify cache_key and fix bug
- Simplifies the cache_key by removing namespace duplicate
- Fixes a bug with reactive_cache memoization
|
|
|
|
|
|
|
|
|
|
Instance level clusters were already mostly supported, this change adds
admin area controllers for cluster CRUD
|
|
In order to not miss any errors since we are not checking the return
value of update
|
|
Basically does the reverse of after_transition to :installed.
|
|
Add specs
|
|
Only prometheus can be uninstalled atm, the rest will be dealt with
later.
Presumption is that new application types will have uninstallation
implmemented at the same time.
|
|
|
|
|
|
|
|
|
|
|
|
A runner installed on a cluster will now use the
cluster's `cluster_type` as its `runner_type`.
|
|
|
|
|
|
https://gitlab.com/amit1rrr/gitlab-ce into restrict-jupyter-login
|
|
|
|
This could be potentially useful to all cluster applications.
Address followup issue https://gitlab.com/gitlab-org/gitlab-ce/issues/56524
|
|
|
|
|
|
Port generic Helm upgrade functionality to CE
See merge request gitlab-org/gitlab-ce!23924
|
|
- #update_errored? method def is redundant, already defined from state
machine
- #update_in_progress? moved to ApplicationStatus
- #ready_status becomes a constant. Previously it was extended in ee/ so
maybe that was why it's a instance method
|
|
Port from EE generic upgrade related functionality used to upgrade Helm
applications
Remove memoization which could be incorrect
It looks like we are memoizing without regard to the method's argument
so this could result in an incorrect upgrade_command
Remove `const_get` indirection now we are no longer in EE
|
|
Bump nginx-ingress chart to 1.1.2
See merge request gitlab-org/gitlab-ce!24203
|
|
|
|
|
|
|
|
|
|
Prefer to use after_transition
Closes #55306
See merge request gitlab-org/gitlab-ce!24107
|
|
Before_transition does not play nice when used with
OptimisticLocking and this can result in triggering
multiple events
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/55306
|
|
|
|
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
|
|
|
|
Ability to override Issuer Email for Cert Manager
See merge request gitlab-org/gitlab-ce!23503
|
