From 239afe9e160605ade9cff3a2d839566d1583d9aa Mon Sep 17 00:00:00 2001 From: Piotr Halama Date: Fri, 10 May 2024 08:53:54 +0200 Subject: [PATCH] Deprecate kyma provision k3d command (#18673) * Deprecate kyma provision k3d command * add missing * use local registry in docs --- docs/02-get-started/01-quick-install.md | 3 ++- .../troubleshooting/01-k3d-fails-on-linux.md | 4 ++-- .../docs/application-connectivity-validator-tests.md | 4 +++- .../application-connector/docs/application-gateway-tests.md | 4 +++- .../docs/compass-runtime-agent-tests.md | 6 ++++-- tests/components/application-connector/scripts/test-cra.sh | 4 +++- 6 files changed, 17 insertions(+), 8 deletions(-) diff --git a/docs/02-get-started/01-quick-install.md b/docs/02-get-started/01-quick-install.md index 976525a833a4..3e0e9034f175 100644 --- a/docs/02-get-started/01-quick-install.md +++ b/docs/02-get-started/01-quick-install.md @@ -17,7 +17,8 @@ To get started with Kyma, let's quickly install it with specific modules first. 1. Provision a k3d cluster, run: ```bash - kyma provision k3d + k3d cluster create + kubectl create ns kyma-system ``` 1. To install a Kyma module of your choice on a Kubernetes cluster, deploy its module manager and apply the module configuration. See the following Kyma modules with their quick installation commands and links to their GitHub repositories: diff --git a/docs/04-operation-guides/troubleshooting/01-k3d-fails-on-linux.md b/docs/04-operation-guides/troubleshooting/01-k3d-fails-on-linux.md index 76770d751c64..09f637b673b2 100644 --- a/docs/04-operation-guides/troubleshooting/01-k3d-fails-on-linux.md +++ b/docs/04-operation-guides/troubleshooting/01-k3d-fails-on-linux.md @@ -14,7 +14,7 @@ On Linux, the ports are reserved to be used by a privileged user. Use a custom port for the load balancer. For example, use the port `8080`: ```bash -kyma provision k3d -p 8080:80@loadbalancer -p 8443:443@loadbalancer +k3d cluster create -p 8080:80@loadbalancer -p 8443:443@loadbalancer ``` -Alternatively, execute the `kyma provision k3d` command with sudo privileges. +Alternatively, execute the `k3d cluster create` command with sudo privileges. diff --git a/tests/components/application-connector/docs/application-connectivity-validator-tests.md b/tests/components/application-connector/docs/application-connectivity-validator-tests.md index c293701ff3c8..c7f16db5d341 100644 --- a/tests/components/application-connector/docs/application-connectivity-validator-tests.md +++ b/tests/components/application-connector/docs/application-connectivity-validator-tests.md @@ -46,7 +46,9 @@ Pipelines run the tests using the **test-validator** target from the `Makefile`. 1. Provision a local Kubernetes cluster with k3d: ```sh - kyma provision k3d + k3d registry create kyma-registry --port 5001 + k3d cluster create kyma --kubeconfig-switch-context -p 80:80@loadbalancer -p 443:443@loadbalancer --registry-use kyma-registry + kubectl create ns kyma-system ``` 2. Install the minimal set of components required to run Application Connectivity Validator **for Kyma SKR (Compass mode)**: diff --git a/tests/components/application-connector/docs/application-gateway-tests.md b/tests/components/application-connector/docs/application-gateway-tests.md index d8c08a3754eb..87a88f58d4e6 100644 --- a/tests/components/application-connector/docs/application-gateway-tests.md +++ b/tests/components/application-connector/docs/application-gateway-tests.md @@ -107,7 +107,9 @@ Pipelines run the tests using the **test-gateway** target from the `Makefile`. 1. Provision a local Kubernetes cluster with k3d: ```sh - kyma provision k3d + k3d registry create kyma-registry --port 5001 + k3d cluster create kyma --kubeconfig-switch-context -p 80:80@loadbalancer -p 443:443@loadbalancer --registry-use kyma-registry + kubectl create ns kyma-system ``` 2. Install the minimal set of components required to run Application Gateway for either Kyma OS or SKR: diff --git a/tests/components/application-connector/docs/compass-runtime-agent-tests.md b/tests/components/application-connector/docs/compass-runtime-agent-tests.md index afc21a24958b..0bd25c9c7632 100644 --- a/tests/components/application-connector/docs/compass-runtime-agent-tests.md +++ b/tests/components/application-connector/docs/compass-runtime-agent-tests.md @@ -56,7 +56,9 @@ Pipelines run the tests using the **test-compass-runtime-agent** target from the 1. Provision a local Kubernetes cluster with k3d: ```bash - kyma provision k3d + k3d registry create kyma-registry --port 5001 + k3d cluster create kyma --kubeconfig-switch-context -p 80:80@loadbalancer -p 443:443@loadbalancer --registry-use kyma-registry + kubectl create ns kyma-system ``` 2. Install the minimal set of components required to run Compass Runtime Agent **for Kyma SKR (Compass mode)**: @@ -135,4 +137,4 @@ To run the test in your IDE, perform the following steps. ```bash make clean-test-compass-runtime-agent-test - ``` \ No newline at end of file + ``` diff --git a/tests/components/application-connector/scripts/test-cra.sh b/tests/components/application-connector/scripts/test-cra.sh index f3313d1075cf..2b84c945eafc 100755 --- a/tests/components/application-connector/scripts/test-cra.sh +++ b/tests/components/application-connector/scripts/test-cra.sh @@ -5,7 +5,9 @@ service docker start curl -s https://raw.githubusercontent.com/k3d-io/k3d/main/install.sh | bash curl -Lo kyma.tar.gz "https://github.com/kyma-project/cli/releases/download/$(curl -s https://api.github.com/repos/kyma-project/cli/releases/latest | grep tag_name | cut -d '"' -f 4)/kyma_Linux_x86_64.tar.gz" && mkdir kyma-release && tar -C kyma-release -zxvf kyma.tar.gz && chmod +x kyma-release/kyma && rm -rf kyma.tar.gz -kyma-release/kyma provision k3d +k3d registry create kyma-registry --port 5001 +k3d cluster create kyma --kubeconfig-switch-context -p 80:80@loadbalancer -p 443:443@loadbalancer --registry-use kyma-registry +kubectl create ns kyma-system kubectl cluster-info kyma-release/kyma deploy --ci --components-file tests/components/application-connector/resources/installation-config/mini-kyma-skr.yaml --source local --workspace $PWD cd tests/components/application-connector