-
Notifications
You must be signed in to change notification settings - Fork 103
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
Ingress API version is end-of-live #255
Comments
Did you get it working? Can you make a pull request with that update? |
Deployment worked, but there is an issue accessing the front end. Will update the issue after I fix it. |
URL to the admin portalResponse I am getting back-- Question"Additionally this example assumes that pki.primekey.example to be resolvable from the Ingress." Where should the address point to, or to where should it resolve? does the readme intend to deploy the app locally? And if yes, what needs to be changed to deploy it to a public cloud? |
do you use https:// in the url and not http://? |
To create a new branch and a pull request do the following:
|
The RA UI is there, in the EJBCA Admin UI there is link to it at the bottom left menu. |
Hi @kathodion : if you don't want, or can't, create a PR. Just upload your version here and we will take care of it. |
Hi @kathodion , if you don't know how to create a PR, you can send me the files as well and I can handle it. |
Hi
Had problems deploying the file https://github.com/Keyfactor/ejbca-containers/blob/master/deployment-examples/kubernetes/microk8s/ejbca-ce-with-ingress-and-mariadb.yaml
to Azure K8 cluster. The problem occurred around the API version v1beta. Tried to migrate the code to v1 stable, but it needs further testing (I am quite new to K8).
Here is my version
The text was updated successfully, but these errors were encountered: