The deployment result is inconsistent according to the document on the official website

[sunwenbo]

I need to deploy loki cluster in the microservice mode in my k8s cluster, and deploy it according to the steps in the official website, but the pod displayed in the cluster is inconsistent with the results given in the document, is the chart updated?

values.yaml is also available on the official website

https://grafana.org.cn/docs/loki/latest/setup/install/helm/install-microservices/

This is mine：

This is the deployment result of the official website：

`# Example configuration for Loki with S3 storage

loki:
schemaConfig:
configs:
- from: 2024-04-01
store: tsdb
object_store: s3
schema: v13
index:
prefix: loki_index_
period: 24h
storage_config:
aws:
region: <AWS region your bucket is in, for example, eu-west-2>
bucketnames: <Your AWS bucket for chunk, for example, aws-loki-dev-chunk>
s3forcepathstyle: false
ingester:
chunk_encoding: snappy
pattern_ingester:
enabled: true
limits_config:
allow_structured_metadata: true
volume_enabled: true
retention_period: 672h # 28 days retention
querier:
max_concurrent: 4

storage:
type: s3
bucketNames:
chunks: <Your AWS bucket for chunk, for example, aws-loki-dev-chunk>
ruler: <Your AWS bucket for ruler, for example, aws-loki-dev-ruler>
admin: <Your AWS bucket for admin, for example, aws-loki-dev-admin>
s3:
# s3 URL can be used to specify the endpoint, access key, secret key, and bucket name this works well for S3 compatible storage or if you are hosting Loki on-premises and want to use S3 as the storage backend. Either use the s3 URL or the individual fields below (AWS endpoint, region, secret).
s3: s3://access_key:secret_access_key@custom_endpoint/bucket_name
# AWS endpoint URL
endpoint:
# AWS region where the S3 bucket is located
region:
# AWS secret access key
secretAccessKey:
# AWS access key ID
accessKeyId:
# AWS signature version (e.g., v2 or v4)
signatureVersion:
# Forces the path style for S3 (true/false)
s3ForcePathStyle: false
# Allows insecure (HTTP) connections (true/false)
insecure: false
# HTTP configuration settings
http_config: {}

deploymentMode: Distributed

Disable minio storage

minio:
enabled: false

ingester:
replicas: 3
querier:
replicas: 3
maxUnavailable: 2
queryFrontend:
replicas: 2
maxUnavailable: 1
queryScheduler:
replicas: 2
distributor:
replicas: 3
maxUnavailable: 2
compactor:
replicas: 1
indexGateway:
replicas: 2
maxUnavailable: 1

bloomPlanner:
replicas: 0
bloomBuilder:
replicas: 0
bloomGateway:
replicas: 0

backend:
replicas: 0
read:
replicas: 0
write:
replicas: 0

singleBinary:
replicas: 0`

I also tried to download the chart package to my server and install it with the helm install loki -f values.yaml.-n loki command, but I also got an error.
This is why？
The chart package I use is downloaded from github.
wget https://github.com/grafana/helm-charts/releases/download/helm-loki-6.23.0/loki-6.23.0.tgz