forked from rook/rook
majiayu000
ac6ec79865
Allow users to configure custom labels on CephObjectStore RGW services by adding a Labels field to the RGWServiceSpec, following the existing pattern used for Annotations. This enables use cases such as service mesh integration and monitoring discovery that require specific labels on Kubernetes services. Fixes: #17235 Signed-off-by: majiayu000 <1835304752@qq.com>
178 lines
7.1 KiB
YAML
178 lines
7.1 KiB
YAML
#################################################################################################################
|
|
# Create an object store with settings for replication in a production environment. A minimum of 3 hosts with
|
|
# OSDs are required in this example.
|
|
# kubectl create -f object.yaml
|
|
#################################################################################################################
|
|
|
|
apiVersion: ceph.rook.io/v1
|
|
kind: CephObjectStore
|
|
metadata:
|
|
name: my-store
|
|
namespace: rook-ceph # namespace:cluster
|
|
spec:
|
|
# The pool spec used to create the metadata pools. Must use replication.
|
|
metadataPool:
|
|
failureDomain: host
|
|
replicated:
|
|
size: 3
|
|
# Disallow setting pool with replica 1, this could lead to data loss without recovery.
|
|
# Make sure you're *ABSOLUTELY CERTAIN* that is what you want
|
|
requireSafeReplicaSize: true
|
|
parameters:
|
|
# Inline compression mode for the data pool
|
|
# Further reference: https://docs.ceph.com/docs/master/rados/configuration/bluestore-config-ref/#inline-compression
|
|
compression_mode: none
|
|
# gives a hint (%) to Ceph in terms of expected consumption of the total cluster capacity of a given pool
|
|
# for more info: https://docs.ceph.com/docs/master/rados/operations/placement-groups/#specifying-expected-pool-size
|
|
#target_size_ratio: ".5"
|
|
# The pool spec used to create the data pool. Can use replication or erasure coding.
|
|
dataPool:
|
|
failureDomain: host
|
|
replicated:
|
|
size: 3
|
|
# Disallow setting pool with replica 1, this could lead to data loss without recovery.
|
|
# Make sure you're *ABSOLUTELY CERTAIN* that is what you want
|
|
requireSafeReplicaSize: true
|
|
parameters:
|
|
# RGW data pools are expected to be large, so mark them as "bulk" so that the PG autoscaler will treat them accordingly
|
|
# (see https://docs.ceph.com/en/reef/rados/operations/placement-groups/)
|
|
# In short, it will precreate a full number of PGs, so that the cluster works with optimal performance from day 1.
|
|
bulk: "true"
|
|
# Inline compression mode for the data pool
|
|
# Further reference: https://docs.ceph.com/docs/master/rados/configuration/bluestore-config-ref/#inline-compression
|
|
compression_mode: none
|
|
# gives a hint (%) to Ceph in terms of expected consumption of the total cluster capacity of a given pool
|
|
# for more info: https://docs.ceph.com/docs/master/rados/operations/placement-groups/#specifying-expected-pool-size
|
|
#target_size_ratio: ".5"
|
|
# Whether to preserve metadata and data pools on object store deletion
|
|
preservePoolsOnDelete: false
|
|
# The gateway service configuration
|
|
gateway:
|
|
# A reference to the secret in the rook namespace where the ssl certificate is stored
|
|
# sslCertificateRef:
|
|
# A reference to the secret in the rook namespace where the ca bundle is stored
|
|
# caBundleRef:
|
|
# The port that RGW pods will listen on (http)
|
|
port: 80
|
|
# The port that RGW pods will listen on (https). An ssl certificate is required.
|
|
# securePort: 443
|
|
# The number of pods in the rgw deployment
|
|
instances: 1
|
|
# The affinity rules to apply to the rgw deployment.
|
|
placement:
|
|
podAntiAffinity:
|
|
preferredDuringSchedulingIgnoredDuringExecution:
|
|
- weight: 100
|
|
podAffinityTerm:
|
|
labelSelector:
|
|
matchExpressions:
|
|
- key: app
|
|
operator: In
|
|
values:
|
|
- rook-ceph-rgw
|
|
# topologyKey: */zone can be used to spread RGW across different AZ
|
|
topologyKey: kubernetes.io/hostname
|
|
# A key/value list of annotations
|
|
# nodeAffinity:
|
|
# requiredDuringSchedulingIgnoredDuringExecution:
|
|
# nodeSelectorTerms:
|
|
# - matchExpressions:
|
|
# - key: role
|
|
# operator: In
|
|
# values:
|
|
# - rgw-node
|
|
# topologySpreadConstraints:
|
|
# tolerations:
|
|
# - key: rgw-node
|
|
# operator: Exists
|
|
# podAffinity:
|
|
# podAntiAffinity:
|
|
# A key/value list of annotations
|
|
annotations:
|
|
# key: value
|
|
# A key/value list of labels
|
|
labels:
|
|
# key: value
|
|
# service:
|
|
# # A key/value list of annotations to add to the rgw service
|
|
# annotations:
|
|
# key: value
|
|
# # A key/value list of labels to add to the rgw service
|
|
# labels:
|
|
# key: value
|
|
resources:
|
|
# The requests and limits set here, allow the object store gateway Pod(s) to use half of one CPU core and 1 gigabyte of memory
|
|
# limits:
|
|
# memory: "1024Mi"
|
|
# requests:
|
|
# cpu: "500m"
|
|
# memory: "1024Mi"
|
|
priorityClassName: system-cluster-critical
|
|
# # Add arbitrary volume mounts to RGW pods
|
|
# additionalVolumeMounts:
|
|
# # 'rgw-ldap' secret keys will show up as files in RGW container in dir /var/rgw/ldap
|
|
# - subPath: ldap
|
|
# volumeSource:
|
|
# secret:
|
|
# secretName: rgw-ldap
|
|
# defaultMode: 0600
|
|
# opsLogSidecar:
|
|
# resources:
|
|
# limits:
|
|
# memory: "60Mi"
|
|
# requests:
|
|
# cpu: "100m"
|
|
# memory: "60Mi"
|
|
# zone:
|
|
# name: zone-a
|
|
# service endpoint healthcheck
|
|
healthCheck:
|
|
# Configure the pod probes for the rgw daemon
|
|
startupProbe:
|
|
disabled: false
|
|
readinessProbe:
|
|
disabled: false
|
|
# hosting:
|
|
# The list of subdomain names for virtual hosting of buckets.
|
|
# dnsNames:
|
|
# - "mystore.example.com"
|
|
|
|
# If a CephObjectStoreUser is created in a namespace other than the Rook cluster namespace,
|
|
# the namespace must be added to the list of allowed namespaces, or specify "*" to allow all namespaces.
|
|
# allowUsersInNamespaces:
|
|
# - other-namespace
|
|
# security oriented settings
|
|
# security:
|
|
# To enable the Server Side Encryption configuration properly don't forget to uncomment the Secret at the end of the file
|
|
# kms: # configures RGW with AWS-SSE:KMS
|
|
# # name of the config map containing all the kms connection details
|
|
# connectionDetails:
|
|
# KMS_PROVIDER: "vault"
|
|
# VAULT_ADDR: VAULT_ADDR_CHANGE_ME # e,g: http://vault.my-domain.com:8200
|
|
# VAULT_BACKEND_PATH: "rook"
|
|
# VAULT_SECRET_ENGINE: "kv"
|
|
# VAULT_BACKEND: v2
|
|
# # name of the secret containing the kms authentication token
|
|
# tokenSecretName: rook-vault-token
|
|
# s3: # configures RGW with AWS-SSE:S3
|
|
# # name of the config map containing all the kms connection details
|
|
# connectionDetails:
|
|
# KMS_PROVIDER: "vault"
|
|
# VAULT_ADDR: VAULT_ADDR_CHANGE_ME # e,g: http://vault.my-domain.com:8200
|
|
# VAULT_BACKEND_PATH: "rook"
|
|
# VAULT_SECRET_ENGINE: "transit"
|
|
# # name of the secret containing the kms authentication token
|
|
# tokenSecretName: rook-vault-token
|
|
# # UNCOMMENT THIS TO ENABLE A KMS CONNECTION
|
|
# # Also, do not forget to replace both:
|
|
# # * ROOK_TOKEN_CHANGE_ME: with a base64 encoded value of the token to use
|
|
# # * VAULT_ADDR_CHANGE_ME: with the Vault address
|
|
# ---
|
|
# apiVersion: v1
|
|
# kind: Secret
|
|
# metadata:
|
|
# name: rook-vault-token
|
|
# namespace: rook-ceph # namespace:cluster
|
|
# data:
|
|
# token: ROOK_TOKEN_CHANGE_ME
|