-
Notifications
You must be signed in to change notification settings - Fork 2
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
chore(deps): update cloudnative-pg docker tag to v0.22.0 #504
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Infro diff for d0574fdembla > cloudnative-postgres (4 files changed) time="2024-08-22T16:36:51Z" level=warning msg="Failed to invoke grpc call. Use flag --grpc-web in grpc calls. To avoid this warning message, use flag --grpc-web."
time="2024-08-22T16:36:52Z" level=warning msg="Failed to invoke grpc call. Use flag --grpc-web in grpc calls. To avoid this warning message, use flag --grpc-web."
===== /ConfigMap cloudnative-postgres/cnpg-controller-manager-config ======
--- /tmp/argocd-diff2596086963/cnpg-controller-manager-config-live.yaml
+++ /tmp/argocd-diff2596086963/cnpg-controller-manager-config
@@ -7,8 +7,8 @@
app.kubernetes.io/instance: cloudnative-postgres
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: cloudnative-pg
- app.kubernetes.io/version: 1.23.3
- helm.sh/chart: cloudnative-pg-0.21.6
+ app.kubernetes.io/version: 1.24.0
+ helm.sh/chart: cloudnative-pg-0.22.0
managedFields:
- apiVersion: v1
fieldsType: FieldsV1
===== /ConfigMap cloudnative-postgres/cnpg-default-monitoring ======
--- /tmp/argocd-diff1284972180/cnpg-default-monitoring-live.yaml
+++ /tmp/argocd-diff1284972180/cnpg-default-monitoring
@@ -456,9 +456,9 @@
app.kubernetes.io/instance: cloudnative-postgres
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: cloudnative-pg
- app.kubernetes.io/version: 1.23.3
+ app.kubernetes.io/version: 1.24.0
cnpg.io/reload: ""
- helm.sh/chart: cloudnative-pg-0.21.6
+ helm.sh/chart: cloudnative-pg-0.22.0
managedFields:
- apiVersion: v1
fieldsType: FieldsV1
===== /Service cloudnative-postgres/cnpg-webhook-service ======
--- /tmp/argocd-diff3499429413/cnpg-webhook-service-live.yaml
+++ /tmp/argocd-diff3499429413/cnpg-webhook-service
@@ -7,8 +7,8 @@
app.kubernetes.io/instance: cloudnative-postgres
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: cloudnative-pg
- app.kubernetes.io/version: 1.23.3
- helm.sh/chart: cloudnative-pg-0.21.6
+ app.kubernetes.io/version: 1.24.0
+ helm.sh/chart: cloudnative-pg-0.22.0
managedFields:
- apiVersion: v1
fieldsType: FieldsV1
===== /ServiceAccount cloudnative-postgres/cloudnative-postgres-cloudnative-pg ======
--- /tmp/argocd-diff3905410163/cloudnative-postgres-cloudnative-pg-live.yaml
+++ /tmp/argocd-diff3905410163/cloudnative-postgres-cloudnative-pg
@@ -7,8 +7,8 @@
app.kubernetes.io/instance: cloudnative-postgres
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: cloudnative-pg
- app.kubernetes.io/version: 1.23.3
- helm.sh/chart: cloudnative-pg-0.21.6
+ app.kubernetes.io/version: 1.24.0
+ helm.sh/chart: cloudnative-pg-0.22.0
managedFields:
- apiVersion: v1
fieldsType: FieldsV1
===== admissionregistration.k8s.io/MutatingWebhookConfiguration /cnpg-mutating-webhook-configuration ======
--- /tmp/argocd-diff2045503358/cnpg-mutating-webhook-configuration-live.yaml
+++ /tmp/argocd-diff2045503358/cnpg-mutating-webhook-configuration
@@ -8,8 +8,8 @@
app.kubernetes.io/instance: cloudnative-postgres
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: cloudnative-pg
- app.kubernetes.io/version: 1.23.3
- helm.sh/chart: cloudnative-pg-0.21.6
+ app.kubernetes.io/version: 1.24.0
+ helm.sh/chart: cloudnative-pg-0.22.0
managedFields:
- apiVersion: admissionregistration.k8s.io/v1
fieldsType: FieldsV1
===== admissionregistration.k8s.io/ValidatingWebhookConfiguration /cnpg-validating-webhook-configuration ======
--- /tmp/argocd-diff3403573733/cnpg-validating-webhook-configuration-live.yaml
+++ /tmp/argocd-diff3403573733/cnpg-validating-webhook-configuration
@@ -8,8 +8,8 @@
app.kubernetes.io/instance: cloudnative-postgres
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: cloudnative-pg
- app.kubernetes.io/version: 1.23.3
- helm.sh/chart: cloudnative-pg-0.21.6
+ app.kubernetes.io/version: 1.24.0
+ helm.sh/chart: cloudnative-pg-0.22.0
managedFields:
- apiVersion: admissionregistration.k8s.io/v1
fieldsType: FieldsV1
===== apiextensions.k8s.io/CustomResourceDefinition /clusters.postgresql.cnpg.io ======
--- /tmp/argocd-diff3390056993/clusters.postgresql.cnpg.io-live.yaml
+++ /tmp/argocd-diff3390056993/clusters.postgresql.cnpg.io
@@ -1377,6 +1377,26 @@
When not defined, WAL files will be stored uncompressed and may be
unencrypted in the object store, according to the bucket default policy.
properties:
+ archiveAdditionalCommandArgs:
+ description: |-
+ Additional arguments that can be appended to the 'barman-cloud-wal-archive'
+ command-line invocation. These arguments provide flexibility to customize
+ the WAL archive process further, according to specific requirements or configurations.
+
+
+ Example:
+ In a scenario where specialized backup options are required, such as setting
+ a specific timeout or defining custom behavior, users can use this field
+ to specify additional command arguments.
+
+
+ Note:
+ It's essential to ensure that the provided arguments are valid and supported
+ by the 'barman-cloud-wal-archive' command, to avoid potential errors or unintended
+ behavior during execution.
+ items:
+ type: string
+ type: array
compression:
description: |-
Compress a WAL file before sending it to the object store. Available
@@ -1406,6 +1426,26 @@
value - with 1 being the minimum accepted value.
minimum: 1
type: integer
+ restoreAdditionalCommandArgs:
+ description: |-
+ Additional arguments that can be appended to the 'barman-cloud-wal-restore'
+ command-line invocation. These arguments provide flexibility to customize
+ the WAL restore process further, according to specific requirements or configurations.
+
+
+ Example:
+ In a scenario where specialized backup options are required, such as setting
+ a specific timeout or defining custom behavior, users can use this field
+ to specify additional command arguments.
+
+
+ Note:
+ It's essential to ensure that the provided arguments are valid and supported
+ by the 'barman-cloud-wal-restore' command, to avoid potential errors or unintended
+ behavior during execution.
+ items:
+ type: string
+ type: array
type: object
required:
- destinationPath
@@ -1602,17 +1642,19 @@
postInitApplicationSQL:
description: |-
List of SQL queries to be executed as a superuser in the application
- database right after is created - to be used with extreme care
+ database right after the cluster has been created - to be used with extreme care
(by default empty)
items:
type: string
type: array
postInitApplicationSQLRefs:
description: |-
- PostInitApplicationSQLRefs points references to ConfigMaps or Secrets which
- contain SQL files, the general implementation order to these references is
- from all Secrets to all ConfigMaps, and inside Secrets or ConfigMaps,
- the implementation order is same as the order of each array
+ List of references to ConfigMaps or Secrets containing SQL files
+ to be executed as a superuser in the application database right after
+ the cluster has been created. The references are processed in a specific order:
+ first, all Secrets are processed, followed by all ConfigMaps.
+ Within each group, the processing order follows the sequence specified
+ in their respective arrays.
(by default empty)
properties:
configMapRefs:
@@ -1656,20 +1698,118 @@
type: object
postInitSQL:
description: |-
- List of SQL queries to be executed as a superuser immediately
- after the cluster has been created - to be used with extreme care
+ List of SQL queries to be executed as a superuser in the `postgres`
+ database right after the cluster has been created - to be used with extreme care
(by default empty)
items:
type: string
type: array
+ postInitSQLRefs:
+ description: |-
+ List of references to ConfigMaps or Secrets containing SQL files
+ to be executed as a superuser in the `postgres` database right after
+ the cluster has been created. The references are processed in a specific order:
+ first, all Secrets are processed, followed by all ConfigMaps.
+ Within each group, the processing order follows the sequence specified
+ in their respective arrays.
+ (by default empty)
+ properties:
+ configMapRefs:
+ description: ConfigMapRefs holds a list of references
+ to ConfigMaps
+ items:
+ description: |-
+ ConfigMapKeySelector contains enough information to let you locate
+ the key of a ConfigMap
+ properties:
+ key:
+ description: The key to select
+ type: string
+ name:
+ description: Name of the referent.
+ type: string
+ required:
+ - key
+ - name
+ type: object
+ type: array
+ secretRefs:
+ description: SecretRefs holds a list of references to
+ Secrets
+ items:
+ description: |-
+ SecretKeySelector contains enough information to let you locate
+ the key of a Secret
+ properties:
+ key:
+ description: The key to select
+ type: string
+ name:
+ description: Name of the referent.
+ type: string
+ required:
+ - key
+ - name
+ type: object
+ type: array
+ type: object
postInitTemplateSQL:
description: |-
List of SQL queries to be executed as a superuser in the `template1`
- after the cluster has been created - to be used with extreme care
+ database right after the cluster has been created - to be used with extreme care
(by default empty)
items:
type: string
type: array
+ postInitTemplateSQLRefs:
+ description: |-
+ List of references to ConfigMaps or Secrets containing SQL files
+ to be executed as a superuser in the `template1` database right after
+ the cluster has been created. The references are processed in a specific order:
+ first, all Secrets are processed, followed by all ConfigMaps.
+ Within each group, the processing order follows the sequence specified
+ in their respective arrays.
+ (by default empty)
+ properties:
+ configMapRefs:
+ description: ConfigMapRefs holds a list of references
+ to ConfigMaps
+ items:
+ description: |-
+ ConfigMapKeySelector contains enough information to let you locate
+ the key of a ConfigMap
+ properties:
+ key:
+ description: The key to select
+ type: string
+ name:
+ description: Name of the referent.
+ type: string
+ required:
+ - key
+ - name
+ type: object
+ type: array
+ secretRefs:
+ description: SecretRefs holds a list of references to
+ Secrets
+ items:
+ description: |-
+ SecretKeySelector contains enough information to let you locate
+ the key of a Secret
+ properties:
+ key:
+ description: The key to select
+ type: string
+ name:
+ description: Name of the referent.
+ type: string
+ required:
+ - key
+ - name
+ type: object
+ type: array
+ type: object
secret:
description: |-
Name of the secret containing the initial credentials for the
@@ -2701,6 +2841,26 @@
When not defined, WAL files will be stored uncompressed and may be
unencrypted in the object store, according to the bucket default policy.
properties:
+ archiveAdditionalCommandArgs:
+ description: |-
+ Additional arguments that can be appended to the 'barman-cloud-wal-archive'
+ command-line invocation. These arguments provide flexibility to customize
+ the WAL archive process further, according to specific requirements or configurations.
+
+
+ Example:
+ In a scenario where specialized backup options are required, such as setting
+ a specific timeout or defining custom behavior, users can use this field
+ to specify additional command arguments.
+
+
+ Note:
+ It's essential to ensure that the provided arguments are valid and supported
+ by the 'barman-cloud-wal-archive' command, to avoid potential errors or unintended
+ behavior during execution.
+ items:
+ type: string
+ type: array
compression:
description: |-
Compress a WAL file before sending it to the object store. Available
@@ -2730,6 +2890,26 @@
value - with 1 being the minimum accepted value.
minimum: 1
type: integer
+ restoreAdditionalCommandArgs:
+ description: |-
+ Additional arguments that can be appended to the 'barman-cloud-wal-restore'
+ command-line invocation. These arguments provide flexibility to customize
+ the WAL restore process further, according to specific requirements or configurations.
+
+
+ Example:
+ In a scenario where specialized backup options are required, such as setting
+ a specific timeout or defining custom behavior, users can use this field
+ to specify additional command arguments.
+
+
+ Note:
+ It's essential to ensure that the provided arguments are valid and supported
+ by the 'barman-cloud-wal-restore' command, to avoid potential errors or unintended
+ behavior during execution.
+ items:
+ type: string
+ type: array
type: object
required:
- destinationPath
@@ -3087,6 +3267,443 @@
- name
type: object
type: array
+ services:
+ description: Services roles managed by the `Cluster`
+ properties:
+ additional:
+ description: Additional is a list of additional managed services
+ specified by the user.
+ items:
+ description: |-
+ ManagedService represents a specific service managed by the cluster.
+ It includes the type of service and its associated template specification.
+ properties:
+ selectorType:
+ allOf:
+ - enum:
+ - rw
+ - r
+ - ro
+ - enum:
+ - rw
+ - r
+ - ro
+ description: |-
+ SelectorType specifies the type of selectors that the service will have.
+ Valid values are "rw", "r", and "ro", representing read-write, read, and read-only services.
+ type: string
+ serviceTemplate:
+ description: ServiceTemplate is the template specification
+ for the service.
+ properties:
+ metadata:
+ description: |-
+ Standard object's metadata.
+ More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
+ properties:
+ annotations:
+ additionalProperties:
+ type: string
+ description: |-
+ Annotations is an unstructured key value map stored with a resource that may be
+ set by external tools to store and retrieve arbitrary metadata. They are not
+ queryable and should be preserved when modifying objects.
+ More info: http://kubernetes.io/docs/user-guide/annotations
+ type: object
+ labels:
+ additionalProperties:
+ type: string
+ description: |-
+ Map of string keys and values that can be used to organize and categorize
+ (scope and select) objects. May match selectors of replication controllers
+ and services.
+ More info: http://kubernetes.io/docs/user-guide/labels
+ type: object
+ name:
+ description: The name of the resource. Only
+ supported for certain types
+ type: string
+ type: object
+ spec:
+ description: |-
+ Specification of the desired behavior of the service.
+ More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
+ properties:
+ allocateLoadBalancerNodePorts:
+ description: |-
+ allocateLoadBalancerNodePorts defines if NodePorts will be automatically
+ allocated for services with type LoadBalancer. Default is "true". It
+ may be set to "false" if the cluster load-balancer does not rely on
+ NodePorts. If the caller requests specific NodePorts (by specifying a
+ value), those requests will be respected, regardless of this field.
+ This field may only be set for services with type LoadBalancer and will
+ be cleared if the type is changed to any other type.
+ type: boolean
+ clusterIP:
+ description: |-
+ clusterIP is the IP address of the service and is usually assigned
+ randomly. If an address is specified manually, is in-range (as per
+ system configuration), and is not in use, it will be allocated to the
+ service; otherwise creation of the service will fail. This field may not
+ be changed through updates unless the type field is also being changed
+ to ExternalName (which requires this field to be blank) or the type
+ field is being changed from ExternalName (in which case this field may
+ optionally be specified, as describe above). Valid values are "None",
+ empty string (""), or a valid IP address. Setting this to "None" makes a
+ "headless service" (no virtual IP), which is useful when direct endpoint
+ connections are preferred and proxying is not required. Only applies to
+ types ClusterIP, NodePort, and LoadBalancer. If this field is specified
+ when creating a Service of type ExternalName, creation will fail. This
+ field will be wiped when updating a Service to type ExternalName.
+ More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies
+ type: string
+ clusterIPs:
+ description: |-
+ ClusterIPs is a list of IP addresses assigned to this service, and are
+ usually assigned randomly. If an address is specified manually, is
+ in-range (as per system configuration), and is not in use, it will be
+ allocated to the service; otherwise creation of the service will fail.
+ This field may not be changed through updates unless the type field is
+ also being changed to ExternalName (which requires this field to be
+ empty) or the type field is being changed from ExternalName (in which
+ case this field may optionally be specified, as describe above). Valid
+ values are "None", empty string (""), or a valid IP address. Setting
+ this to "None" makes a "headless service" (no virtual IP), which is
+ useful when direct endpoint connections are preferred and proxying is
+ not required. Only applies to types ClusterIP, NodePort, and
+ LoadBalancer. If this field is specified when creating a Service of type
+ ExternalName, creation will fail. This field will be wiped when updating
+ a Service to type ExternalName. If this field is not specified, it will
+ be initialized from the clusterIP field. If this field is specified,
+ clients must ensure that clusterIPs[0] and clusterIP have the same
+ value.
+
+
+ This field may hold a maximum of two entries (dual-stack IPs, in either order).
+ These IPs must correspond to the values of the ipFamilies field. Both
+ clusterIPs and ipFamilies are governed by the ipFamilyPolicy field.
+ More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies
+ items:
+ type: string
+ type: array
+ x-kubernetes-list-type: atomic
+ externalIPs:
+ description: |-
+ externalIPs is a list of IP addresses for which nodes in the cluster
+ will also accept traffic for this service. These IPs are not managed by
+ Kubernetes. The user is responsible for ensuring that traffic arrives
+ at a node with this IP. A common example is external load-balancers
+ that are not part of the Kubernetes system.
+ items:
+ type: string
+ type: array
+ x-kubernetes-list-type: atomic
+ externalName:
+ description: |-
+ externalName is the external reference that discovery mechanisms will
+ return as an alias for this service (e.g. a DNS CNAME record). No
+ proxying will be involved. Must be a lowercase RFC-1123 hostname
+ (https://tools.ietf.org/html/rfc1123) and requires `type` to be "ExternalName".
+ type: string
+ externalTrafficPolicy:
+ description: |-
+ externalTrafficPolicy describes how nodes distribute service traffic they
+ receive on one of the Service's "externally-facing" addresses (NodePorts,
+ ExternalIPs, and LoadBalancer IPs). If set to "Local", the proxy will configure
+ the service in a way that assumes that external load balancers will take care
+ of balancing the service traffic between nodes, and so each node will deliver
+ traffic only to the node-local endpoints of the service, without masquerading
+ the client source IP. (Traffic mistakenly sent to a node with no endpoints will
+ be dropped.) The default value, "Cluster", uses the standard behavior of
+ routing to all endpoints evenly (possibly modified by topology and other
+ features). Note that traffic sent to an External IP or LoadBalancer IP from
+ within the cluster will always get "Cluster" semantics, but clients sending to
+ a NodePort from within the cluster may need to take traffic policy into account
+ when picking a node.
+ type: string
+ healthCheckNodePort:
+ description: |-
+ healthCheckNodePort specifies the healthcheck nodePort for the service.
+ This only applies when type is set to LoadBalancer and
+ externalTrafficPolicy is set to Local. If a value is specified, is
+ in-range, and is not in use, it will be used. If not specified, a value
+ will be automatically allocated. External systems (e.g. load-balancers)
+ can use this port to determine if a given node holds endpoints for this
+ service or not. If this field is specified when creating a Service
+ which does not need it, creation will fail. This field will be wiped
+ when updating a Service to no longer need it (e.g. changing type).
+ This field cannot be updated once set.
+ format: int32
+ type: integer
+ internalTrafficPolicy:
+ description: |-
+ InternalTrafficPolicy describes how nodes distribute service traffic they
+ receive on the ClusterIP. If set to "Local", the proxy will assume that pods
+ only want to talk to endpoints of the service on the same node as the pod,
+ dropping the traffic if there are no local endpoints. The default value,
+ "Cluster", uses the standard behavior of routing to all endpoints evenly
+ (possibly modified by topology and other features).
+ type: string
+ ipFamilies:
+ description: |-
+ IPFamilies is a list of IP families (e.g. IPv4, IPv6) assigned to this
+ service. This field is usually assigned automatically based on cluster
+ configuration and the ipFamilyPolicy field. If this field is specified
+ manually, the requested family is available in the cluster,
+ and ipFamilyPolicy allows it, it will be used; otherwise creation of
+ the service will fail. This field is conditionally mutable: it allows
+ for adding or removing a secondary IP family, but it does not allow
+ changing the primary IP family of the Service. Valid values are "IPv4"
+ and "IPv6". This field only applies to Services of types ClusterIP,
+ NodePort, and LoadBalancer, and does apply to "headless" services.
+ This field will be wiped when updating a Service to type ExternalName.
+
+
+ This field may hold a maximum of two entries (dual-stack families, in
+ either order). These families must correspond to the values of the
+ clusterIPs field, if specified. Both clusterIPs and ipFamilies are
+ governed by the ipFamilyPolicy field.
+ items:
+ description: |-
+ IPFamily represents the IP Family (IPv4 or IPv6). This type is used
+ to express the family of an IP expressed by a type (e.g. service.spec.ipFamilies).
+ type: string
+ type: array
+ x-kubernetes-list-type: atomic
+ ipFamilyPolicy:
+ description: |-
+ IPFamilyPolicy represents the dual-stack-ness requested or required by
+ this Service. If there is no value provided, then this field will be set
+ to SingleStack. Services can be "SingleStack" (a single IP family),
+ "PreferDualStack" (two IP families on dual-stack configured clusters or
+ a single IP family on single-stack clusters), or "RequireDualStack"
+ (two IP families on dual-stack configured clusters, otherwise fail). The
+ ipFamilies and clusterIPs fields depend on the value of this field. This
+ field will be wiped when updating a service to type ExternalName.
+ type: string
+ loadBalancerClass:
+ description: |-
+ loadBalancerClass is the class of the load balancer implementation this Service belongs to.
+ If specified, the value of this field must be a label-style identifier, with an optional prefix,
+ e.g. "internal-vip" or "example.com/internal-vip". Unprefixed names are reserved for end-users.
+ This field can only be set when the Service type is 'LoadBalancer'. If not set, the default load
+ balancer implementation is used, today this is typically done through the cloud provider integration,
+ but should apply for any default implementation. If set, it is assumed that a load balancer
+ implementation is watching for Services with a matching class. Any default load balancer
+ implementation (e.g. cloud providers) should ignore Services that set this field.
+ This field can only be set when creating or updating a Service to type 'LoadBalancer'.
+ Once set, it can not be changed. This field will be wiped when a service is updated to a non 'LoadBalancer' type.
+ type: string
+ loadBalancerIP:
+ description: |-
+ Only applies to Service Type: LoadBalancer.
+ This feature depends on whether the underlying cloud-provider supports specifying
+ the loadBalancerIP when a load balancer is created.
+ This field will be ignored if the cloud-provider does not support the feature.
+ Deprecated: This field was under-specified and its meaning varies across implementations.
+ Using it is non-portable and it may not support dual-stack.
+ Users are encouraged to use implementation-specific annotations when available.
+ type: string
+ loadBalancerSourceRanges:
+ description: |-
+ If specified and supported by the platform, this will restrict traffic through the cloud-provider
+ load-balancer will be restricted to the specified client IPs. This field will be ignored if the
+ cloud-provider does not support the feature."
+ More info: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/
+ items:
+ type: string
+ type: array
+ x-kubernetes-list-type: atomic
+ ports:
+ description: |-
+ The list of ports that are exposed by this service.
+ More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies
+ items:
+ description: ServicePort contains information
+ on service's port.
+ properties:
+ appProtocol:
+ description: |-
+ The application protocol for this port.
+ This is used as a hint for implementations to offer richer behavior for protocols that they understand.
+ This field follows standard Kubernetes label syntax.
+ Valid values are either:
+
+
+ * Un-prefixed protocol names - reserved for IANA standard service names (as per
+ RFC-6335 and https://www.iana.org/assignments/service-names).
+
+
+ * Kubernetes-defined prefixed names:
+ * 'kubernetes.io/h2c' - HTTP/2 prior knowledge over cleartext as described in https://www.rfc-editor.org/rfc/rfc9113.html#name-starting-http-2-with-prior-
+ * 'kubernetes.io/ws' - WebSocket over cleartext as described in https://www.rfc-editor.org/rfc/rfc6455
+ * 'kubernetes.io/wss' - WebSocket over TLS as described in https://www.rfc-editor.org/rfc/rfc6455
+
+
+ * Other protocols should use implementation-defined prefixed names such as
+ mycompany.com/my-custom-protocol.
+ type: string
+ name:
+ description: |-
+ The name of this port within the service. This must be a DNS_LABEL.
+ All ports within a ServiceSpec must have unique names. When considering
+ the endpoints for a Service, this must match the 'name' field in the
+ EndpointPort.
+ Optional if only one ServicePort is defined on this service.
+ type: string
+ nodePort:
+ description: |-
+ The port on each node on which this service is exposed when type is
+ NodePort or LoadBalancer. Usually assigned by the system. If a value is
+ specified, in-range, and not in use it will be used, otherwise the
+ operation will fail. If not specified, a port will be allocated if this
+ Service requires one. If this field is specified when creating a
+ Service which does not need it, creation will fail. This field will be
+ wiped when updating a Service to no longer need it (e.g. changing type
+ from NodePort to ClusterIP).
+ More info: https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport
+ format: int32
+ type: integer
+ port:
+ description: The port that will be exposed
+ by this service.
+ format: int32
+ type: integer
+ protocol:
+ default: TCP
+ description: |-
+ The IP protocol for this port. Supports "TCP", "UDP", and "SCTP".
+ Default is TCP.
+ type: string
+ targetPort:
+ anyOf:
+ - type: integer
+ - type: string
+ description: |-
+ Number or name of the port to access on the pods targeted by the service.
+ Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME.
+ If this is a string, it will be looked up as a named port in the
+ target Pod's container ports. If this is not specified, the value
+ of the 'port' field is used (an identity map).
+ This field is ignored for services with clusterIP=None, and should be
+ omitted or set equal to the 'port' field.
+ More info: https://kubernetes.io/docs/concepts/services-networking/service/#defining-a-service
+ x-kubernetes-int-or-string: true
+ required:
+ - port
+ type: object
+ type: array
+ x-kubernetes-list-map-keys:
+ - port
+ - protocol
+ x-kubernetes-list-type: map
+ publishNotReadyAddresses:
+ description: |-
+ publishNotReadyAddresses indicates that any agent which deals with endpoints for this
+ Service should disregard any indications of ready/not-ready.
+ The primary use case for setting this field is for a StatefulSet's Headless Service to
+ propagate SRV DNS records for its Pods for the purpose of peer discovery.
+ The Kubernetes controllers that generate Endpoints and EndpointSlice resources for
+ Services interpret this to mean that all endpoints are considered "ready" even if the
+ Pods themselves are not. Agents which consume only Kubernetes generated endpoints
+ through the Endpoints or EndpointSlice resources can safely assume this behavior.
+ type: boolean
+ selector:
+ additionalProperties:
+ type: string
+ description: |-
+ Route service traffic to pods with label keys and values matching this
+ selector. If empty or not present, the service is assumed to have an
+ external process managing its endpoints, which Kubernetes will not
+ modify. Only applies to types ClusterIP, NodePort, and LoadBalancer.
+ Ignored if type is ExternalName.
+ More info: https://kubernetes.io/docs/concepts/services-networking/service/
+ type: object
+ x-kubernetes-map-type: atomic
+ sessionAffinity:
+ description: |-
+ Supports "ClientIP" and "None". Used to maintain session affinity.
+ Enable client IP based session affinity.
+ Must be ClientIP or None.
+ Defaults to None.
+ More info: https://kubernetes.io/docs/concepts/services-networking/service/#virtual-ips-and-service-proxies
+ type: string
+ sessionAffinityConfig:
+ description: sessionAffinityConfig contains
+ the configurations of session affinity.
+ properties:
+ clientIP:
+ description: clientIP contains the configurations
+ of Client IP based session affinity.
+ properties:
+ timeoutSeconds:
+ description: |-
+ timeoutSeconds specifies the seconds of ClientIP type session sticky time.
+ The value must be >0 && <=86400(for 1 day) if ServiceAffinity == "ClientIP".
+ Default value is 10800(for 3 hours).
+ format: int32
+ type: integer
+ type: object
+ type: object
+ trafficDistribution:
+ description: |-
+ TrafficDistribution offers a way to express preferences for how traffic is
+ distributed to Service endpoints. Implementations can use this field as a
+ hint, but are not required to guarantee strict adherence. If the field is
+ not set, the implementation will apply its default routing strategy. If set
+ to "PreferClose", implementations should prioritize endpoints that are
+ topologically close (e.g., same zone).
+ This is an alpha field and requires enabling ServiceTrafficDistribution feature.
+ type: string
+ type:
+ description: |-
+ type determines how the Service is exposed. Defaults to ClusterIP. Valid
+ options are ExternalName, ClusterIP, NodePort, and LoadBalancer.
+ "ClusterIP" allocates a cluster-internal IP address for load-balancing
+ to endpoints. Endpoints are determined by the selector or if that is not
+ specified, by manual construction of an Endpoints object or
+ EndpointSlice objects. If clusterIP is "None", no virtual IP is
+ allocated and the endpoints are published as a set of endpoints rather
+ than a virtual IP.
+ "NodePort" builds on ClusterIP and allocates a port on every node which
+ routes to the same endpoints as the clusterIP.
+ "LoadBalancer" builds on NodePort and creates an external load-balancer
+ (if supported in the current cloud) which routes to the same endpoints
+ as the clusterIP.
+ "ExternalName" aliases this service to the specified externalName.
+ Several other fields do not apply to ExternalName services.
+ More info: https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types
+ type: string
+ type: object
+ type: object
+ updateStrategy:
+ default: patch
+ description: UpdateStrategy describes how the service
+ differences should be reconciled
+ enum:
+ - patch
+ - replace
+ type: string
+ required:
+ - selectorType
+ - serviceTemplate
+ type: object
+ type: array
+ disabledDefaultServices:
+ description: |-
+ DisabledDefaultServices is a list of service types that are disabled by default.
+ Valid values are "r", and "ro", representing read, and read-only services.
+ items:
+ description: |-
+ ServiceSelectorType describes a valid value for generating the service selectors.
+ It indicates which type of service the selector applies to, such as read-write, read, or read-only
+ enum:
+ - rw
+ - r
+ - ro
+ type: string
+ type: array
+ type: object
type: object
maxSyncReplicas:
default: 0
@@ -3345,6 +3962,18 @@
type: string
type: object
type: array
+ tls:
+ description: |-
+ Configure TLS communication for the metrics endpoint.
+ Changing tls.enabled option will force a rollout of all instances.
+ properties:
+ enabled:
+ default: false
+ description: |-
+ Enable TLS for the monitoring endpoint.
+ Changing this option will force a rollout of all instances.
+ type: boolean
+ type: object
type: object
nodeMaintenanceWindow:
description: Define a maintenance window for the Kubernetes nodes
@@ -3527,6 +4156,54 @@
required:
- enabled
type: object
+ synchronous:
+ description: Configuration of the PostgreSQL synchronous replication
+ feature
+ properties:
+ maxStandbyNamesFromCluster:
+ description: |-
+ Specifies the maximum number of local cluster pods that can be
+ automatically included in the `synchronous_standby_names` option in
+ PostgreSQL.
+ type: integer
+ method:
+ description: |-
+ Method to select synchronous replication standbys from the listed
+ servers, accepting 'any' (quorum-based synchronous replication) or
+ 'first' (priority-based synchronous replication) as values.
+ enum:
+ - any
+ - first
+ type: string
+ number:
+ description: |-
+ Specifies the number of synchronous standby servers that
+ transactions must wait for responses from.
+ type: integer
+ x-kubernetes-validations:
+ - message: The number of synchronous replicas should be greater
+ than zero
+ rule: self > 0
+ standbyNamesPost:
+ description: |-
+ A user-defined list of application names to be added to
+ `synchronous_standby_names` after local cluster pods (the order is
+ only useful for priority-based synchronous replication).
+ items:
+ type: string
+ type: array
+ standbyNamesPre:
+ description: |-
+ A user-defined list of application names to be added to
+ `synchronous_standby_names` before local cluster pods (the order is
+ only useful for priority-based synchronous replication).
+ items:
+ type: string
+ type: array
+ required:
+ - method
+ - number
+ type: object
type: object
primaryUpdateMethod:
default: restart
@@ -3908,13 +4585,35 @@
object store or via streaming through pg_basebackup.
Refer to the Replica clusters page of the documentation for more information.
type: boolean
+ minApplyDelay:
+ description: |-
+ When replica mode is enabled, this parameter allows you to replay
+ transactions only when the system time is at least the configured
+ time past the commit time. This provides an opportunity to correct
+ data loss errors. Note that when this parameter is set, a promotion
+ token cannot be used.
+ type: string
+ primary:
+ description: |-
+ Primary defines which Cluster is defined to be the primary in the distributed PostgreSQL cluster, based on the
+ topology specified in externalClusters
+ type: string
+ promotionToken:
+ description: |-
+ A demotion token generated by an external cluster used to
+ check if the promotion requirements are met.
+ type: string
+ self:
+ description: |-
+ Self defines the name of this cluster. It is used to determine if this is a primary
+ or a replica cluster, comparing it with `primary`
+ type: string
source:
description: The name of the external cluster which is the replication
origin
minLength: 1
type: string
required:
- - enabled
- source
type: object
replicationSlots:
@@ -4091,6 +4790,10 @@
and services.
More info: http://kubernetes.io/docs/user-guide/labels
type: object
+ name:
+ description: The name of the resource. Only supported for
+ certain types
+ type: string
type: object
required:
- metadata
@@ -5210,6 +5913,13 @@
items:
type: string
type: array
+ demotionToken:
+ description: |-
+ DemotionToken is a JSON token containing the information
+ from pg_controldata such as Database system identifier, Latest checkpoint's
+ TimeLineID, Latest checkpoint's REDO location, Latest checkpoint's REDO
+ WAL file, and Time of latest checkpoint
+ type: string
firstRecoverabilityPoint:
description: |-
The first recoverability point, stored as a date in RFC3339 format.
@@ -5277,6 +5987,11 @@
lastFailedBackup:
description: Stored as a date in RFC3339 format
type: string
+ lastPromotionToken:
+ description: |-
+ LastPromotionToken is the last verified promotion token that
+ was used to promote a replica cluster
+ type: string
lastSuccessfulBackup:
description: |-
Last successful backup, stored as a date in RFC3339 format
@@ -5370,6 +6085,10 @@
items:
type: string
type: array
+ status:
+ description: Status contain the status reported by the plugin
+ through the SetStatusInCluster interface
+ type: string
version:
description: |-
Version is the version of the plugin loaded by the
===== apiextensions.k8s.io/CustomResourceDefinition /poolers.postgresql.cnpg.io ======
--- /tmp/argocd-diff2199245583/poolers.postgresql.cnpg.io-live.yaml
+++ /tmp/argocd-diff2199245583/poolers.postgresql.cnpg.io
@@ -449,6 +449,10 @@
and services.
More info: http://kubernetes.io/docs/user-guide/labels
type: object
+ name:
+ description: The name of the resource. Only supported for
+ certain types
+ type: string
type: object
spec:
description: |-
@@ -827,6 +831,10 @@
and services.
More info: http://kubernetes.io/docs/user-guide/labels
type: object
+ name:
+ description: The name of the resource. Only supported for
+ certain types
+ type: string
type: object
spec:
description: |-
===== apps/Deployment cloudnative-postgres/cloudnative-postgres-cloudnative-pg ======
--- /tmp/argocd-diff1269999156/cloudnative-postgres-cloudnative-pg-live.yaml
+++ /tmp/argocd-diff1269999156/cloudnative-postgres-cloudnative-pg
@@ -9,8 +9,8 @@
app.kubernetes.io/instance: cloudnative-postgres
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: cloudnative-pg
- app.kubernetes.io/version: 1.23.3
- helm.sh/chart: cloudnative-pg-0.21.6
+ app.kubernetes.io/version: 1.24.0
+ helm.sh/chart: cloudnative-pg-0.22.0
managedFields:
- apiVersion: apps/v1
fieldsType: FieldsV1
@@ -195,7 +195,7 @@
template:
metadata:
annotations:
- checksum/config: cb8fa89607abeae54f18f8b9d2beecc621afc6d70b0796e002f26b0bd6a36be9
+ checksum/config: 75a69d1cff936a37106d9fd104fdbb8d08dfa04d884159a24852146df16b72d6
kubectl.kubernetes.io/restartedAt: "2024-06-10T17:47:22Z"
creationTimestamp: null
labels:
@@ -212,7 +212,7 @@
- /manager
env:
- name: OPERATOR_IMAGE_NAME
- value: ghcr.io/cloudnative-pg/cloudnative-pg:1.23.3
+ value: ghcr.io/cloudnative-pg/cloudnative-pg:1.24.0
- name: OPERATOR_NAMESPACE
valueFrom:
fieldRef:
@@ -220,7 +220,7 @@
fieldPath: metadata.namespace
- name: MONITORING_QUERIES_CONFIGMAP
value: cnpg-default-monitoring
- image: ghcr.io/cloudnative-pg/cloudnative-pg:1.23.3
+ image: ghcr.io/cloudnative-pg/cloudnative-pg:1.24.0
imagePullPolicy: IfNotPresent
livenessProbe:
failureThreshold: 3
===== monitoring.coreos.com/PodMonitor cloudnative-postgres/cloudnative-postgres-cloudnative-pg ======
--- /tmp/argocd-diff807491954/cloudnative-postgres-cloudnative-pg-live.yaml
+++ /tmp/argocd-diff807491954/cloudnative-postgres-cloudnative-pg
@@ -8,8 +8,8 @@
app.kubernetes.io/instance: cloudnative-postgres
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: cloudnative-pg
- app.kubernetes.io/version: 1.23.3
- helm.sh/chart: cloudnative-pg-0.21.6
+ app.kubernetes.io/version: 1.24.0
+ helm.sh/chart: cloudnative-pg-0.22.0
managedFields:
- apiVersion: monitoring.coreos.com/v1
fieldsType: FieldsV1
===== rbac.authorization.k8s.io/ClusterRole /cloudnative-postgres-cloudnative-pg ======
--- /tmp/argocd-diff1712097520/cloudnative-postgres-cloudnative-pg-live.yaml
+++ /tmp/argocd-diff1712097520/cloudnative-postgres-cloudnative-pg
@@ -7,8 +7,8 @@
app.kubernetes.io/instance: cloudnative-postgres
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: cloudnative-pg
- app.kubernetes.io/version: 1.23.3
- helm.sh/chart: cloudnative-pg-0.21.6
+ app.kubernetes.io/version: 1.24.0
+ helm.sh/chart: cloudnative-pg-0.22.0
managedFields:
- apiVersion: rbac.authorization.k8s.io/v1
fieldsType: FieldsV1
@@ -175,14 +175,6 @@
verbs:
- get
- patch
-- apiGroups:
- - apiextensions.k8s.io
- resources:
- - customresourcedefinitions
- verbs:
- - get
- - list
- - update
- apiGroups:
- apps
resources:
===== rbac.authorization.k8s.io/ClusterRole /cloudnative-postgres-cloudnative-pg-edit ======
--- /tmp/argocd-diff2094033862/cloudnative-postgres-cloudnative-pg-edit-live.yaml
+++ /tmp/argocd-diff2094033862/cloudnative-postgres-cloudnative-pg-edit
@@ -7,8 +7,8 @@
app.kubernetes.io/instance: cloudnative-postgres
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: cloudnative-pg
- app.kubernetes.io/version: 1.23.3
- helm.sh/chart: cloudnative-pg-0.21.6
+ app.kubernetes.io/version: 1.24.0
+ helm.sh/chart: cloudnative-pg-0.22.0
managedFields:
- apiVersion: rbac.authorization.k8s.io/v1
fieldsType: FieldsV1
===== rbac.authorization.k8s.io/ClusterRole /cloudnative-postgres-cloudnative-pg-view ======
--- /tmp/argocd-diff3206055504/cloudnative-postgres-cloudnative-pg-view-live.yaml
+++ /tmp/argocd-diff3206055504/cloudnative-postgres-cloudnative-pg-view
@@ -7,8 +7,8 @@
app.kubernetes.io/instance: cloudnative-postgres
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: cloudnative-pg
- app.kubernetes.io/version: 1.23.3
- helm.sh/chart: cloudnative-pg-0.21.6
+ app.kubernetes.io/version: 1.24.0
+ helm.sh/chart: cloudnative-pg-0.22.0
managedFields:
- apiVersion: rbac.authorization.k8s.io/v1
fieldsType: FieldsV1
===== rbac.authorization.k8s.io/ClusterRoleBinding /cloudnative-postgres-cloudnative-pg ======
--- /tmp/argocd-diff1887440980/cloudnative-postgres-cloudnative-pg-live.yaml
+++ /tmp/argocd-diff1887440980/cloudnative-postgres-cloudnative-pg
@@ -7,8 +7,8 @@
app.kubernetes.io/instance: cloudnative-postgres
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: cloudnative-pg
- app.kubernetes.io/version: 1.23.3
- helm.sh/chart: cloudnative-pg-0.21.6
+ app.kubernetes.io/version: 1.24.0
+ helm.sh/chart: cloudnative-pg-0.22.0
managedFields:
- apiVersion: rbac.authorization.k8s.io/v1
fieldsType: FieldsV1 embla > home-assistant (0 files changed) time="2024-08-22T16:36:56Z" level=warning msg="Failed to invoke grpc call. Use flag --grpc-web in grpc calls. To avoid this warning message, use flag --grpc-web."
time="2024-08-22T16:36:56Z" level=warning msg="Failed to invoke grpc call. Use flag --grpc-web in grpc calls. To avoid this warning message, use flag --grpc-web."
===== apps/StatefulSet home-assistant/home-assistant ======
--- /tmp/argocd-diff527090759/home-assistant-live.yaml
+++ /tmp/argocd-diff527090759/home-assistant
@@ -255,7 +255,12 @@
resources: {}
securityContext:
allowPrivilegeEscalation: false
- capabilities: {}
+ capabilities:
+ add:
+ - NET_RAW
+ - NET_BIND_SERVICE
+ drop:
+ - ALL
runAsGroup: 5000
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
@@ -282,7 +287,10 @@
restartPolicy: Always
securityContext:
allowPrivilegeEscalation: false
- capabilities: {}
+ capabilities:
+ add: []
+ drop:
+ - ALL
runAsGroup: 5000
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
@@ -296,6 +304,7 @@
serviceAccount: home-assistant
serviceAccountName: home-assistant
terminationGracePeriodSeconds: 30
+ tolerations: []
updateStrategy:
rollingUpdate:
partition: 0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.21.6
->0.22.0
Release Notes
cloudnative-pg/charts (cloudnative-pg)
v0.22.0
CloudNativePG Operator Helm Chart
What's Changed
Full Changelog: cloudnative-pg/charts@cloudnative-pg-v0.21.6...cloudnative-pg-v0.22.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.