Thanks!

Just a quick typo fix!

I am trying to login to openshift console url from below course using "developer" account, but it is automatically getting logout everytime.

COURSE LINK: https://learn.openshift.com/introduction/getting-started

Openshift console url: https://oauth-openshift-2886795280-443-host19nc.environments.katacoda.com/login?then=%2Foauth%2Fauthorize%3Fclient_id%3Dconsole%26redirect_uri%3Dhttps%253A%252F%252Fconsole-openshift-console-2886795280-443-host19nc.environments.katacoda.com%252Fauth%252Fcallback%26response_type%3Dcode%26scope%3Duser%253Afull%26state%3D7fccbe0c

We deployed a fix yesterday which appears to have corrected this issue that was related to a timing bug. If you could please retry that would be great.

Hi,

I am currently doing the openshift training. The oc client is working but as soon as I am waked to use the web console; I can add the user name and password. But then I get an error.

Is this training unavailable?

used training: https://learn.openshift.com/introduction/cluster-access

regards

Frank

We deployed a fix yesterday which appears to have corrected this issue that was related to a timing bug.

@jankleinert I see the issue now. I was going checking that the console loaded, but didn't check the login.

Investigating the fix now.

@jankleinert I'm unable to reproduce this. I wonder if there were some old nodes still left that hadn't been removed correctly this morning so the certificates had expired and where still running so not renewed.

Could you try again please? If you continue to see an issue, can you provide the full URL for the console you are accessing to help us debug.

@jankleinert Taking a look. The certificate rotation started this morning so might be related.

Operator Workshop - July 30 and 31, 2020 8am to 5pm Central Time. 30 attendees

Please use this pathway: https://github.com/openshift-labs/learn-katacoda/blob/master/operatorframework-pathway.json

Environments will need to be on 4.4

@BenHall @madorn

Thursday 30-07-2020 at 13:00 UTC until Thursday 30-07-2020 at 22:00 UTC

Number of expected attendees: 30

Environment: openshift-4-4

Friday 31-07-2020 at 13:00 UTC until Friday 31-07-2020 at 22:00 UTC

Number of expected attendees: 30

Environment: openshift-4-4

Operator Workshop - July 16 and 17, 2020 8am to 5pm Central Time. 40 attendees

Please use this pathway: https://github.com/openshift-labs/learn-katacoda/blob/master/operatorframework-pathway.json

Environments will need to be on 4.4

@BenHall @madorn

Thursday 16-07-2020 at 13:00 UTC until Thursday 16-07-2020 at 22:00 UTC

Number of expected attendees: 30

Environment: openshift-4-4

Friday 17-07-2020 at 13:00 UTC until Friday 17-07-2020 at 22:00 UTC

Number of expected attendees: 30

Environment: openshift-4-4

Operator Workshop - Wednesday, July 15, 15:30 UTC to 1930 UTC 100 attendees

Environments will need to be on 4.4

@BenHall @mrhillsman @mhrivnak @chris-short

Wednesday 15-07-2020 at 15:30 UTC until Wednesday 15-07-2020 at 19:30 UTC

Number of expected attendees: 100

Environment: openshift-4-4

Operator Workshop - Tuesday, July 14, 2230 UTC to 0230 UTC July 15th 100 attendees

Environments will need to be on 4.4

@BenHall @mrhillsman @mhrivnak @chris-short

Done

Tuesday 14-07-2020 at 22:30 UTC until Wednesday 15-07-2020 at 02:30 UTC

Number of expected attendees: 100

Environment: openshift-4-4

FYI: It looks like one of the environments in the pathway is still using 4.2

@girikuncoro The content should now be available when embedding Katacoda. Please let us know if you need anything else

@girikuncoro This looks great! We need to do something on our side to resolve an issue but this will be live tomorrow.

This PR is part of Indonesian translation docs https://github.com/kubernetes/website/issues/22296 . It requires to translate Kubernetes first scenario in Katacoda labs ( this page /docs/tutorials/kubernetes-basics/create-cluster/cluster-interactive/) 😊

cc: @girikuncoro

@soniasingla Sorry for the issue. The URL should be accessible and used when you are configuring the Git webhook. When you access it what do you see?

Tuesday 30-06-2020 at 15:25 UTC until 18:55 UTC

Number of expected attendees: 120

Environment: openshift-4-2

@madorn Sorry for not confirming, I was out of the office. This is scheduled. Please let us know if you need anything.

Which browser are you using?

On Mon, 22 Jun 2020, 21:38 Brian Tannous, [email protected] wrote:

@BenHall https://github.com/BenHall , not sure which css is causing this, any ideas?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openshift-labs/learn-katacoda/issues/809#issuecomment-647757535, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAUFNQ433DD6Q7XHCVGAULRX66M5ANCNFSM4OFAQGGA .

@btannous Thanks! I applied the changes this morning and will test properly when the certs expire at the end of the month.

Operator Workshop - June 25 and 26, 2020 7am to 5pm Central Time. 50 attendees

