Refactor Distributed Analytics project structure
[demo.git] / vnfs / DAaaS / operator / charts / etcd-operator / values.yaml
diff --git a/vnfs/DAaaS/operator/charts/etcd-operator/values.yaml b/vnfs/DAaaS/operator/charts/etcd-operator/values.yaml
deleted file mode 100644 (file)
index 1260e07..0000000
+++ /dev/null
@@ -1,153 +0,0 @@
-# Default values for etcd-operator.
-# This is a YAML-formatted file.
-# Declare variables to be passed into your templates.
-
-## Install Default RBAC roles and bindings
-rbac:
-  create: true
-  apiVersion: v1beta1
-
-## Service account names and whether to create them
-serviceAccount:
-  etcdOperatorServiceAccount:
-    create: true
-    name:
-  backupOperatorServiceAccount:
-    create: true
-    name:
-  restoreOperatorServiceAccount:
-    create: true
-    name:
-
-# Select what to deploy
-deployments:
-  etcdOperator: true
-  # one time deployment, delete once completed,
-  # Ref: https://github.com/coreos/etcd-operator/blob/master/doc/user/walkthrough/backup-operator.md
-  backupOperator: true
-  # one time deployment, delete once completed
-  # Ref: https://github.com/coreos/etcd-operator/blob/master/doc/user/walkthrough/restore-operator.md
-  restoreOperator: true
-
-# creates custom resources, not all required,
-# you could use `helm template --values <values.yaml> --name release_name ... `
-# and create the resources yourself to deploy on your cluster later
-customResources:
-  createEtcdClusterCRD: false
-  createBackupCRD: false
-  createRestoreCRD: false
-
-# etcdOperator
-etcdOperator:
-  name: etcd-operator
-  replicaCount: 1
-  image:
-    repository: quay.io/coreos/etcd-operator
-    tag: v0.9.3
-    pullPolicy: Always
-  resources:
-    cpu: 100m
-    memory: 128Mi
-  ## Node labels for etcd-operator pod assignment
-  ## Ref: https://kubernetes.io/docs/user-guide/node-selection/
-  nodeSelector: {}
-  ## additional command arguments go here; will be translated to `--key=value` form
-  ## e.g., analytics: true
-  commandArgs:
-    cluster-wide: true
-  ## Configurable health checks against the /readyz endpoint that etcd-operator exposes
-  readinessProbe:
-    enabled: false
-    initialDelaySeconds: 0
-    periodSeconds: 10
-    timeoutSeconds: 1
-    successThreshold: 1
-    failureThreshold: 3
-  livenessProbe:
-    enabled: false
-    initialDelaySeconds: 0
-    periodSeconds: 10
-    timeoutSeconds: 1
-    successThreshold: 1
-    failureThreshold: 3
-# backup spec
-backupOperator:
-  name: etcd-backup-operator
-  replicaCount: 1
-  image:
-    repository: quay.io/coreos/etcd-operator
-    tag: v0.9.3
-    pullPolicy: Always
-  resources:
-    cpu: 100m
-    memory: 128Mi
-  spec:
-    storageType: S3
-    s3:
-      s3Bucket:
-      awsSecret:
-  ## Node labels for etcd pod assignment
-  ## Ref: https://kubernetes.io/docs/user-guide/node-selection/
-  nodeSelector: {}
-  ## additional command arguments go here; will be translated to `--key=value` form
-  ## e.g., analytics: true
-  commandArgs: {}
-
-# restore spec
-restoreOperator:
-  name: etcd-restore-operator
-  replicaCount: 1
-  image:
-    repository: quay.io/coreos/etcd-operator
-    tag: v0.9.3
-    pullPolicy: Always
-  port: 19999
-  resources:
-    cpu: 100m
-    memory: 128Mi
-  spec:
-    s3:
-      # The format of "path" must be: "<s3-bucket-name>/<path-to-backup-file>"
-      # e.g: "etcd-snapshot-bucket/v1/default/example-etcd-cluster/3.2.10_0000000000000001_etcd.backup"
-      path:
-      awsSecret:
-  ## Node labels for etcd pod assignment
-  ## Ref: https://kubernetes.io/docs/user-guide/node-selection/
-  nodeSelector: {}
-  ## additional command arguments go here; will be translated to `--key=value` form
-  ## e.g., analytics: true
-  commandArgs: {}
-
-## etcd-cluster specific values
-etcdCluster:
-  name: etcd
-  size: 3
-  version: 3.2.25
-  image:
-    repository: quay.io/coreos/etcd
-    tag: v3.2.25
-    pullPolicy: Always
-  enableTLS: false
-  # TLS configs
-  tls:
-    static:
-      member:
-        peerSecret: etcd-peer-tls
-        serverSecret: etcd-server-tls
-      operatorSecret: etcd-client-tls
-  ## etcd cluster pod specific values
-  ## Ref: https://github.com/coreos/etcd-operator/blob/master/doc/user/spec_examples.md#three-members-cluster-with-resource-requirement
-  pod:
-    ## Antiaffinity for etcd pod assignment
-    ## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
-    antiAffinity: false
-    resources:
-      limits:
-        cpu: 100m
-        memory: 128Mi
-      requests:
-        cpu: 100m
-        memory: 128Mi
-    ## Node labels for etcd pod assignment
-    ## Ref: https://kubernetes.io/docs/user-guide/node-selection/
-    nodeSelector: {}