-
Notifications
You must be signed in to change notification settings - Fork 33
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
1.0 possible breakage list #76
Comments
|
spire-server.upstreamAuthority.certManager.ca.create could be set to true |
|
consider switching default identifiers to include nested names so taking non nested clusters and scale it out to multiple containers doesn't break things. |
base hostpath socket name on release.namespace-release.name by default so they don't conflict. |
In spire-agent, the value
could be collapsed into a general tools container along with the permissions fix init container. |
Fix up naming so there is consistency between |
moved to #454 |
moved to #454 |
moved to #454 |
We've tried hard to ensure backwards compatibility, a bit to the detriment of usability out of the box. Before 1.0.0 we may want to have one release where we change the defaults to be easier to use. This issue will track possible things to change.
The text was updated successfully, but these errors were encountered: