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

Tiller RBAC creation fails for kubectl v1.10.11 #14464

Closed
benoitf opened this issue Sep 9, 2019 · 4 comments
Closed

Tiller RBAC creation fails for kubectl v1.10.11 #14464

benoitf opened this issue Sep 9, 2019 · 4 comments
Labels
area/chectl Issues related to chectl, the CLI of Che kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@benoitf
Copy link
Contributor

benoitf commented Sep 9, 2019

From chectl created by l0rd: che-incubator/chectl#78

When using helm as installer we should check that kubectl version is 1.11 or greater otherwise we get the following error:

 ✖ Create Tiller RBAC
      → error: SchemaError(io.k8s.apimachinery.pkg.apis.meta.v1.Patch): invalid object doesn't have additional properties
@benoitf benoitf added the bug label Sep 9, 2019
@benoitf
Copy link
Contributor Author

benoitf commented Sep 9, 2019

+1 @l0rd I was getting an unauthorized error was able to get past that by helm ls, Isn't it possible to access Auth Application default context?

@benoitf
Copy link
Contributor Author

benoitf commented Sep 9, 2019

I recognize @slemeur spirit in this issue :-)

@benoitf
Copy link
Contributor Author

benoitf commented Sep 9, 2019

@benoitf correct!

Actually to fix this issue I would like to avoid using kubectl and use kube javascript client instead in HelmHelper class.

@benoitf benoitf added area/chectl Issues related to chectl, the CLI of Che kind/bug Outline of a bug - must adhere to the bug report template. and removed bug labels Sep 9, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 9, 2019
@ibuziuk ibuziuk added severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Sep 9, 2019
@che-bot
Copy link
Contributor

che-bot commented Mar 11, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 11, 2020
@che-bot che-bot closed this as completed Mar 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/chectl Issues related to chectl, the CLI of Che kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

3 participants