1
0
Fork 0
mirror of https://github.com/chrislusf/seaweedfs synced 2024-05-08 20:41:20 +02:00
seaweedfs/k8s/helm_charts2/templates
Kaiwalya Joshi bee482d49e
fix: Remove invalid serviceName from s3-deployments template.
Remove `deployments.spec.serviceName` from the s3 deployment template.

`serviceName` isn't a valid field and causes issues when deploying the
chart.

This is the full output for `kubectl explain deployments.spec`
```
KIND:     Deployment
VERSION:  apps/v1

RESOURCE: spec <Object>

DESCRIPTION:
     Specification of the desired behavior of the Deployment.

     DeploymentSpec is the specification of the desired behavior of the
     Deployment.

FIELDS:
   minReadySeconds      <integer>
     Minimum number of seconds for which a newly created pod should be ready
     without any of its container crashing, for it to be considered available.
     Defaults to 0 (pod will be considered available as soon as it is ready)

   paused       <boolean>
     Indicates that the deployment is paused.

   progressDeadlineSeconds      <integer>
     The maximum time in seconds for a deployment to make progress before it is
     considered to be failed. The deployment controller will continue to process
     failed deployments and a condition with a ProgressDeadlineExceeded reason
     will be surfaced in the deployment status. Note that progress will not be
     estimated during the time a deployment is paused. Defaults to 600s.

   replicas     <integer>
     Number of desired pods. This is a pointer to distinguish between explicit
     zero and not specified. Defaults to 1.

   revisionHistoryLimit <integer>
     The number of old ReplicaSets to retain to allow rollback. This is a
     pointer to distinguish between explicit zero and not specified. Defaults to
     10.

   selector     <Object> -required-
     Label selector for pods. Existing ReplicaSets whose pods are selected by
     this will be the ones affected by this deployment. It must match the pod
     template's labels.

   strategy     <Object>
     The deployment strategy to use to replace existing pods with new ones.

   template     <Object> -required-
     Template describes the pods that will be created.
```
2022-05-19 15:01:27 -07:00
..
_helpers.tpl deprecate all cronjob module related code 2021-12-05 01:20:47 -08:00
ca-cert.yaml
cert-clusterissuer.yaml
client-cert.yaml
filer-cert.yaml
filer-service-client.yaml rename directory 2021-08-23 13:37:09 -07:00
filer-service.yaml
filer-servicemonitor.yaml ignore ServiceMonitor when monitoring is disabled 2021-10-03 18:35:04 +02:00
filer-statefulset.yaml fix filer using leveldb2 may lose data 2022-04-18 18:31:45 +08:00
ingress.yaml Update resource API versions up to K8S 1.22 2021-11-22 07:11:53 +01:00
master-cert.yaml
master-service.yaml
master-statefulset.yaml rename directory 2021-08-23 13:37:09 -07:00
s3-deployment.yaml fix: Remove invalid serviceName from s3-deployments template. 2022-05-19 15:01:27 -07:00
s3-service.yaml
s3-servicemonitor.yaml ignore ServiceMonitor when monitoring is disabled 2021-10-03 18:35:04 +02:00
seaweedfs-grafana-dashboard.yaml
seaweedfs-s3-secret.yaml helm add auditLogConfig option 2021-12-14 18:05:22 +05:00
secret-seaweedfs-db.yaml
security-configmap.yaml
service-account.yaml Update resource API versions up to K8S 1.22 2021-11-22 07:11:53 +01:00
volume-cert.yaml
volume-service.yaml
volume-servicemonitor.yaml ignore ServiceMonitor when monitoring is disabled 2021-10-03 18:35:04 +02:00
volume-statefulset.yaml graceful stop cluster http server default timeout 60 sec 2022-02-08 13:07:28 +05:00