Open abbi-gaurav opened 3 months ago
This works fine. Thank you
We have a similar flow already: Quick Install --> Create a Workload --> Expose a Workload that uses HTTPBin instead of nginx and should work on both k3d and Gardener. I’ll be working on the tutorials as part of this issue so they’re more straightforward also for developers who’d like to install API Gateway locally
The Quick Install guide should be the entry point for all Kyma tutorials that you can see on the kyma-project website, so I'd like to update the k3d cluster create... command
there.
@abbi-gaurav @triffer I have a few questions regarding the steps:
-p 30080:80@loadbalancer -p 30443:443@loadbalancer
? It would be best if we could have the same version of API Gateway tutorials for managed and OS Kyma. If I understand correctly, with this change, I also need to add two versions of commands for accessing workloads, which I can do, but I'd rather keep it simple. 30080
and 30443
, do you think there might be other tutorials for other modules that need updating (besides the ones for API Gateway)? @abbi-gaurav, could you have a look at the above comment, please?
I think steps core DNS update are required. Regarding ports, it is not a must to use these ports. They can be some other ports. Since we are talking about running kyma locally, we need to use ports that are not reserved.
@nataliasitko @mmitoraj in quick install we have slightly different command:
`k3d cluster create --k3s-arg ‘--tls-san=host.docker.internal@server:*’
kubectl create ns kyma-system`
while in the issue:
k3d cluster create kyma --kubeconfig-switch-context -p 30080:80@loadbalancer -p 30443:443@loadbalancer --k3s-arg "--disable=traefik@server:0"
kubectl create ns kyma-system
this needs to be adjusted in quick install
I've updated the command, added the step to update CoreDNS, and added a note about the ports. It's approved by Goats. @abbi-gaurav Could you also see if it's fine with you? Here's the PR: https://github.com/kyma-project/kyma/pull/18749/files
Description
Technically advanced users like to try out kyma locally. Using k3d is the easiest way to do it. However, there is no clear step-by-step documentation. It is scattered, and some steps may be wrong.
e.g. this local domain is no longer used
I tried myself and was able to put together a set of steps. Thanks to @triffer for resolving one misconfiguration issue:
Steps
local.kyma.dev
domain/etc/hosts
to point tonginx.local.kyma.dev