You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,7 +83,7 @@ Use the status connectionStatus field to check the status of the MySQL connectio
83
83
### RelationalDatabaseProvider Spec Fields
84
84
85
85
- kind (required): The type of database provider, which can be either mysql or postgresql.
86
-
-scope (required): Defines the scope of the database request, which influences the environment setup. Valid values are production, development, and custom. Defaults to development if not specified.
86
+
-selector (required): Defines the selector of the database request, which influences the environment setup. Valid values are production, development, and custom. Defaults to development if not specified.
87
87
- connections (required): A list of `connection` objects that detail the connection parameters to MySQL or PostgreSQL databases. At least one connection must be defined.
88
88
89
89
- connection Fields
@@ -116,7 +116,7 @@ metadata:
116
116
name: example-mysql-provider
117
117
spec:
118
118
kind: mysql
119
-
scope: development
119
+
selector: development
120
120
mysqlConnections:
121
121
- name: primary-db
122
122
hostname: primary-db.example.com
@@ -130,12 +130,12 @@ spec:
130
130
131
131
## DatabaseRequest CRD Documentation
132
132
133
-
The `DatabaseRequest` Custom Resource Definition (CRD) provides a mechanism for requesting database instances within a Kubernetes cluster. This resource allows lagoon to specify their requirements for a database, including the type, scope, and optional parameters such as seeding data, additional users, and database connection references. This documentation outlines the structure and functionality of the `DatabaseRequest` resource to facilitate its usage.
133
+
The `DatabaseRequest` Custom Resource Definition (CRD) provides a mechanism for requesting database instances within a Kubernetes cluster. This resource allows lagoon to specify their requirements for a database, including the type, selector, and optional parameters such as seeding data, additional users, and database connection references. This documentation outlines the structure and functionality of the `DatabaseRequest` resource to facilitate its usage.
134
134
135
135
### DatabaseRequest Spec Fields
136
136
137
137
- name (required): Defines the intended service name for the database. This field is required and must be unique within the namespace.
138
-
- scope (required): Defines the intended use of the requested database. It helps in configuring the database appropriately for its intended environment. Valid options are production, development, and custom. The default value is development.
138
+
- selector (required): Defines the intended use of the requested database. It helps in configuring the database appropriately for its intended environment. Valid options are production, development, and custom. The default value is development.
139
139
- type (required): Specifies the type of database requested. Supported types are mysql, mariadb, postgres, and mongodb.
140
140
- seed (optional): A reference to a local Kubernetes secret within the same namespace that contains data used for seeding the database. This field is optional and intended for initial database setup.
141
141
- additionalUsers (optional): Specifies the creation of additional database users.
0 commit comments