Skip to content
This repository was archived by the owner on Sep 6, 2022. It is now read-only.

Commit e367adb

Browse files
committed
Add failure related to delay in DNS propagation
1 parent febd436 commit e367adb

File tree

1 file changed

+24
-0
lines changed

1 file changed

+24
-0
lines changed

README.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,30 @@ The whole process takes around twenty minutes. In the end, the following resourc
4040

4141
*After increasing the quota, retry the installation running `make install`*
4242

43+
- Some pods never start (`Init` state)
44+
45+
```shell
46+
❯ kubectl get pods -l component=proxy
47+
NAME READY STATUS RESTARTS AGE
48+
proxy-5998488f4c-t8vkh 0/1 Init 0/1 0 5m
49+
```
50+
51+
One of the reason could be related to the [DNS01 challenge](https://cert-manager.io/docs/configuration/acme/dns01/) validation for the wildcard certificates can take several minutes (*DNS propagation*).
52+
So, once the Certificate is `Ready`, maybe it will be needed to restart the deployments
53+
54+
```shell
55+
❯ kubectl get certificate
56+
NAME READY SECRET AGE
57+
proxy-config-certificates True proxy-config-certificates 5m
58+
```
59+
60+
running the commands:
61+
62+
```shell
63+
kubectl rollout restart deployment/server
64+
kubectl rollout restart deployment/ws-proxy
65+
```
66+
4367
## Verify the installation
4468

4569
First, check that Gitpod components are running.

0 commit comments

Comments
 (0)