You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- build KAS on build, enable via GITLAB_AGENT_KAS_ENABLED
(automatically enabled if GITLAB_KAS_ENABLED=true)
- Add built-in KAS config file
kas config: import upstream (v15.10.0 - d88f4b89)
- minimal parameterization
gitlab side:
- GITLAB_KAS_ENABLED
gitlab_rails['gitlab_kas_enabled'] for omnibus installation
- GITLAB_KAS_INTERNAL
gitlab_rails['gitlab_kas_internal_url'] for omnibus installation
- GITLAB_KAS_EXTERNAL
gitlab_rails['gitlab_kas_external_url'] for omnibus installation
- GITLAB_KAS_PROXY
gitlab_rails['gitlab_kas_external_k8s_proxy_url'] for omnibus installation
kas side:
- GITLAB_AGENT_KAS_ENABLED
gitlab_kas['enabled'] for omnibus installation
- GITLAB_AGENT_KAS_API_LISTEN_AUTHENTICATION_SECRET_FILE
gitlab_kas['internal_api_listen_authentication_secret_file']
- GITLAB_AGENT_KAS_PRIVATE_API_LISTEN_AUTHENTICATION_SECRET_FILE
used by both:
- GITLAB_KAS_SECRET
used as a value for
- gitlabhq/gitlab.yml : production.gitlab_kas.secret_file
- gitlab-agent/gitlab-kas_config.yaml : gitlab.authentication_secret_file
Prefix for parameters that only used by gitlab-agent/kas is "GITLAB_AGENT_KAS_"
Also add process to generate secret files for KAS
Update built-in KAS to 16.10.1, sync config
Update built-in gitlab-kas to v17.0.2, sync configuration
- Bump to v17.0.0, sync configuration
GitOps module have been removed. See upstream change:
https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/merge_requests/1436
- Bump: gitlab-kas 17.0.1
no change in configuration file
- Bump: gitlab-kas 17.0.2
no change in configuration file
Personal note:
I am still unable to successfully connect the agent from the WebUI.
The problem is that I don't know the correct way to do it in the first place,
so I have to check it out.
Stop gitlab_kas before restoring backup
It seems that kas has DB connection and blocks restoration
- Bump: gitlab-kas 18.1.0
reference configuration file have been renamed to kascfg_defaults.yaml
and does not contain full configurations
So I have to search a way to generate full configuration from .proto
or docs
GitLab agent server for Kubernetes (KAS) is disabled by default, but you can enable it by setting configuration parameter [`GITLAB_KAS_ENABLED`](#GITLAB_KAS_ENABLED) to true.
921
-
By default, built-in `gitlab-kas` is used. But you can use an external installation of KAS by setting internal URL for the GItLab backend. Corresponding configuration parameter is [`GITLAB_KAS_INTERNAL`](#GITLAB_KAS_INTERNAL).
922
-
You can specify user-facing URL by setting [`GITLAB_KAS_EXTERNAL`](#GITLAB_KAS_EXTERNAL). If you set up proxy URL, use `GITLAB_KAS_PROXY`.
920
+
GitLab agent server for Kubernetes (KAS) is disabled by default, but you can enable it by setting configuration parameter [`GITLAB_KAS_ENABLED`](#gitlab_kas_enabled) to true.
921
+
By default, built-in `gitlab-kas` is also enabled once you enable KAS feature. But you can use an external installation of KAS by setting internal URL for the GitLab backend. Corresponding configuration parameter is [`GITLAB_KAS_INTERNAL`](#gitlab_kas_internal).
922
+
You can specify user-facing URL by setting [`GITLAB_KAS_EXTERNAL`](#gitlab_kas_external). If you set up proxy URL, use `GITLAB_KAS_PROXY`.
923
923
924
-
You can specify custom secret file by setting [`GITLAB_KAS_SECRET`](#GITLAB_KAS_SECRET), [`GITLAB_KAS_API_AUTHENTICATION_SECRET_FILE`](#GITLAB_KAS_API_AUTHENTICATION_SECRET_FILE) and [`GITLAB_KAS_PRIVATE_API_AUTHENTICATION_SECRET_FILE`](#GITLAB_KAS_PRIVATE_API_AUTHENTICATION_SECRET_FILE). These secret files are automatically generated if they don't exist.
924
+
You can specify custom secret file by setting [`GITLAB_KAS_SECRET`](#gitlab_kas_secret). This secret file will be generated if they don't exist.
925
+
926
+
#### Built-in GitLab-Agent KAS
927
+
928
+
To control whether launch built-in `gitlab-kas` on container startup or not, you can use configuration parameter [`GITLAB_AGENT_KAS_ENABLED`](#gitlab_agent_kas_enabled).
929
+
930
+
You can specify custom secret file by setting [`GITLAB_AGENT_KAS_API_LISTEN_AUTHENTICATION_SECRET_FILE`](#gitlab_agent_kas_api_listen_authentication_secret_file) and [`GITLAB_AGENT_KAS_PRIVATE_API_LISTEN_AUTHENTICATION_SECRET_FILE`](#gitlab_agent_kas_private_api_listen_authentication_secret_file). These secret files also be generated if they don't exist.
925
931
926
932
Built-in KAS communicates to redis. The host and ports are set using `REDIS_HOST` and `REDIS_PORT`.
927
-
You can specify the password file path in `GITLAB_KAS_REDIS_PASSWORD_FILE`, but please do not set the parameter. We still do not support password authentication for Redis. The password file should contain the redis authentication password, but this is not currently done because there is no way to specify the redis password. So please let this parameter empty. See https://github.com/sameersbn/docker-gitlab/pull/1026
933
+
You can specify the password file path in `GITLAB_AGENT_KAS_REDIS_PASSWORD_FILE`, but please do not set the parameter. We still do not support password authentication for Redis. The password file should contain the redis authentication password, but this is not currently done because there is no way to specify the redis password. So please let this parameter empty. See [sameersbn/gitlab#1026](https://github.com/sameersbn/docker-gitlab/pull/1026)
928
934
929
935
Also note that KAS requires that environment variable `OWN_PRIVATE_API_URL` is set (e.g. `OWN_PRIVATE_API_URL=grpc://127.0.0.1:8155`). If not, the KAS service will keep restarting.
930
936
931
-
See official documentation : https://docs.gitlab.com/ee/administration/clusters/kas.html
937
+
See [official documentation](https://docs.gitlab.com/ee/administration/clusters/kas.html) for more detail.
932
938
933
939
#### Available Configuration Parameters
934
940
@@ -1272,19 +1278,23 @@ Internal URL for the GitLab backend. Defaults to `"grpc://localhost:8153"`
1272
1278
1273
1279
The URL to the Kubernetes API proxy (used by GitLab users). No default.
Control startup behavior of built-in KAS. `autostart` value in supervisor configuration for KAS will be set to this value. Default to [`GITLAB_KAS_ENABLED`](#gitlab_kas_enabled)
An authentication secret file to verify JWT token, for KAS API. If not exist, an secret file will be generated on startup. Defaults to `${GITLAB_INSTALL_DIR}/.gitlab_kas_api_secret`
1287
+
An authentication secret file to verify JWT token, for built-in KAS API. If not exist, an secret file will be generated on startup. Defaults to `${GITLAB_INSTALL_DIR}/.gitlab_kas_api_secret`
An authentication secret file to verify JWT token, for KAS internal API. If not exists, an secret file will be generated on startup. This is not "required", so please leave blank if you don't need it. No default.
1291
+
An authentication secret file to verify JWT token, for built-in KAS internal API. If not exists, an secret file will be generated on startup. This is not "required", so please leave blank if you don't need it. No default.
1282
1292
1283
-
##### `GITLAB_KAS_REDIS_PASSWORD_FILE`
1293
+
##### `GITLAB_AGENT_KAS_REDIS_PASSWORD_FILE`
1284
1294
1285
-
Path for the file that contains redis password. This is not "required", so please leave blank if you don't need it. No default.
1295
+
Path for the file that contains redis password to be used by built-in KAS. This is not "required", so please leave blank if you don't need it. No default.
1286
1296
1287
-
NOTE: We currently do not support password authentication between gitlab and redis. See https://github.com/sameersbn/docker-gitlab/pull/1026
1297
+
NOTE: We currently do not support password authentication between gitlab and redis. See [sameersbn/gitlab#1026](https://github.com/sameersbn/docker-gitlab/pull/1026)
0 commit comments