skupperproject / skupper-website Goto Github PK

#25

https://skupper.io/docs/declarative/tutorial.html references v. 0.3 of the site controller

Docker desktop now supports k8s https://www.docker.com/products/kubernetes

However, ran into issues trying to run thru the getting-started:

• setting the config, eg kubectl config set-context --current --namespace west
  workaround is to copy the ~/.kube/config to ~/.kube/config-west

• creating connection
  creating the token seems to work fine, but cannot make the connection

$ skupper connect $HOME/secret.yaml
Skupper configured to connect to localhost:55671 (name=conn1)
$ skupper status Skupper is enabled for namespace "east" in interior mode. It is not connected to any other sites. It has no exposed services.

For each release we update config.py and run `./plano render'. However this time that process only updated releases/index.html
As a workaround I reverted to an old version of .planofile

output at https://gist.github.com/pwright/4e48eca4c028009db32ade54296532b2

I think this should create a route?

kubectl expose deployment hello-world-frontend --port 8080 --type LoadBalancer

it's not doing it for me in OCP 3.11, altho I can create the route using the console and all works

see https://skupper.io/docs/overview/index.html

Images aren't available in the specified path, e.g.:
https://skupper.io/docs/overview/_images/overview-clouds.png

See screenshot below:

Consolidate our install instructions, currently

https://skupper.io/releases/index.html
https://skupper.io/start/index.html#step-1-install-the-skupper-commandline-tool-in-your-environment
https://skupper.io/install/index.html
https://skupper.io/docs/cli/index.html#installing-cli

The instructions at https://skupper.io/start/minikube.html assume that when running minikube tunnel, the correct kubeconfig is set. If multiple separate profiles for minikube are run at once, then the tunnel can only be run for one of them. For the hello world example this would require tweaking the instructions such that the backend site connects to the frontend site (so that the frontend site can have loadbalancer capability as it uses that for the exposed service also). The backend site would need to use --cluster-local or --edge on skupper init.

While you can use YAML with K8s, and cli with OCP, we discussed and agreed to create a Getting Started with OpenShift guide that provides an alternative using just yaml:

• provision a site controller
• create a site
• request a token
• use a token

using OpenShift terminology (Projects, not namespaces)

The current site takes a very long time to load each page for me. I see the browser hang on connecting to localhost before timing out and loading the rest of the site. The site seems to work OK once loaded, but this hang occurs on every page load.

In the page source, I see this:

<script src="http://localhost:35729/livereload.js"></script>

Since visitors won't be running a local web server to serve a JavaScript file on a weird port, this should almost certainly be omitted from the page source.

Hi,

Following the Getting Started guide, the first step suggests to check the skupper version command before configuring namespaces, but at this point skupper just informs that the configuration has not been provided:

$ skupper version
invalid configuration: no configuration has been provided

After configuring namespaces with kubectl, it returns the versions correctly:

$ skupper version
client version                 0.5.3
transport version              not-found
controller version             not-found

The rest of the instructions from the guide work as expected.

Thanks!

When the change from cert to claim tokens was added, the instructions are using the defaults with claim token and uses = 1.

This causes the addition of another site to fail as the claim was already used if another token is not created for the second site.

A note on the instructions related to this would help people avoid this problem in the future.

On the releases page, the link to the 1.1.1 version actually points to 1.1.0.

<li><a href="https://github.com/skupperproject/skupper/releases/tag/1.1.0">1.1.1</a> - October 2022</li>

https://skupper.io/releases/index.html shows 0.8.1 not 0.8.5