-
Notifications
You must be signed in to change notification settings - Fork 252
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
Add support for running in Kubernetes #154
Comments
Thanks for the bug report. I will test vanilla systemd in latest Kubernetes and report back. |
possibly related to this: this issue has also come up here: container-images/postfix#9 |
Just ran in to this. We currently have a FreeIPA instance running on a plain VM that we would love to move into our Kubernetes cluster. Wondering if this is still an issue before starting to experiment. |
Nope, works just fine on k8s 1.8+. |
Going to close this out since it's no longer an issue. |
@bradbeam do you happen to have a working example of freeipa and kubernetes? Or is the above working now? |
The above should work. |
Do you have an ingress or anything that maps an externally routable DNS name to this instance. When I do that, IPA seems to redirect immediately to the internal cluster hostname. In your case I have seen articles on how to avoid this redirect by changing the apache config inside IPA. Wondering if you ran into this. |
We don't use ingress; we use calico + bgp along with a headless service. So in our case, |
@bradbeam hey I applied that deployment.yaml, but when I try to access it via pod's ip or port-forwarding, it gives me "404 page not found" have u encountered this one? |
Please open new issue and provide exactly the kubectl commands you use. Ideally extend tests/run-master-in-k3s.sh to show what you try to do and what fails. |
Hey I ran into the same problem, when I set ingress for this, its giving me error "too many redirect" . do you know how to encounter this? @mmacfadden I have created helm-chart. and I am using this. |
With some of the recent changes to Kubernetes [1], systemd can no longer be pid1 inside of a container. This causes issues when trying to run the freeipa-containers which result in an error similar to [2]
Couldn't find an alternative telinit implementation to spawn
. When applying the workaround proposed in [3] to init-data [4], the container starts up, but hangs during the installation at[2/47]: creating directory server instance
. Even after adding in--debug
there isn't much information to go off of [5].Versions:
Kubernetes: 1.6.4 works, 1.7.2 broken
Docker: 1.13.1
freeipa-container: Dockerfile.centos-7-upstream // Dockerfile.fedora-26
freeipa-deployment.yaml
[1]
kubernetes/kubernetes#45236
[2]
kubernetes/kubernetes#48937
[3]
kubernetes/kubernetes#48937 (comment)
[4]
[5]
The text was updated successfully, but these errors were encountered: