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.

Sign up for GitHub

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

Jump to bottom

Kubernetes without access to the Apiserver #21230

Closed
mmack opened this issue Mar 3, 2022 · 1 comment
Closed

Kubernetes without access to the Apiserver #21230

mmack opened this issue Mar 3, 2022 · 1 comment
Labels
area/install Issues related to installation, including offline/air gap and initial setup kind/question Questions that haven't been identified as being feature requests or bugs. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@mmack
Copy link

mmack commented Mar 3, 2022 •
edited
Loading

Summary

I'm using managed kubernetes from vultr.com. They do not allow me to change settings on the apiserver, so i'm not able to set k8s up like described by this user: #21049 (comment) (btw i can't find that setup step anywhere in the docs)

So, is it even possible to install Che then ?

Relevant information

https://www.vultr.com/kubernetes/
@mmack mmack added the kind/question Questions that haven't been identified as being feature requests or bugs. label Mar 3, 2022
@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 Mar 3, 2022
@sparkoo
Copy link
Member

sparkoo commented Mar 3, 2022

You don't need to change Kubernetes apiserver settings. You need to setup Che to same OIDC as Kubernetes. So you're interested only in Configure Che part of #21049 (comment). You need identity provider url, client and secret and you should get that from your Kubernetes provider (Vultr).

@sparkoo sparkoo added area/install Issues related to installation, including offline/air gap and initial setup 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 Mar 3, 2022
@tolusha tolusha closed this as completed May 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/install Issues related to installation, including offline/air gap and initial setup kind/question Questions that haven't been identified as being feature requests or bugs. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mmack @sparkoo @tolusha @che-bot