Default spire-server port 443 (#308)

Changes the default service port for the spire-server to 443 to allow easier switching between internal access and external access through an ingress controller.

Signed-off-by: Kevin Fox <[email protected]>
Signed-off-by: Faisal Memon <[email protected]>
Co-authored-by: Faisal Memon <[email protected]>
This commit is contained in:
kfox1111
2024-04-11 12:29:28 -07:00
committed by GitHub
co-authored by Faisal Memon
parent 1ef979c4e7
commit 1bf3aa77ef
5 changed files with 10 additions and 7 deletions
+4 -1
View File
@@ -77,7 +77,10 @@ We only support upgrading one major version at a time. Version skipping isn't su
### 0.20.X
This release configures the entries managed by the spire-controller-manager to move into their own managed space within SPIRE. This should be transparent. In a future release, we will
- The default service port for the spire-server was changed to be port 443 to allow easier switching between internal access and external access through an ingress controller. For most users, this will be a transparent
change.
- This release configures the entries managed by the spire-controller-manager to move into their own managed space within SPIRE. This should be transparent. In a future release, we will
disable cleanup by default of the old space. This release lays the groundwork for future support for manually created entries in the SPIRE database without the spire-controller-manager
destroying them. It is supported in this release by manually setting spire-server.controllerManager.entryIDPrefixCleanup=false after successfully upgrading to the chart without the
setting and waiting for a spire-controller-manager sync.