Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

📖 small fixes for the doc Using External Resources #4211

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 0 additions & 14 deletions docs/book/src/reference/using_an_external_resource.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,18 +73,6 @@ Also, the RBAC role:
This scaffolds a controller for the external type but skips creating new resource
definitions since the type is defined in an external project.

### Creating a Webhook to Manage an External Type

<aside>
<H1> Support </H1>

Webhook support for external types is not currently automated by the tool.
However, you can still use the tool to scaffold the webhook setup and make
manual adjustments as needed. For guidance, you can follow a similar approach as
described in the section [Webhooks for Core Types][webhook-for-core-types].

</aside>

## Managing Core Types

Core Kubernetes API types, such as `Pods`, `Services`, and `Deployments`, are predefined by Kubernetes.
Expand Down Expand Up @@ -169,8 +157,6 @@ Also, the RBAC for the above markers:
- update
```

```

This scaffolds a controller for the Core type `corev1.Pod` but skips creating new resource
definitions since the type is already defined in the Kubernetes API.

Expand Down
Loading