Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update notes #479

Merged
merged 6 commits into from
Oct 24, 2024
Merged
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions charts/spire/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,9 +90,36 @@ We only support upgrading one major/minor version at a time. Version skipping is

### 0.24.X

You must upgrade spire-crds to 0.5.0+ before performing this upgrade.

As we approach 1.0.0, we would like to ensure all the values are well supported, follow convention, and allow additions in the future without major changes. In order to support this, we have made a bunch of minor changes to the values in this version. If you are upgrading from a previous version, please read these upgrade nodes carefully.

In order to make it easier to target specific SPIFFE IDs to workloads, a fallback feature was added to ClusterSPIFFEIDs so that a default ID will only apply when no others do. To change back to the previous behavior, use spire-server.controllerManager.identities.clusterSPIFFEIDs.default.fallback=false. The new default is likely to work well for you without changes.

We also set a hint of the ClusterSPIFFEID name on each entry created. This can be undone by setting the hint="" property on the ClusterSPIFFEID. Again, the new default here is unlikely to need changes.

We have added the remaining options needed for the SPIRE Server SQL data store plugin. We have removed `spire-server.dataStore.sql.plugin_data` section as it is no longer needed. If you are using it, please migrate
your settings to the ones under `spire-server.dataStore.sql`.
kfox1111 marked this conversation as resolved.
Show resolved Hide resolved

Other changes:

spire-server.federation.bundleEndpoint.refresh_hint -> spire-server.federation.bundleEndpoint.refreshHint
spire-server.nodeAttestor.k8sPsat -> spire-server.nodeAttestor.k8sPSAT
spire-server.nodeAttestor.externalK8sPsat -> spire-server.nodeAttestor.ExternalK8sPSAT
spire-server.notifier.k8sbundle -> spire-server.notifier.k8sBundle
spire-server.ca_subject -> spire-server.caSubject
spire-server.ca_subject.common_name -> spire-server.caSubject.commonName
spire-server.upstreamAuthority.certManager.issuer_name -> spire-server.upstreamAuthority.certManager.issuerName
spire-server.upstreamAuthority.certManager.issuer_kind -> spire-server.upstreamAuthority.certManager.issuerKind
spire-server.upstreamAuthority.certManager.issuer_group -> spire-server.upstreamAuthority.certManager.issuerGroup
spire-server.upstreamAuthority.certManager.kube_config_file -> spire-server.upstreamAuthority.certManager.kubeConfigFile
spire-agent.sds.defaultSvidName -> spire-agent.sds.defaultSVIDName
spire-agent.sds.disableSpiffeCertValidation -> spire-agent.sds.disableSPIFFECertValidation
spire-agent.sds.defaultSvidName -> spire-agent.sds.defaultSVIDName
spire-agent.nodeAttestor.k8sPsat -> spire-agent.nodeAttestor.k8sPSAT
faisal-memon marked this conversation as resolved.
Show resolved Hide resolved

Lastly, for users of spire-server.upstreamAuthority.certManager, a bug was discovered with templates not honoring global.spire.caSubject.*. It has been fixed, but may change values if your not careful. Please double check the new settings are what you need them to be before completing the upgrade.

### 0.23.X

In previous versions, the setting spire-agent.workloadAttestors.k8s.skipKubeletVerification was set to true by default. Starting in 0.23.x, we removed that setting and replaced it with
Expand Down
Loading