Skip to content

Commit 553e282

Browse files
author
Katie Horne
authored
Release 1.30.0 (#952)
1 parent a1072d2 commit 553e282

File tree

22 files changed

+245
-52
lines changed

22 files changed

+245
-52
lines changed

‎admin/access-control/manage.md

+17-1
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,8 @@ article.
1616

1717
## Coder's OIDC claims
1818

19-
Coder expects the following [OIDC claims](https://developer.okta.com/blog/2017/07/25/oidc-primer-part-1#whats-a-claim)
19+
Coder expects the following
20+
[OIDC claims](https://developer.okta.com/blog/2017/07/25/oidc-primer-part-1#whats-a-claim)
2021
from your OIDC provider:
2122

2223
- `email` (required)
@@ -65,6 +66,21 @@ you:
6566
to log in with an email/password option when you've enabled OIDC
6667
authentication
6768

69+
### Logging
70+
71+
If you're having issues with your OIDC configuration, you can enable additional
72+
logging of OIDC tokens to aid in troubleshooting.
73+
74+
To do so, [update your Helm chart](../../guides/admin/helm-charts.md) and set
75+
the `OIDC_DEBUG` environment variable to `true`:
76+
77+
```yaml
78+
coderd:
79+
extraEnvs:
80+
- name: "OIDC_DEBUG"
81+
value: "true"
82+
```
83+
6884
### Disable built-in authentication
6985
7086
You can disable built-in authentication as an option for accessing Coder if you

‎admin/git.md

+21-6
Original file line numberDiff line numberDiff line change
@@ -26,8 +26,8 @@ Coder integrates with the following service providers for authentication and
2626
2727
Linking your Coder account with a git service provider is _not_ required.
2828
Instead, you can use Visual Studio Code with git, the command-line tool, and we
29-
expect that this combination will work with most hosting software or services.
30-
However, Coder doesn't test these and cannot provide recommendations or support.
29+
expect this combination to work with most hosting software or services. However,
30+
Coder doesn't test these and cannot provide recommendations or support.
3131

3232
> Ensure that your Git provider supports the keygen algorithm that Coder uses;
3333
> you can choose the algorithm in **Manage** > **Admin** > **Security** >
@@ -38,8 +38,16 @@ However, Coder doesn't test these and cannot provide recommendations or support.
3838
## Configuring OAuth
3939

4040
Before developers can link their accounts, you (or another site manager) must
41-
create an OAuth application with the appropriate providers. When registering,
42-
you'll be asked for the following details related to your Coder deployment.
41+
create an OAuth application with the appropriate providers. You can create as
42+
many OAuth applications as necessary.
43+
44+
1. Log into Coder as a site manager, and go to **Manage** > **Admin** > **Git
45+
OAuth**.
46+
1. Click **Add provider**.
47+
1. Select your **Provider** (e.g., GitHub, GitLab, or Bitbucket Server).
48+
1. Create an OAuth application with your Git provider and provide Coder with the
49+
requested details (the parameters required vary based on your Git provider).
50+
See the following sections for additional guidance.
4351

4452
### GitHub
4553

@@ -54,7 +62,9 @@ ask you for the following Coder parameters:
5462
`[your-coder-domain]/oauth/callback` (e.g.
5563
`https://coder.domain.com/oauth/callback`)
5664

57-
Then, provide your **Client ID** and **Client Secret** to Coder.
65+
Then, in Coder, provide a **Name** for your app, your **URL**, **Client ID**,
66+
and **Client Secret** to Coder. You can also provide an optional
67+
**Description**.
5868

5969
When done, click **Save**.
6070

@@ -73,7 +83,9 @@ enabled the following:
7383
- **Confidential**: Check this option
7484
- **API** (scope): Check this option
7585

76-
Then, provide your **Client ID** and **Client Secret** to Coder.
86+
Then, in Coder, provide a **Name** for your app, your **URL**, **Application
87+
ID**, and **Client Secret** to Coder. You can also provide an optional
88+
**Description**.
7789

7890
When done, click **Save**.
7991

@@ -93,4 +105,7 @@ For your newly created Application Link, provide the following values as your
93105
- **Public Key**: Your public key (available from the Coder Admin Configuration
94106
page)
95107

108+
Then, in Coder, provide a **Name** for your app, your **URL**, and, optionally,
109+
a **Description**.
110+
96111
When done, click **Save**.

‎admin/workspace-management/cvms/management.md

+16-2
Original file line numberDiff line numberDiff line change
@@ -9,13 +9,27 @@ a site manager must enable CVMs. To do so:
99
1. Go to **Manage > Admin > Infrastructure**.
1010
1. Toggle the **Enable Container-Based Virtual Machines** option to **Enable**.
1111

12-
This section also describes the customization features that Coder offers for
13-
CVMs:
12+
## Customization
13+
14+
Once you've enabled CVMs, you can customize the behavior of your deployment and
15+
workspaces.
1416

1517
![CVM Settings](../../../assets/admin/cvm-settings.png)
1618

1719
These settings will apply to workspaces **after** they have been rebuilt.
1820

21+
## Default workspaces to CVMs
22+
23+
Once you've enabled CVMs, you can control whether all new workspaces should be
24+
built as a CVM or not.
25+
26+
If you would like all newly created workspaces to be CVMs, toggle **Default to
27+
container-based virtual machines** to **On**.
28+
29+
> While this toggle changes the default workspace creation setting, users can still
30+
> override this setting. For example, if you enable CVMS and set them as the
31+
> default, a user can still create non-CVM workspaces (and vice versa).
32+
1933
## Caching
2034

2135
> Cached CVMs are currently an **alpha** feature.

‎admin/workspace-management/limits.md

+16
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
title: "Workspace limits"
3+
description: Learn how to limit the number of workspaces users can create.
4+
---
5+
6+
You can set the maximum number of workspaces that each user can create. To do
7+
so, [update your Helm chart](../../guides/admin/helm-charts.md) and set the
8+
`CODER_MAX_WORKSPACES_PER_USER` parameter to the maximum allowable number:
9+
10+
```yaml
11+
# Allow each user to create no more than 100 workspaces
12+
coderd:
13+
extraEnvs:
14+
- name: CODER_MAX_WORKSPACES_PER_USER
15+
value: 100
16+
```

‎admin/workspace-management/self-contained-builds.md

+20-12
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,35 @@
11
---
22
title: "Self-contained workspace builds"
3-
description: Learn how to enable self-contained workspace builds.
4-
state: alpha
3+
description: Learn how to toggle self-contained workspace builds.
54
---
65

7-
By default the Coder workspace boot sequence occurs remotely -- Coder uploads
8-
assets (including the Coder agent, code-server, and JetBrains Projector) from
9-
`coderd` to a workspace.
6+
Currently, there are two ways in which the workspace boot sequence can occur:
107

11-
However, Coder offers the option of using **self-contained workspace builds**.
12-
Enabling this option changes the Coder deployment so that workspaces control the
13-
boot sequence internally, with the workspace downloading assets from `coderd`.
8+
1. Remotely: Coder uploads assets (including the Coder agent, code-server, and
9+
JetBrains Projector) from `coderd` to a workspace.
10+
1. Self-contained: workspaces control the boot sequence internally; the
11+
workspace downloads assets from `coderd`. This requires `curl` to be
12+
available in the image.
1413

15-
> At this time, Coder does not support certificate injection with
16-
> self-contained workspace builds.
14+
Beginning with v1.30.0, the default is **self-contained workspace builds**,
15+
though site managers can toggle this feature off and opt for remote builds
16+
instead.
1717

18-
To enable self-contained workspace builds:
18+
> Coder plans to deprecate remote workspace builds in the future.
19+
20+
To toggle self-contained workspace builds:
1921

2022
1. Log into Coder.
2123
1. Go to Manage > Admin.
2224
1. On the Infrastructure page, scroll down to **Workspace container runtime**.
23-
1. Under **Enable self-contained workspace builds**, flip the toggle to **On**.
25+
1. Under **Enable self-contained workspace builds**, flip the toggle to **On**
26+
or **Off** as required.
2427
1. Click **Save workspaces**.
2528

2629
> Build errors are typically more verbose for remote builds than with
2730
> self-contained builds.
31+
32+
## Known issues
33+
34+
At this time, Coder does not support certificate injection with self-contained
35+
workspace builds.

‎assets/guides/admin/file-download.png

113 KB
Loading

‎changelog/1.30.0.md

+87
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
---
2+
title: "1.30.0"
3+
description: "Released on 04/27/2022"
4+
---
5+
6+
### Breaking changes ❗
7+
8+
There are no breaking changes in 1.30.0.
9+
10+
### Features ✨
11+
12+
- web: added
13+
[admin toggle that sets whether new workspaces are CVMs or not](../admin/workspace-management/cvms/management.md#default-workspaces-to-cvms)
14+
(if CVMs are enabled for the deployment).
15+
- web: added support for the use of
16+
[multiple Git OAuth providers](../admin/git.md).
17+
- web: added ability to
18+
[choose webRTC mode](../workspaces/preferences.md#networking).
19+
- infra: upgraded code-server to v4.3.0 (featuring VS Code v1.65.2).
20+
- infra: added ability for an admin to
21+
[disable the download files function](../guides/admin/disable-downloads.md)
22+
from the web IDE's tree view.
23+
- infra: added ability to toggle
24+
[logging of OIDC tokens](../admin/access-control/manage.md#logging).
25+
- infra: mounted additional NVIDIA GPU libraries (specifically the GL/GLX
26+
libraries) from the host into CVMs if users request GPUs.
27+
- infra: added `CODER_MAX_WORKSPACES_PER_USER` environment variable to `coderd`
28+
that
29+
[controls the maximum number of workspaces allowed to each user](../admin/workspace-management/limits.md).
30+
- infra: improved Bitbucket server account linking error messages to help debug
31+
integration issues.
32+
- infra: updated Coder so that
33+
[self-contained builds](../admin/workspace-management/self-contained-builds.md)
34+
are now the default.
35+
- infra: updated Sysbox to version 0.5.0.
36+
37+
### Bug fixes 🐛
38+
39+
- web: fixed issue where dev URLs created via configure scripts do not show in
40+
the UI without a manual refresh.
41+
- web: fixed issue with Projector navbar occasionally displaying.
42+
- web: fixed issue where JetBrains 2022.1 IDE versions would not open in
43+
Projector.
44+
- web: fixed issue with EC2 provider workspaces hanging on build if a filesystem
45+
issue prevented mounting user volumes.
46+
- web: fixed issue where creating/editing an audit log results in two audit log
47+
entries.
48+
- web: fixed issue where changes to the Git URL in dotfiles aren’t included in
49+
the audit log.
50+
- web: fixed issue where air-gapped deployments wouldn’t render “Open in Coder”
51+
buttons.
52+
- web: fixed issue where users could create new workspaces even when there were
53+
no workspace providers configured for the organization.
54+
- web: fixed metrics to track connections via SSH.
55+
- infra: fixed scan error on metrics table caused by float being scanned as int.
56+
- infra: fixed issue where the built-in provider respawns when `coderd`
57+
restarts.
58+
- infra: fixed issue where the Coder front-end attempts to reconnect to a
59+
workspace even when it is offline.
60+
- infra: updated Coder to return a 404 error instead of a 5xx error if `coderd`
61+
cannot reach a workspace.
62+
- infra: fixed issue where air-gapped deployments were unable to update admin
63+
configuration settings.
64+
65+
### Security updates 🔐
66+
67+
- infra: fixed issue with authorization controls that allowed unauthorized
68+
editing of shells and dotfiles.
69+
- infra: fixed issue where site managers could change a user’s login type to
70+
built-in, even when built-in authentication is disabled in favor of OIDC
71+
login.
72+
- infra: added validation to URIs used in dotfiles.
73+
74+
### Known issues 🔧
75+
76+
- web: the service banner (if enabled) reappears for all users, even if they've
77+
previously dismissed it.
78+
- web: using the web terminal in Coder can occasionally result in the connection
79+
being reset and needing to be restarted.
80+
- web: the **Switch workspace** drop-down menu shows a workspace's status as
81+
**Building** even though the build process is completed.
82+
- web: users installing v1.24 (or later) into an air-gapped environment cannot
83+
upload their license when prompted.
84+
- infra: workspaces using images without `curl` available (e.g.,
85+
`ubuntu:latest`) will fail to build on new Coder deployments with
86+
self-contained workspace builds enabled. The workaround is to use a base image
87+
with `curl` available (e.g., `codercom/enterprise-base:ubuntu`).

‎changelog/1.26.0.md renamed to ‎changelog/archive/1.26.0.md

File renamed without changes.

‎changelog/1.26.1.md renamed to ‎changelog/archive/1.26.1.md

File renamed without changes.

‎changelog/1.26.2.md renamed to ‎changelog/archive/1.26.2.md

File renamed without changes.

‎changelog/1.26.3.md renamed to ‎changelog/archive/1.26.3.md

File renamed without changes.

‎changelog/1.26.4.md renamed to ‎changelog/archive/1.26.4.md

File renamed without changes.

‎guides/admin/disable-downloads.md

+22
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
title: File download disabling
3+
description: Learn how to disable file downloading in Coder.
4+
---
5+
6+
For security and compliance purposes, Coder site managers may choose to disable
7+
the downloading of files from Coder's built-in IDEs:
8+
9+
![File actions download option](../../assets/guides/admin/file-download.png)
10+
11+
To do so,
12+
[update your deployment's workspace template policy](../../admin/templates.md)
13+
to include the following definition:
14+
15+
```yaml
16+
kubernetes:
17+
env:
18+
policy: append
19+
value:
20+
- key: "CS_DISABLE_FILE_DOWNLOADS"
21+
value: "1"
22+
```

‎guides/tls-certificates/azureDNS.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ the domain you're using for your Coder deployment.
8484
cert-manager:
8585

8686
```console
87-
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.7.1/cert-manager.yaml
87+
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.8.0/cert-manager.yaml
8888
```
8989

9090
1. Check that cert-manager installs correctly by running

‎guides/tls-certificates/cloudDNS.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Add cert-manager to your cluster
4545
running:
4646

4747
```console
48-
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.7.1/cert-manager.yaml
48+
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.8.0/cert-manager.yaml
4949
```
5050

5151
## Option 2: Helm

‎guides/tls-certificates/cloudflare.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ You must have:
3434
## Step 1: Add cert-manager to your Kubernetes cluster
3535

3636
```console
37-
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.7.1/cert-manager.yaml
37+
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.8.0/cert-manager.yaml
3838
```
3939

4040
More specifics can be found in the

‎guides/tls-certificates/route53.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ You should also:
4242
cert-manager:
4343

4444
```console
45-
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.7.1/cert-manager.yaml
45+
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.8.0/cert-manager.yaml
4646
```
4747

4848
1. Check that cert-manager installs correctly by running

0 commit comments

Comments
 (0)