kyma-incubator / local-kyma Goto Github PK

The failed test: https://github.com/kyma-incubator/local-kyma/runs/1356724634?check_suite_focus=true#step:7:25

{"error":"Calling CSR URL failed with status '500' and body '{\n  \"code\": 500,\n  \"error\": \"Error while decoding pem block\"\n}'"}
registering commerce webservices
jq: error (at <stdin>:0): Cannot index string with string "name"
{"error":"Not connected to a kyma cluster, please re-connect"}
COMMERCE_WEBSERVICES_ID=

The kyma-gateway-certs-cacert had empty cacert field:

apiVersion: v1
data:
  cacert: ""
kind: Secret
metadata:
  annotations:
    meta.helm.sh/release-name: core
    meta.helm.sh/release-namespace: kyma-system
  creationTimestamp: "2020-11-05T06:13:45Z"
  labels:
    app.kubernetes.io/managed-by: Helm
  name: kyma-gateway-certs-cacert
  namespace: istio-system
  resourceVersion: "2990"
  selfLink: /api/v1/namespaces/istio-system/secrets/kyma-gateway-certs-cacert
  uid: 84332623-1653-42fe-b126-7c1e404f8eb0
type: Opaque

There is a new version of K3d ( 3.0 ). This will be the supported one from now on.
The installation does not work with k3d 3.0

When running ./kyma-k3d.sh, I see that there are lots of error logs relating to installation below. It seems that helm repo is not up-to-dated? Please help to check and update, thanks (sorry that I don't know about this one to contribute PR). Noted that my script still completes successfully even getting these errors (pass all tests and I can access https://console.local.kyma.dev)

Release "core" does not exist. Installing it now.
Release "helm-broker" does not exist. Installing it now.
Release "service-catalog" does not exist. Installing it now.
Release "service-catalog-addons" does not exist. Installing it now.
Release "logging" does not exist. Installing it now.
Release "pod-preset" does not exist. Installing it now.
Release "monitoring" does not exist. Installing it now.
Release "dex" does not exist. Installing it now.
Release "cluster-users" does not exist. Installing it now.
Release "tracing" does not exist. Installing it now.
Release "application-connector" does not exist. Installing it now.
Release "rafter" does not exist. Installing it now.
Release "event-sources" does not exist. Installing it now.
Release "ory" does not exist. Installing it now.
Error: failed to download "resources/event-sources" (hint: running helm repo update may help)
Release "knative-provisioner-natss" does not exist. Installing it now.
Error: failed to download "resources/knative-provisioner-natss" (hint: running helm repo update may help)
Release "ingress-dns-cert" does not exist. Installing it now.
load.go:120: Warning: Dependencies are handled in Chart.yaml since apiVersion "v2". We recommend migrating dependencies to Chart.yaml.
Release "api-gateway" does not exist. Installing it now.
Release "kiali" does not exist. Installing it now.
Release "knative-eventing" does not exist. Installing it now.
Release "nats-streaming" does not exist. Installing it now.
Error: failed to download "resources/knative-eventing" (hint: running helm repo update may help)
Error: failed to download "resources/nats-streaming" (hint: running helm repo update may help)
Release "serverless" does not exist. Installing it now.
Release "console" does not exist. Installing it now.
Installing event-sources in the namespace kyma-system
Installing knative-provisioner-natss in the namespace knative-eventing
Installing nats-streaming in the namespace natss
Installing knative-eventing in the namespace knative-eventing
Release "event-sources" does not exist. Installing it now.
Error: failed to download "resources/event-sources" (hint: running helm repo update may help)
Release "knative-provisioner-natss" does not exist. Installing it now.
Error: failed to download "resources/knative-provisioner-natss" (hint: running helm repo update may help)
Release "nats-streaming" does not exist. Installing it now.
Error: failed to download "resources/nats-streaming" (hint: running helm repo update may help)
Release "knative-eventing" does not exist. Installing it now.
Error: failed to download "resources/knative-eventing" (hint: running helm repo update may help)
Installing knative-provisioner-natss in the namespace knative-eventing
Installing nats-streaming in the namespace natss
Installing event-sources in the namespace kyma-system
Installing knative-eventing in the namespace knative-eventing
Release "nats-streaming" does not exist. Installing it now.
Error: failed to download "resources/nats-streaming" (hint: running helm repo update may help)
Release "knative-provisioner-natss" does not exist. Installing it now.
Error: failed to download "resources/knative-provisioner-natss" (hint: running helm repo update may help)
Release "event-sources" does not exist. Installing it now.
Error: failed to download "resources/event-sources" (hint: running helm repo update may help)
Release "knative-eventing" does not exist. Installing it now.
Error: failed to download "resources/knative-eventing" (hint: running helm repo update may help)
Installing nats-streaming in the namespace natss
Installing knative-provisioner-natss in the namespace knative-eventing
Installing event-sources in the namespace kyma-system
Installing knative-eventing in the namespace knative-eventing
Release "nats-streaming" does not exist. Installing it now.
Error: failed to download "resources/nats-streaming" (hint: running helm repo update may help)
Release "knative-provisioner-natss" does not exist. Installing it now.
Error: failed to download "resources/knative-provisioner-natss" (hint: running helm repo update may help)
namespace/kyma-installer created
Release "event-sources" does not exist. Installing it now.
Error: failed to download "resources/event-sources" (hint: running helm repo update may help)
deployment.apps/kyma-installer created
Waiting for 20 command(s) executed in the background, elapsed time: 0 min 12 sec
Release "knative-eventing" does not exist. Installing it now.
Error: failed to download "resources/knative-eventing" (hint: running helm repo update may help)

The scripts support also kind and minikube. The repository needs a fundamental update.

TO DO:

• add section with comparison (fetures, speed, resource consumption)
• unify script naming - apply convention

When Rafter is uninstalled (helm uninstall) it doesn't clean up all the cluster resources: ClusterAssets and ClusterBuckets. The resources are created for the commerce mock API spec. Unfortunately, there is no easy way to delete these resources as they have finalizers.

Hello,
I'm new to k8s and kyma, and trying to make kyma works on my local PC.
I did run command ./kyma-k3d.sh and got this problem below, would you please help me to give some advices what's problem with it?

lanphan@Lans-MacBook-Pro local-kyma % ./kyma-k3d.sh
2af08e21153c458f03cf570e88391d08a6ea95924225898f74c7f9756949af32
7bd408f3f3e78a18c418bb12d91a309eb13d3dd952d11e0a3d46a52b58a3b944
WARN[0000] No node filter specified
INFO[0000] Prep: Network
INFO[0000] Re-using existing network 'k3d-kyma' (2af08e21153c458f03cf570e88391d08a6ea95924225898f74c7f9756949af32)
INFO[0000] Created volume 'k3d-kyma-images'
INFO[0001] Creating node 'k3d-kyma-server-0'
INFO[0001] Creating LoadBalancer 'k3d-kyma-serverlb'
INFO[0001] Starting cluster 'kyma'
INFO[0001] Starting servers...
INFO[0001] Starting Node 'k3d-kyma-server-0'
INFO[0008] Starting agents...
INFO[0008] Starting helpers...
INFO[0008] Starting Node 'k3d-kyma-serverlb'
INFO[0013] (Optional) Trying to get IP of the docker host and inject it into the cluster as 'host.k3d.internal' for easy access
INFO[0015] Successfully added host record to /etc/hosts in 2/2 nodes and to the CoreDNS ConfigMap
INFO[0015] Cluster 'kyma' created successfully!
INFO[0015] --kubeconfig-update-default=false --> sets --kubeconfig-switch-context=false
INFO[0015] You can now use it like this:
kubectl config use-context k3d-kyma
kubectl cluster-info
Cluster created in 0 min 24 sec
✔ Istio core installed
✘ Istiod encountered an error: failed to wait for resource: resources not ready after 5m0s: timed out waiting for the condition
Deployment/istio-system/istiod
✘ Ingress gateways encountered an error: failed to wait for resource: resources not ready after 5m0s: timed out waiting for the condition
Deployment/istio-system/istio-ingressgateway

• Pruning removed resources Error: failed to install manifests: errors occurred during operation

Thanks so much

Hi,

Trying to make the same or similar script working for WSL2 with docker desktop for Windows.
I succeed with the installation only once. With exactly the same script (the previous version for k3d 1.x, not with k3d 3.0).
With the successful installation (apart of the certificate), all pods looked healthy. Except I didn't figure out what to do with the routing and hence Kyma console was not accessible.

But most of the time it just goes nowhere. What I mean is: during installation, it starts well but then loses the connection to cluster. And any command (like for example get all pods) is timing out.

Any plans to make it happen for WSL2? Or is it not the scope for PoC?
Or maybe anyone has any ideas how theoretically make it work with WSL2?

There are some cases when App Conector fails, because the function is not returning the last order. It is not clear what is the root cause. If the event is not received or order details cannot be fetched with app gateway. Extend function code to cache information about incoming events in the separate object and add a check for that object.

Default docker setting allocates just 2GB RAM. It is not enough for k3s cluster with kyma on top. It would be nice to display warning if there is less than 7GB memory allocated.
Docker command to check the memory is:

docker info --format '{{json .MemTotal}}'

Hi,

seems like jq is required during installation? Could you update the install script to check for it?
Sorry if I am wrong I am new to this ;)