Please use this pathway: https://github.com/openshift-labs/learn-katacoda/blob/master/operatorframework-pathway.json

Environments will need to be on 4.2.

@BenHall @madorn

This has been scheduled.

Thursday 25-06-2020 at 12:00 UTC until Thursday 25-06-2020 at 22:00 UTC

Number of expected attendees: 50

Environment: openshift-4-2

Friday 26-06-2020 at 12:00 UTC until Friday 26-06-2020 at 22:00 UTC

Number of expected attendees: 50

Environment: openshift-4-2

@mrhillsman Thanks, we'll get this ready and scheduled

On the Katacoda side we adjusted our infrastructure so this shouldn't happen in future.

Noted. Will deploy tomorrow.

On Tue, 9 Jun 2020, 21:20 Jan Kleinert, [email protected] wrote:

@BenHall https://github.com/BenHall We added some additional tiles to the homepage, so we need to increase the height of the main div to get rid of the scrollbar. Can you merge and then redeploy (not sure specifically what you have to do) so that the change takes effect?

Thanks!

@jdob https://github.com/jdob FYI

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openshift-labs/learn-katacoda/pull/795#issuecomment-641547673, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAUFNSYYZYGNJZQMNCALRDRV2KRDANCNFSM4NZXVABA .

@devopskarthikeyan The 1.11 release should include a fix for this - https://github.com/code-ready/crc/releases/tag/1.11.0

General information

• OS: Linux / Ubuntu 16.04
• Hypervisor: KVM
• Did you run crc setup before starting it (Yes/No)? Yes
• Running CRC on: Baremetal-Server

CRC version

crc version: 1.11.0+883ca49
OpenShift version: 4.4.5 (embedded in binary)

Host Operating System

cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.6 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.6 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

Steps to reproduce

1. crc-linux-1.11.0-amd64 # ./crc setup INFO Checking if oc binary is cached INFO Caching oc binary INFO Checking if podman remote binary is cached INFO Checking if goodhosts binary is cached INFO Caching goodhosts binary INFO Will use root access: change ownership of /root/.crc/bin/goodhosts FATA Unable to set ownership of /root/.crc/bin/goodhosts to root:wheel: exit status 1: chown: invalid group: ‘root:wheel’

2. ./crc setup INFO Checking if oc binary is cached INFO Caching oc binary INFO Checking if podman remote binary is cached INFO Checking if goodhosts binary is cached INFO Caching goodhosts binary INFO Will use root access: change ownership of /home/ubuntu/.crc/bin/goodhosts INFO Will use root access: set suid for /home/ubuntu/.crc/bin/goodhosts INFO Checking if CRC bundle is cached in '$HOME/.crc' INFO Unpacking bundle from the CRC binary INFO Checking if running as non-root INFO Checking if Virtualization is enabled INFO Checking if KVM is enabled INFO Checking if libvirt is installed INFO Installing libvirt service and dependencies INFO Will use root access: install virtualization related packages FATA Could not install required packages: exit status 1: sudo: yum: command not found

Expected

Dependency on wheel not require and apt-get to be used instead

Actual

Need to add addgroup wheel

@ozbillwang Thanks! We'll get the API updated to reflect this new image and the validate environment list.

@mvazquezc The fix should be live

The certificates expired this morning and it looks like this has had an impact. Any suggestions?

