Add get starting guide#176
Conversation
|
|
||
| Example: | ||
| ```console | ||
| export TRUSTEE_ADDR=kbs-service.trusted-execution-clusters.svc.cluster.local |
There was a problem hiding this comment.
For external trustee users, we can't use this address directly.
There was a problem hiding this comment.
I added a comment that it is only for setup up that uses the pod networking like kubevirt
|
A few notes that can be added: Required toolsTo build the operator the following tools are needed:
Setupmake sure the testing environment has the ssh-agent rumming. |
|
Added the tools |
Jakob-Naucke
left a comment
Jakob-Naucke
left a comment
There was a problem hiding this comment.
Thank you for writing this up and sorry for my delayed review. Mostly nits.
docs/usage/getting-started-guide.md
Outdated
|
|
||
| These ports can be used in order to access the endpoint if you are creating the VMs externally to the cluster, for example via Libvirt. | ||
|
|
||
| Alongside the kind cluster, a registry is running and can be accessed with tagging, pushing and pulling the images using `locahost:5000` from and to the host and the cluster as well. |
There was a problem hiding this comment.
| Alongside the kind cluster, a registry is running and can be accessed with tagging, pushing and pulling the images using `locahost:5000` from and to the host and the cluster as well. | |
| Kind launches a registry alongside the cluster. | |
| The registry will serve on port 5000, so users can tag and push images to the local registry at `localhost:5000`. | |
| Cluster workloads can then use this registry. |
Clarity (what provides the registry, what do users do with registries)
There was a problem hiding this comment.
To be very picky, we launch the registry with the container runtime, kind is configured to access the local registry
There was a problem hiding this comment.
Ah of course, I should have read create-cluster-kind.sh better.
I see you removed the section as a whole -- I thought it had some merits, but I'd also understand if you think it's out of scope.
Signed-off-by: Alice Frosi <afrosi@redhat.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: alicefr, Jakob-Naucke The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Jakob-Naucke
merged commit e886683
into
trusted-execution-clusters:main
4 participants
No description provided.