There is a guideline about this problem with minikube here:
https://kyma-project.io/docs/#troubleshooting-basic-troubleshooting-can-t-log-in-to-the-console-after-hibernating-the-minikube-cluster

Do I need to do the same in k3d? Which command should I run?

Thanks.

See details here: kyma-project/kyma#10200

If commerce mock fails to establish a connection with Kyma the new token should be requested.
See error: https://github.com/kyma-incubator/local-kyma-k3d/runs/1245802255?check_suite_focus=true#step:6:24
Currently, there is no retry at all:
https://github.com/kyma-incubator/local-kyma-k3d/blob/c8fe89ffaf4b251ed67c0d5170f311b3093f865b/app-connector-example.sh#L85-L97

As the cluster is consuming resources, I've tried to stop it when not deeded using k3d stop -n kyma, and then start it againa k3d start -n kyma.
It seems that after the whole cluster stabilises ( no pods in the CrashLoopBackOff state) after the start, when trying to login into console you get:

I did see that there is script ./kyma-k3d-start.sh , therefore I think I can stop it by using
k3d cluster stop kyma

Somehow it works (without error), but I cannot log into Console.
Is there anyway I can do to refresh token / refresh password so that I can log into Console after restart k3d?

Thanks.

Ory release is the slowest one from all charts in Kyma, and fails frequently. In this case helm reported an error:

Error: failed post-install: warning: Hook post-install ory/charts/oathkeeper/templates/job.yaml failed: Internal error occurred: failed calling webhook "legacysinkbindings.webhook.sources.knative.dev": Post https://eventing-webhook.knative-eventing.svc:443/legacysinkbindings?timeout=10s: dial tcp 10.43.239.58:443: connect: connection refused

Is it possible to reuse old certificates? The more we do local installs, the more certificates we have