Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error installing rio on k8s v1.16.2 #580

Closed
greyarch opened this issue Oct 19, 2019 · 9 comments
Assignees
Labels
Milestone

Comments

@greyarch
Copy link

@greyarch greyarch commented Oct 19, 2019

Describe the bug
rio install fails when using k8s v1.16.2.
Error message is failed to discover client for extensions/v1beta1, Kind=Deployment

To Reproduce
Steps to reproduce the behavior:
Create a k8s v1.16.2 cluster. Try installing rio.

Expected behavior
Rio gets isntalled.

Kubernetes version & type (GKE, on-prem): kubectl version

Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:18:23Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:09:08Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
@StrongMonkey StrongMonkey added the bug label Oct 19, 2019
@StrongMonkey

This comment has been minimized.

Copy link
Member

@StrongMonkey StrongMonkey commented Oct 19, 2019

@greyarch thanks for reporting this. We should bump api version for deployment in next release.

@izaac

This comment has been minimized.

Copy link
Contributor

@izaac izaac commented Oct 22, 2019

Validated that this fails with k8s 1.16.2 using k3s v0.10.0-rc2
rio v0.5.0
@StrongMonkey @davidnuzik

@davidnuzik

This comment has been minimized.

Copy link
Collaborator

@davidnuzik davidnuzik commented Oct 22, 2019

Thanks @izaac moving out of test.

@Vad1mo

This comment has been minimized.

Copy link

@Vad1mo Vad1mo commented Oct 25, 2019

Is there any workaround or pre-release available meanwhile?

@izaac

This comment has been minimized.

Copy link
Contributor

@izaac izaac commented Oct 25, 2019

@Vad1mo we are expecting to have a v0.6.0 RC soon.

@izaac

This comment has been minimized.

Copy link
Contributor

@izaac izaac commented Oct 25, 2019

@Vad1mo latest v0.6.0-alpha.1 is out, but expect it to contain bugs. It works with k8s 1.16.2

snsinfu added a commit to snsinfu/infra-rio that referenced this issue Oct 26, 2019
K3s v0.10.0 uses newer kubernetes API. It causes Rio installation issue:

    rancher/rio#580

The bug will be fixed in the next Rio release. For now let us downgrade
k3s to the previous version.
snsinfu added a commit to snsinfu/infra-rio that referenced this issue Oct 26, 2019
Rio v0.6.0-alpha.1 solves the innstallation issue:

    rancher/rio#580
@izaac

This comment has been minimized.

Copy link
Contributor

@izaac izaac commented Oct 28, 2019

I tested this with a k3s v0.10.0 instance on Linode, the installation goes through with rio despite the warning messages.

I did the same in a local docker installation using k3d

k3d create --workers 0 --image rancher/k3s:v0.10.0 -n $name --publish 80:80 --publish 443:443 --publish 9443:9443 --publish 9080:9080 &&

rio install  --ip-address=127.0.0.1
Deploying Rio control plane....
- Warning: Detected that Rio cluster domain is not generated for this cluster right nowClusterDomain is reachable. Run `rio info` to get more info.
rio controller version v0.6.0-alpha.1 (7678d67d) installed into namespace rio-system
Controller logs are available from `rio systemlogs`

Welcome to Rio!

Run `rio run https://github.com/rancher/rio-demo` as an example
➜  rio-izaac git:(master) ✗ rio info
Rio Version: v0.6.0-alpha.1 (7678d67d)
Rio CLI Version: v0.6.0-alpha.1 (7678d67d)
Cluster Domain: fn5f8w.on-rio.io
Cluster Domain IPs: 127.0.0.1
System Namespace: rio-system
System Ready State: false
Wildcard certificates: false

System Components:

➜  rio-izaac git:(master) ✗ k cluster-info
Kubernetes master is running at https://127.0.0.1:6443
CoreDNS is running at https://127.0.0.1:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
➜  rio-izaac git:(master) ✗ k version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.6", GitCommit:"96fac5cd13a5dc064f7d9f4f23030a6aeface6cc", GitTreeState:"clean", BuildDate:"2019-08-19T11:13:49Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2-k3s.1", GitCommit:"b8b17ba55f20e590df507fce333dfee13ab438c6", GitTreeState:"clean", BuildDate:"2019-10-16T05:17Z", GoVersion:"go1.13.3", Compiler:"gc", Platform:"linux/amd64"}

The installation is being polished at the moment by Dev to address all these and we will be further test it in a future alpha/RC. The original reported issue of not being able to install in a k8s cluster v1.16.2 cluster seems solved.

@izaac izaac closed this Oct 28, 2019
@zube zube bot added [zube]: Done and removed [zube]: To Test labels Oct 28, 2019
@izaac

This comment has been minimized.

Copy link
Contributor

@izaac izaac commented Oct 28, 2019

Related issues for tracking:

#619
#605
#599

@Vad1mo

This comment has been minimized.

Copy link

@Vad1mo Vad1mo commented Oct 28, 2019

can confirm as well that rio 0.6alpha installation works on 1.16.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
6 participants
You can’t perform that action at this time.