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: designs/helper_to_upgrade_projects_by_rescaffolding.md
-2
Original file line number
Diff line number
Diff line change
@@ -83,8 +83,6 @@ make less painful this process. Examples:
83
83
- Deal with customizations or deviations from the proposed layout
84
84
- Be able to perform the project upgrade to the latest changes without human interactions
85
85
- Deal and support external plugins
86
-
- Provides support to [declarative](https://book.kubebuilder.io/plugins/declarative-v1.html) plugin
87
-
since it is desired and planned to decouple this solution and donate this plugin to its own authors [More info](https://github.com/kubernetes-sigs/kubebuilder/issues/3186)
88
86
- Provide support to older version before having the Project config (Kubebuilder < 3x) and the go/v2 layout which exists to ensure a backwards compatibility with legacy layout provided by Kubebuilder 2x
|[kustomize.common.kubebuilder.io/v1](https://github.com/kubernetes-sigs/kubebuilder/pull/3235/kustomize-v1.md)| kustomize/v1 (Deprecated) | Responsible for scaffolding all manifests to configure projects with [kustomize(v3)][kustomize]. (create and update the `config/` directory). This plugin is used in the composition to create the plugin (`go/v3`). |
19
-
|[kustomize.common.kubebuilder.io/v2](kustomize-v2.md)|`kustomize/v2`| It has the same purpose of `kustomize/v1`. However, it works with [kustomize][kustomize] version `v4` and addresses the required changes for future kustomize configurations. It will probably be used with the future `go/v4-alpha` plugin. |
20
-
|`base.go.kubebuilder.io/v3`|`base/v3`| Responsible for scaffolding all files that specifically require Golang. This plugin is used in composition to create the plugin (`go/v3`) |
21
-
|`base.go.kubebuilder.io/v4`|`base/v4`| Responsible for scaffolding all files which specifically requires Golang. This plugin is used in the composition to create the plugin (`go/v4`) |
|[kustomize.common.kubebuilder.io/v2](kustomize-v2.md)|`kustomize/v2`| Responsible for scaffolding all [kustomize][kustomize] files under the `config/` directory |
19
+
|`base.go.kubebuilder.io/v4`|`base/v4`| Responsible for scaffolding all files which specifically requires Golang. This plugin is used in the composition to create the plugin (`go/v4`) |
Copy file name to clipboardexpand all lines: docs/book/src/reference/project-config.md
+21-21
Original file line number
Diff line number
Diff line change
@@ -130,28 +130,28 @@ version: "3"
130
130
131
131
Now let's check its layout fields definition:
132
132
133
-
| Field | Description |
134
-
|----------|-------------|
135
-
| `layout` | Defines the global plugins, e.g. a project `init` with `--plugins="go/v3,declarative"` means that any sub-command used will always call its implementation for both plugins in a chain. |
136
-
| `domain` | Store the domain of the project. This information can be provided by the user when the project is generate with the `init` sub-command and the `domain` flag. |
137
-
| `plugins` | Defines the plugins used to do custom scaffolding, e.g. to use the optional `declarative` plugin to do scaffolding for just a specific api via the command `kubebuider create api [options] --plugins=declarative/v1`. |
| `layout` | Defines the global plugins, e.g. a project `init` with `--plugins="go/v4,deploy-image/v1-alpha"` means that any sub-command used will always call its implementation for both plugins in a chain. |
136
+
| `domain` | Store the domain of the project. This information can be provided by the user when the project is generate with the `init` sub-command and the `domain` flag. |
137
+
| `plugins` | Defines the plugins used to do custom scaffolding, e.g. to use the optional `deploy-image/v1-alpha` plugin to do scaffolding for just a specific api via the command `kubebuider create api [options] --plugins=deploy-image/v1-alpha`. |
138
138
| `projectName` | The name of the project. This will be used to scaffold the manager data. By default it is the name of the project directory, however, it can be provided by the user in the `init` sub-command via the `--project-name` flag. |
139
-
| `repo` | The project repository which is the Golang module, e.g `github.com/example/myproject-operator`. |
140
-
| `resources` | An array of all resources which were scaffolded in the project. |
141
-
| `resources.api` | The API scaffolded in the project via the sub-command `create api`. |
142
-
| `resources.api.crdVersion` | The Kubernetes API version (`apiVersion`) used to do the scaffolding for the CRD resource. |
143
-
| `resources.api.namespaced` | The API RBAC permissions which can be namespaced or cluster scoped. |
144
-
| `resources.controller` | Indicates whether a controller was scaffolded for the API. |
145
-
| `resources.domain` | The domain of the resource which is provided by the `--domain` flag when the sub-command `create api` is used. |
146
-
| `resources.group` | The GKV group of the resource which is provided by the `--group` flag when the sub-command `create api` is used. |
147
-
| `resources.version` | The GKV version of the resource which is provided by the `--version` flag when the sub-command `create api` is used. |
148
-
| `resources.kind` | Store GKV Kind of the resource which is provided by the `--kind` flag when the sub-command `create api` is used. |
149
-
| `resources.path` | The import path for the API resource. It will be `<repo>/api/<kind>` unless the API added to the project is an external or core-type. For the core-types scenarios, the paths used are mapped [here][core-types]. |
150
-
| `resources.webhooks`| Store the webhooks data when the sub-command `create webhook` is used. |
151
-
| `resources.webhooks.webhookVersion` | The Kubernetes API version (`apiVersion`) used to scaffold the webhook resource. |
152
-
| `resources.webhooks.conversion` | It is `true` when the webhook was scaffold with the `--conversion` flag which means that is a conversion webhook. |
153
-
| `resources.webhooks.defaulting` | It is `true` when the webhook was scaffold with the `--defaulting` flag which means that is a defaulting webhook. |
154
-
| `resources.webhooks.validation` | It is `true` when the webhook was scaffold with the `--programmatic-validation` flag which means that is a validation webhook. |
139
+
| `repo` | The project repository which is the Golang module, e.g `github.com/example/myproject-operator`. |
140
+
| `resources` | An array of all resources which were scaffolded in the project. |
141
+
| `resources.api` | The API scaffolded in the project via the sub-command `create api`. |
142
+
| `resources.api.crdVersion` | The Kubernetes API version (`apiVersion`) used to do the scaffolding for the CRD resource. |
143
+
| `resources.api.namespaced` | The API RBAC permissions which can be namespaced or cluster scoped. |
144
+
| `resources.controller` | Indicates whether a controller was scaffolded for the API. |
145
+
| `resources.domain` | The domain of the resource which is provided by the `--domain` flag when the sub-command `create api` is used. |
146
+
| `resources.group` | The GKV group of the resource which is provided by the `--group` flag when the sub-command `create api` is used. |
147
+
| `resources.version` | The GKV version of the resource which is provided by the `--version` flag when the sub-command `create api` is used. |
148
+
| `resources.kind` | Store GKV Kind of the resource which is provided by the `--kind` flag when the sub-command `create api` is used. |
149
+
| `resources.path` | The import path for the API resource. It will be `<repo>/api/<kind>` unless the API added to the project is an external or core-type. For the core-types scenarios, the paths used are mapped [here][core-types]. |
150
+
| `resources.webhooks`| Store the webhooks data when the sub-command `create webhook` is used. |
151
+
| `resources.webhooks.webhookVersion` | The Kubernetes API version (`apiVersion`) used to scaffold the webhook resource. |
152
+
| `resources.webhooks.conversion` | It is `true` when the webhook was scaffold with the `--conversion` flag which means that is a conversion webhook. |
153
+
| `resources.webhooks.defaulting` | It is `true` when the webhook was scaffold with the `--defaulting` flag which means that is a defaulting webhook. |
154
+
| `resources.webhooks.validation` | It is `true` when the webhook was scaffold with the `--programmatic-validation` flag which means that is a validation webhook. |
0 commit comments