-
Notifications
You must be signed in to change notification settings - Fork 54
update to Go 1.15 #752
Comments
The problem is that Go 1.15 strengthens the certificate validation and no longer accepts just CN. Here's a naive attempt to fix this ("naive" as in "I have no idea how to specify SANs for cfssl"), but it didn't work:
Note that this also enables validation of the certificates generated by the operator. Otherwise "make test" only fails when using the cfssl certificates, but the operator code also needs to be updated. |
We probably need to migrate to the new behavior in stages:
|
Certificates with just CN and no SAN are not accepted anymore by default by the Go 1.15 runtime (https://golang.org/doc/go1.15#commonname). Before we update to Go 1.15, we need to restore support via the GODEBUG variable because otherwise upgrading to the upcoming PMEM-CSI release will break existing installations. This can be reverted once we are sure that all installations use certificates with SAN. Related-to: intel#752
Certificates with just CN and no SAN are not accepted anymore by default by the Go 1.15 runtime (https://golang.org/doc/go1.15#commonname). Before we update to Go 1.15, we need to restore support via the GODEBUG variable because otherwise upgrading to the upcoming PMEM-CSI release will break existing installations. This can be reverted once we are sure that all installations use certificates with SAN. Related-to: intel#752
Certificates with just CN and no SAN are not accepted anymore by default by the Go 1.15 runtime (https://golang.org/doc/go1.15#commonname). Before we update to Go 1.15, we need to restore support via the GODEBUG variable because otherwise upgrading to the upcoming PMEM-CSI release will break existing installations. This can be reverted once we are sure that all installations use certificates with SAN. Related-to: intel#752
An update to Go 1.15 without certificate creation changes is in: #753 |
Certificates with just CN and no SAN are not accepted anymore by default by the Go 1.15 runtime (https://golang.org/doc/go1.15#commonname). Before we update to Go 1.15, we need to restore support via the GODEBUG variable because otherwise upgrading to the upcoming PMEM-CSI release will break existing installations. This can be reverted once we are sure that all installations use certificates with SAN. Related-to: intel#752
Certificates with just CN and no SAN are not accepted anymore by default by the Go 1.15 runtime (https://golang.org/doc/go1.15#commonname). Before we update to Go 1.15, we need to restore support via the GODEBUG variable because otherwise upgrading to the upcoming PMEM-CSI release will break existing installations. This can be reverted once we are sure that all installations use certificates with SAN. Related-to: intel#752
And certificate creation was fixed in PR #755 |
We should do the next upcoming release (= 0.8) with a Go version that'll be supported for a while. Currently we use 1.13, which is getting old.
The text was updated successfully, but these errors were encountered: