forked from gardener/gardener-extension-registry-cache
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Improve the skaffold setup of the extension. Fix
make extension-down
(
gardener#40) * This PR improves the skaffold setup of the extension The change incorporates the changes from gardener/gardener#7757 and gardener/gardener-extension-shoot-rsyslog-relp#5. It simplifies the skaffold setup and drops the ControllerRegistration chart (`./charts/registration`). The `make extension-up` target is now fixed and invoked by the `make ci-e2e-kind` target now. * Add docs * Drop the `make start`, `make start-admission` and `make debug-admission` targets Dropping these targets makes sense because: - similar to gardener we have skaffold setup and gardener dropped `make start-*` targets - some of these targets were already outdated, hence, it means that they are not used - the setup required for these targets is not easy (compared to the skaffold setup), or at least not documented We already have the skaffold-based local setup.
- Loading branch information
1 parent
dc34900
commit a73babe
Showing
23 changed files
with
96 additions
and
367 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
25 changes: 0 additions & 25 deletions
25
charts/registration/templates/controller-registration.yaml
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
# Deploying Registry Cache Extension Locally | ||
|
||
## Prerequisites | ||
|
||
- Make sure that you have a running local Gardener setup. The steps to complete this can be found in the [Deploying Gardener Locally guide](https://github.com/gardener/gardener/blob/master/docs/deployment/getting_started_locally.md). | ||
|
||
## Setting up the Registry Cache Extension | ||
|
||
Make sure that your `KUBECONFIG` environment variable is targeting the local Gardener cluster. When this is ensured, run: | ||
|
||
```bash | ||
make extension-up | ||
``` | ||
|
||
The corresponding make target will build the extension image, load it into the kind cluster Nodes, and deploy the registry-cache ControllerDeployment and ControllerRegistration resources. The container image in the ControllerDeployment will be the image that was build and loaded into the kind cluster Nodes. | ||
|
||
The make target will then deploy then registry-cache admission component. It will build the admission image, load it into the kind cluster Nodes, and finally install the admission component charts to the kind cluster. | ||
|
||
## Creating a `Shoot` Cluster | ||
|
||
Once the above step is completed you can create a Shoot cluster. Review the Shoot specification in [`example/shoot.yaml`](../../example/shoot.yaml). Create the Shoot: | ||
|
||
```bash | ||
kubectl create -f example/shoot.yaml | ||
``` | ||
|
||
## Tearing Down the Dev Environment | ||
|
||
To tear down the development environment delete the Shoot cluster or disable the `registry-cache` extension in the Shoot's specification. When the extension is not used by the Shoot anymore, you can run: | ||
|
||
```bash | ||
make extension-down | ||
``` | ||
|
||
The make target will delete the ControllerDeployment and ControllerRegistration of the extension, and the registry-cache admission helm deployment. |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.