[Starlingx-discuss] Impact on Horizon and external access to StarlingX REST API

[Jose Mateus Oliveira, Reinildes]

Hello community,



Story https://storyboard.openstack.org/#!/story/2009811 tracks the enhancement of our default security configuration by the adoption of cert-manager certificates for platform certificates and HTTPS enablement on the initial StarlingX install.



This change will offer many benefits:

  *   Enhanced security and less manual work by having platform certificates auto renewal with cert-manager
  *   Enhanced security as cert-manager makes it easier to have certificates with shorter durations
  *   Enhanced security by having HTTPS enabled by default
  *

Having that said, there are some end-user impacts that are important for the community to be aware:

  *   Due to the HTTPS enablement, the horizon URL will default to https://<oam-floating-ip-address>:8443 and not http://<oam-floating-ip-address>:8080 as it is documented today.
  *   Also, because of HTTPS enablement, external scripts that connect to StarlingX REST API will need to be updated to use the HTTPS connection.



We are tracking the documentation changes. Please take a look at the spec proposal https://review.opendev.org/c/starlingx/specs/+/827175 for more details.



Thank you,

Rei

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20220309/33bb817e/attachment.htm>