@michal-hudy Thank you for investigating Katacoda. On our free platform we do limit the memory usage. However, we have options available for those w ith additional resource requirements. When we previously discussed (https://github.com/kyma-project/kyma/issues/4095#issuecomment-508366977) we increased the memory and it worked as expected. If you could drop me an email (ben@katacoda) then I can go into more details.

Hello,

I deployed a k8s service in my scenario and doing a port forward as below

$ kubectl --namespace default port-forward svc/imply-manager-int 9097
Forwarding from 127.0.0.1:9097 -> 9097
Forwarding from [::1]:9097 -> 9097

And the URL below is not working

https://2886795288-9097-ollie09.environments.katacoda.com/

Any help is much appreciated. Thank you.

@kumarlalapet By default, Kube Proxy only accepts connections from localhost as it only listens on 127.0.0.1 for security / dev purposes.

$ kubectl proxy
Starting to serve on 127.0.0.1:8001

You can explicitly bind to 0.0.0.0 by setting it as the address. This will make it available via the Katacoda URL and to your browser.

$ kubectl proxy  --address=0.0.0.0
Starting to serve on [::]:8001

We are currently testing a fix. I will update when it's live.

Operator Workshop - May 26, 2020 10am to 4pm Central Time. 40 attendees

Please use this pathway: https://github.com/openshift-labs/learn-katacoda/blob/master/operatorframework-pathway.json

Environments will need to be on 4.2.

@BenHall @madorn

@ozbillwang They should all be available. Could you please retry?

Hello,

I wrote a first scenario based on the upload-assets scenario: I used the same code and when I push it on GitHub, it didn't work. In the scenario, the deploy.sh script should create a file in the root folder but this file is never created.

In the sample, the path for the shell script are /opt/... but they are copied to /usr/local/bin/. I had an error when I launched the scenario. I corrected the path but it does nos work :-(

So, I used a workaround and it works as expected now : I removed all the code of the shell scripts from the sample and just call my deploy.sh. The code of my scenario is available here.

Currently when run katacoda-cli you get errors:

• Scenario=/app/environment-usages/minikube/ - Validation Error: There are missing scenario files step2.md,step3.md
• Scenario=/app/uilayouts/uilayout-iframe/ - Validation Error: Layout specified in the index.json is not part of the acceptable layouts as specified here: https://katacoda.com/docs/scenarios/layouts
• Scenario=/app/uilayouts/uilayout-terminal-iframe-split/ - Validation Error: Layout specified in the index.json is not part of the acceptable layouts as specified here: https://katacoda.com/docs/scenarios/layouts

Whole output:

$ katacoda validate:all --repo=/app/

Scenario=/app/clipboard/ - is valid
Scenario=/app/create-course/ - is valid
Scenario=/app/create-scenario-101/ - is valid
Scenario=/app/credit-where-credit-due/ - is valid
Scenario=/app/dashboard-tabs/ - is valid
Scenario=/app/dashboard-tabs-iframe/ - is valid
Scenario=/app/displaying-images/ - is valid
Scenario=/app/displaying-progress-spinner/ - is valid
Scenario=/app/displaying-web-ui/ - is valid
Scenario=/app/environment-usages/docker/ - is valid
Scenario=/app/environment-usages/docker-swarm/ - is valid
Scenario=/app/environment-usages/kubernetes/ - is valid
Scenario=/app/environment-usages/kubernetes-cluster/ - is valid
Scenario=/app/environment-usages/minikube/ - Validation Error: There are missing scenario files step2.md,step3.md
Scenario=/app/environment-usages/ubuntu/ - is valid
Scenario=/app/markdown-extensions/ - is valid
Scenario=/app/opening-multiple-terminals/ - is valid
Scenario=/app/quiz/ - is valid
Scenario=/app/run-commands-automatically/ - is valid
Scenario=/app/uilayouts/uilayout-editor-terminal/ - is valid
Scenario=/app/uilayouts/uilayout-iframe/ - Validation Error: Layout specified in the index.json is not part of the acceptable layouts as specified here: https://katacoda.com/docs/scenarios/layouts
Scenario=/app/uilayouts/uilayout-terminal/ - is valid
Scenario=/app/uilayouts/uilayout-terminal-iframe/ - is valid
Scenario=/app/uilayouts/uilayout-terminal-iframe-split/ - Validation Error: Layout specified in the index.json is not part of the acceptable layouts as specified here: https://katacoda.com/docs/scenarios/layouts
Scenario=/app/uilayouts/uilayout-terminal-terminal/ - is valid
Scenario=/app/upload-assets/ - is valid
Scenario=/app/verified-steps/ - is valid
Scenario=/app/visualise-docker/ - is valid

I set environmentsprotocol to http and still getting this:

WebSocket connection to 'ws://2886795282-30080-elsy06.environments.katacoda.com' failed: Error during WebSocket handshake: Unexpected response code: 200

This is my index.json: https://github.com/svekars/katacoda-scenarios/blob/master/getting-started/index.json

@svekars Sorry, I missed your additional question. All ports are available and accessible. More information is at https://www.katacoda.community/accessing-ports-ui.html#using-placeholders-in-scripts

@derberg Within our subscription, you can customise the width when embedding Katacoda into your own documentation. This is an example of what the CSS looks like when using this API.

Currently you can't change the look/feel of the layout on katacoda.com to ensure a consistent user experience.

Hi. I noticed https://github.com/katacoda/scenario-examples/blob/master/assets/test.css but I tried and it did not have any effect on the scenario. Is this implemented?

@ozbillwang You are correct, this is only available within the subscription. You can however use the Ubuntu 18.04 environment and download the Docker Image directly.

The complete list of environments can be found at https://www.katacoda.community/environments.html

Hello, I was able to install the KubeVirt community product into the OpenShift 4.2 playground by applying yaml's directly from the internet

This begs the question what else can be installed into the playground environment.

Thanks for bringing this up. Yes, this is intentional and by design.

Operator Workshop - May 19 and 20, 2020 7am to 4pm Central Time. 40 attendees

Please use this pathway: https://github.com/openshift-labs/learn-katacoda/blob/master/operatorframework-pathway.json

Environments will need to be on 4.2.

@BenHall @mrhillsman

Operator Workshop - May 15 and 22, 2020 8am to 4pm Central Time. 10 attendees

Please use this pathway: https://github.com/openshift-labs/learn-katacoda/blob/master/operatorframework-pathway.json

Environments will need to be on 4.2.

@BenHall @madorn

Operator Workshop - May 13 and 14, 2020 7am to 5pm Central Time. 20 attendees

Please use this pathway: https://github.com/openshift-labs/learn-katacoda/blob/master/operatorframework-pathway.json

Environments will need to be on 4.2.

@BenHall @mrhillsman