Qlik Community

Qlik Support Updates Blog

Important and useful support information about end-of-product support, new service releases, and general support topics.

Announcements
QlikWorld, June 24-25, 2020. Free virtual event for DI and DA gurus. Register Now
Digital Support
Digital Support

Available now an example of Kubernetes environment preparation for QSEoK including deployment steps.

Qlik Sense Enterprise on Kubernetes (QSEoK) has specific environmental requirements which can easily be missed posing a challenge with the new deployment.

Qlik Digital Support has documented steps on an example CentOS Linux system to meet those requirements including the deployment of QSEoK.

You can see this content via the Knowledge Base articles below:

Kubernetes cluster deployment example in preparation to QSEoK deployment
https://support.qlik.com/articles/000101537

Deployment example of Qlik Sense Enterprise on Kubernetes (QSEoK)
https://support.qlik.com/articles/000101649

Please give this post a like if you found it helpful! Also please let us know if you have any questions or leave your feedback in the comments.

 

 

7 Comments
Partner
Partner

I'm following the steps as described in the support article "Deployment example of QSEoK" to install Qlik Sense for Kubernetes on a single node K8s cluster for testing. The cluster is deployed with MicroK8s on a Linux EC-instance in AWS with Ubuntu 18.4. The cluster is up and running and I was able to deploy a sample app and access it from outside the cluster. The installation of Qlik Sense with helm was also succesful. After the installation all pods are running as expected.

During installation I used a YAML file to configure the built-in IDP on NodePort 32433 (as described in the support article). After upgrading the Qlik Sense deployment with the "helm upgrade" command I can see the service 'qliksense-nginx-ingress-controller' is listening on port 32443.

I'm having an issue logging into Qlik Sense via the built-in IDP to apply the license. When I navigate to the URL "https://elastic.example:32443" I can see the certificate warning, so the site is reachable, but when I proceed the browser is redirected to "http://elastic.example:32123" and I end up with the message "can't reach this page". I can't figure out where this redirct URL comes from and how to solve this.

Any help would be appreciated.

0 Likes
353 Views
Digital Support
Digital Support

@ssamuels, thank you for posting your issue.

Edge-Auth is the service listening on 32123 (for authentication/login request). If you have issues with that service the login page will not display.

You can get more detail running the commands below:

kubectl describe service qliksense-edge-auth

kubectl describe pod qliksense-edge-auth

You can also try to kill the specific pod:

kubectl delete pod qliksense-edge-auth-<ID>

where <ID> you can check by running kubectl get pods

257 Views
Partner
Partner

When I run the command "kubectl describe service qliksense-edge-auth" I can see the service is listening on nodeport 31695, instead of port 32123 that you mention (and the one that is being used in the redirect URL). None of the services is listening on port 32123 in my environment.

I tried deleting the pod qliksense-edge-auth-<ID> because I saw some liveless probe failures in the logs. After recreating the pod the errors are gone, but the issue remains the same.

 

 

 

 

0 Likes
207 Views
Digital Support
Digital Support

did you try replacing the redirect auth URL with the port 31695 in your browser, and hitting <enter>, to see the behavior?

 

0 Likes
178 Views
Partner
Partner

Yes I did. Then I get an http 403 error (declined request because endpoint is configured for https only).

157 Views
Digital Support
Digital Support

@ssamuels, I see. I am assuming the error looks like this?

{"errors":[{"title":"Received plain HTTP request over endpoint configured for HTTPS only","code":"AUTH-NOT-SECURE","status":"403"}]} 

 Please post the output of "kubectl describe service qliksense-edge-auth" here.

 

0 Likes
138 Views