-
Notifications
You must be signed in to change notification settings - Fork 96
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
[BUG] - module.kubernetes-keycloak-helm.helm_release.keycloak timed out waiting for the condition on local development #2076
Comments
Hi @chrislevn, sorry to hear you're running into trouble with the local deployment. Local deployments have been a little tricky. Currently this only works on systems running Linux (see #1405). This is where folks, including myself, have been able to deploy to when doing so on Mac. These docs go into more detail if you want to try again on Linux. |
@iameskild Does this also mean for:
|
@chrislevn deploying Nebari to one of the cloud providers is supported on Mac (M1 and Intel). The issue is with deploying Nebari using Kind locally. |
Hi @iameskild, I just found out that with the latest version of Nebari (2023.10.1), there is an option to After upgrading it, I can't deploy Nebari, even after regenerating a new config file. The issue was ValidationError: 1 validation error for ExistingInputVars
kube_context
none is not an allowed value (type=type_error.none.not_allowed) In my
[2] My questions are: Here is the whole config file I would like to deploy:
|
Describe the bug
I'm trying to test deploy Nebari on local (run on Kubernetes - profile docker-desktop). The keycloak stopped due to time out after 5ms.
Result of
kubectl get pods -n <namespace>
:Result of
kubectl logs nebari-traefik-ingress-7dbfdc5dd5-5hfkq -n <namespace>
My questions are:
Expected behavior
Pass all the deployment stages with an accessible URL/IP Address at the end
OS and architecture in which you are running Nebari
MacOS M1
How to Reproduce the problem?
nebari-config.yaml
I ran this with
nebari deploy -c nebari-config.yaml --dns-auto-provision
Command output
No response
Versions and dependencies used.
kubectl version
nebari --version
Compute environment
kind
Integrations
Keycloak
Anything else?
This is related to issue #1491.
However, I am still getting the same error regardless of latest update.
The text was updated successfully, but these errors were encountered: