Adding security_context flag to charms

[osm/devops.git] / installers / charm / keystone / config.yaml

diff --git a/installers/charm/keystone/config.yaml b/installers/charm/keystone/config.yaml
index 2758d1c..dc0953a 100644 (file)
--- a/installers/charm/keystone/config.yaml
+++ b/installers/charm/keystone/config.yaml
@@ -20,6 +20,11 @@ options:
       If there is a reverse proxy in front of Keystone, it may
       need to be configured to handle the requested size.
     default: 5
+  ingress_class:
+    type: string
+    description: |
+      Ingress class name. This is useful for selecting the ingress to be used
+      in case there are multiple ingresses in the underlying k8s clusters.
   ingress_whitelist_source_range:
     type: string
     description: |
@@ -37,6 +42,16 @@ options:
     type: string
     description: Ingress URL
     default: ""
+  image_pull_policy:
+    type: string
+    description: |
+      ImagePullPolicy configuration for the pod.
+      Possible values: always, ifnotpresent, never
+    default: always
+  security_context:
+    description: Enables the security context of the pods
+    type: boolean
+    default: false
   region_id:
     type: string
     description: Region ID to be created when starting the service
@@ -45,6 +60,11 @@ options:
     type: string
     description: Keystone DB Password
     default: admin
+  mysql_uri:
+    type: string
+    description: |
+      Mysql uri with the following format:
+        mysql://<user>:<pass>@<host>:<port>/<database>
   admin_username:
     type: string
     description: Admin username to be created when starting the service