When using an insecure registry; http: server gave HTTP response to HTTPS client
Bug #1882152 reported by
Joseph Borg
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Containerd Subordinate Charm |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
Due to containerd bug https:/
I've just re-tested this on 1.4.0-beta (which includes the patch from CRI) and it's been fixed.
This is a placeholder for the work we'll need to do to get this into CK, which I believe to be
1) Get containerd 1.4.0 into APT (imo, this would be so much easier as a snap).
2) Update the containerd config.toml template as the specs have changed slightly.
Revision history for this message
| Joseph Borg (joeborg) wrote | #1 |
| Changed in charm-containerd: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
To post a comment you must log in.
***config.toml***
[plugins.
[
endpoint = ["https:/
endpoint = ["http://
[
username = "admin"
password = "password"
*** pod.yaml ***
apiVersion: v1
kind: Pod
metadata:
name: test
namespace: default
spec:
containers:
- name: test
image: 34.235.
*** describe pod ***
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled <unknown> default-scheduler Successfully assigned default/test to ip-172-31-17-195
Normal Pulling 10m kubelet, ip-172-31-17-195 Pulling image "34.235.
Normal Pulled 10m kubelet, ip-172-31-17-195 Successfully pulled image "34.235.
Normal Created 10m kubelet, ip-172-31-17-195 Created container test
Normal Started 10m kubelet, ip-172-31-17-195 Started container test