| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| | |
Block local URLs for Kubernetes integration
See merge request gitlab/gitlabhq!2901
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Use existing `public_url` validation to block various local urls. Note
that this validation will allow local urls if the "Allow requests to the
local network from hooks and services" admin setting is enabled.
Block KubeClient from using local addresses
It will also respect `allow_local_requests_from_hooks_and_services` so
if that is enabled KubeClinet will allow local addresses
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Remove application `#ready?`
See merge request gitlab-org/gitlab-ce!25128
|
| | | |
| | |
| | |
| | |
| | | |
Given https://github.com/helm/helm/issues/3338, I think that we should
exclude applications that are :update_errored, :updating as well.
|
| | |/
| |
| |
| |
| |
| | |
This could be potentially useful to all cluster applications.
Address followup issue https://gitlab.com/gitlab-org/gitlab-ce/issues/56524
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Remove TLD validation from cluster domain
Closes #57650
See merge request gitlab-org/gitlab-ce!25262
|
| | |/ |
|
| |/
|
|
|
|
| |
- Adds to specs the case where apps are also updated
- Rename scope calls on Gitlab::UsageData and Clusters::Cluster
- Removes a duplicated spec
|
| |\
| |
| |
| |
| | |
Validate k8s CA certificate at cluster creation
See merge request gitlab-org/gitlab-ce!24990
|
| | |
| |
| |
| |
| |
| | |
No certificate is still accepted, but if one is provided it must
be valid. Only run validation if the certificate has changed to
avoid making existing records invalid.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Remove #make_updated! as have #make_installed! now
Closes #57374
See merge request gitlab-org/gitlab-ce!24988
|
| | | |
| | |
| | |
| | |
| | | |
We can have multiple and conditional transistions in a event, so make
use of that.
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Fixes technical debt issues for cluster domain
Closes #57397
See merge request gitlab-org/gitlab-ce!25010
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Avoid using direct code on spec migration
- Removes milestone and point to issue, to avoid making fake promises
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/57397
|
| |/ / |
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
Moves domain setting to Clusters page
Closes #52363
See merge request gitlab-org/gitlab-ce!24580
|
| | |
| |
| |
| |
| |
| | |
- Changes help text on clusters form to make it more explicit.
- Removes unnecessary warnings on auto devops form
- Simplifies cluster methods logic
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
- Fixes multiple typos on AutoDevops script
- Add an alias to Clusters::Cluster#domain as base_domain, so it's more
descriptive
- Removes unnecessary memoization on qa specs
- Changes migration to a post migration to deal better with traffic on
big instances (like gitlab.com)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Changes domain field to be on the Cluster page show, removing it from
Auto DevOps setting. Also injects the new environment variable
KUBE_INGRESS_BASE_DOMAIN into kubernetes#predefined_variables.
Migration to move the information from ProjectAutoDevops#domain
to Clusters::Cluster#domain. As well as necessary modifications to qa
selectors
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/52363
|
| | |
| |
| |
| |
| |
| | |
This makes this consistent with :updated. And also avoids a potential
issue where an install errors which means that that the recorded version
won't necessarily reflect the version that is actually installed.
|
| |/
|
|
|
|
|
| |
Note: updating version column after :updating is not ideal in the
updating -> update_erroed case. This will mean that the application now
records the version as the version that failed to upgrade, not the
version that it is currently on.
|
| |
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |
|
|
|
|
|
| |
This is the 1st step for moving Auto DevOps domain into cluster
settings, whether is project or group.
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/52363
|
| | |
|
| |\
| |
| |
| |
| | |
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
|
| | |/ |
|
| |/ |
|
| | |
|
| |
|
|
|
| |
Many changes were also made to tests that expected this to default to
false.
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
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
|
| |/ |
|
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
'master'
Update cert-manager chart from v0.5.0 to v0.5.2
Closes #55716
See merge request gitlab-org/gitlab-ce!24025
|
| | |
| |
| |
| | |
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
|
| |\ \
| |/
|/|
| |
| |
| |
| |
| |
| | |
'master'
Handle nil terminals in Clusters::Platforms::Kubernetes
Closes #55551
See merge request gitlab-org/gitlab-ce!23925
|
| | |
| |
| |
| | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
Ability to override Issuer Email for Cert Manager
See merge request gitlab-org/gitlab-ce!23503
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Use group clusters when deploying (DeploymentPlatform)
See merge request gitlab-org/gitlab-ce!22308
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This also means we need to apply the `current_scope` otherwise this
method will return all clusters associated with the groups regardless of
any scopes applied to this method
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Rename ordered_group_clusters_for_project ->
ancestor_clusters_for_clusterable
- Improve name of order option. It makes much more sense to have `hierarchy_order: :asc`
and `hierarchy_order: :desc`
- Allow ancestor_clusters_for_clusterable for group
- Re-use code already present in Project
|
