-
Notifications
You must be signed in to change notification settings - Fork 459
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
Allow custom (non-propagating) stateful set metadata #2337
Conversation
11361b4
to
3d1425c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly looks good. Couple of minor ones.
pkg/client/applyconfiguration/minio.min.io/v2/statefulsetmetadata.go
Outdated
Show resolved
Hide resolved
pkg/client/applyconfiguration/minio.min.io/v2/statefulsetmetadata.go
Outdated
Show resolved
Hide resolved
f7b31a8
to
77fad77
Compare
83172e1
to
77fad77
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@ramondeklein could you please take a look at the failing tests. |
20780cb
to
e66492a
Compare
eb5c1e6
to
9cab4fe
Compare
9cab4fe
to
fe4a452
Compare
@cesnietor Done... |
Any chance a new release could be cut to catch this change? Thanks! |
This PR fixes #2318. This PR will remove all automatic propagation of metadata from the
Tenant
resource to the child resources (statefulset, pod, service, pvc)..spec.poolsMetadata.Annotations
/.spec.poolsMetadata.Labels
. Per-pool labels/annotations can be set using.spec.pools[].Annotations
or.spec.pools[].Labels
..spec.serviceMetadata
. There are custom options for MinIO, console and KES.PersistentVolumeClaim
object.Breaking change
Note that this may be a breaking change for some deployments that depend on propagating annotations/labels from the tenant to downstream resources.