docs: replace references to kuttl.dev (#649)

Signed-off-by: Marcin Owsiany <[email protected]>

Author: porridge

.goreleaser.yml

@@ -70,7 +70,7 @@ brews:
       email: [email protected]
     skip_upload: auto
     directory: Formula
-    homepage: https://kuttl.dev
+    homepage: https://github.com/kudobuilder/kuttl
     description: Interact with KUTTL via the kubectl plugin
     dependencies:
       - kubernetes-cli

README.md

@@ -1,6 +1,6 @@
 # KUTTL
 
-<img src="https://kuttl.dev/images/kuttl-horizontal-logo.png" width="256">
+<img src="docs/images/kuttl-horizontal-logo.png" width="256">
 
 [![lint](https://github.com/kudobuilder/kuttl/actions/workflows/lint.yml/badge.svg?branch=main)](https://github.com/kudobuilder/kuttl/actions)
 [![unit test](https://github.com/kudobuilder/kuttl/actions/workflows/unittest.yml/badge.svg?branch=main)](https://github.com/kudobuilder/kuttl/actions)

docs/images/kuttl-horizontal-logo.png

@@ -59,7 +59,7 @@ spec:
   version: "v${VERSION}"
 
   shortDescription: Declaratively run and test operators
-  homepage: https://kuttl.dev/
+  homepage: https://github.com/kudobuilder/kuttl
   description: |
     The KUbernetes Test TooL (KUTTL) is a highly productive test
     toolkit for testing operators on Kubernetes.

hack/generate_krew.sh

@@ -81,7 +81,7 @@ The test operator supports connecting to an existing Kubernetes cluster or it ca
 It can also apply manifests before running the tests. If no arguments are provided, the test harness will attempt to
 load the test configuration from kuttl-test.yaml.
 
-For more detailed documentation, visit: https://kuttl.dev`,
+For more detailed documentation, visit: https://github.com/kudobuilder/kuttl`,
 		Example: testExample,
 		PreRunE: func(cmd *cobra.Command, args []string) error {
 			flags := cmd.Flags()

internal/kuttlctl/cmd/test.go

@@ -37,7 +37,7 @@ make integration-test
 
 ## Declarative tests
 
-Most tests written for KUTTL use the [declarative test harness](https://kuttl.dev) with the controller-runtime's envtest (which starts `etcd` and `kube-apiserver` locally). This means that tests can be written for and run against KUTTL without requiring a Kubernetes cluster (or even Docker).
+Most tests written for KUTTL use the [declarative test harness](https://github.com/kudobuilder/kuttl) with the controller-runtime's envtest (which starts `etcd` and `kube-apiserver` locally). This means that tests can be written for and run against KUTTL without requiring a Kubernetes cluster (or even Docker).
 
 ### CLI examples